Collaborative Development - Revision history

Zji at 01:50, 26 April 2010

2010-04-26T01:50:13Z

Zji at 16:16, 23 March 2010

2010-03-23T16:16:50Z

Floratos at 05:56, 27 February 2006

2006-02-27T05:56:40Z

Califano at 15:40, 21 February 2006

2006-02-21T15:40:32Z

Floratos at 06:03, 21 February 2006

2006-02-21T06:03:27Z

New page

We encourage developers of geWorkbench plugins to use our CVS server infrastructure. Our source code tree comprises 2 separate CVS modules named ''geWorkbench'' and ''components'' which corespond to the core and plugin code portions outlined in the "[[Developers]]" section.

Collaborative development takes place under the components module. The module contains a number of subdirectories, each corresponding to one geWorkbench plugin. Each subdirectory has the same basic structure:
* A '''src''' directory containing the plugin code.
* An optional '''lib''' directory containing jar files required by the plugin.

The application ant build script (which is made available to collaborative developers) will also create a '''classes''' directory which will contain the executable code. To create a new plugin called "example" a new directory with the same name will be created under the components module and CVS accounts will be issued to the members of the component development team. All developers in that team will become members of a new Unix group which will own the subdirectory (the rest of the world will have read-only rights).

A full development environment can be then obtained by checking out the 2 project CVS modules, "geWorkbench" and "components". In this development space the plugin development team will be able to change the code of their plugin as they please, check it in and out of CVS, use all the available build scripts, etc. However, they will only have read rights to the core "geWorkbench" module.

@@ Line 7: / Line 7: @@
 * An optional '''lib''' directory containing jar files required by the plugin.
-The application ant build script (which is made available to collaborative developers) will also create a '''classes''' directory which will contain the executable code. To create a new plugin called "example" a new directory with the same name will be created under the components module and CVS accounts will be issued to the members of the component development team. All developers in that team will become members of a new Unix group which will own the subdirectory (the rest of the world will have read-only rights).
+The application ant build script (which is made available to collaborative developers) will also create a '''classes''' directory which will contain the executable code. To create a new plugin called "example" a new directory with the same name will be created under the components directory.
-A full development environment can be then obtained by checking out the the project "geWorkbench" and one project for each subdirectory under "components". In this development space the plugin development team will be able to change the code of their plugin as they please, check it out of subversion.
+A full development environment can be then obtained by checking out the the project "geWorkbench" and one project for each subdirectory under "components". In this development space the plugin development team will be able to change the code of their plugin as they please after checking out the code. To commit new code into our code base hosted by NCI's subversion server, you need an NCICB account. Please contact us for more detail.

@@ Line 1: / Line 1: @@
 {{DevelopersTopNav}}
-We encourage developers of geWorkbench plugins to use our CVS server infrastructure. Our source code tree comprises 2 separate CVS modules named ''geworkbench'' and ''components'' which corespond to the core and plugin code portions outlined in the "[[Developers]]" section.
+We encourage developers of geWorkbench plugins to use our code repository. Our source code tree comprises 2 separate modules under ''geworkbench'', ''src'' for the core and ''components'' for the plugin code portions as outlined in the "[[Developers]]" section.
-Collaborative development takes place under the components module. The module contains a number of subdirectories, each corresponding to one geWorkbench plugin. Each subdirectory has the same basic structure:
+Collaborative development typically takes place under the components module. The module contains a number of subdirectories, each corresponding to one geWorkbench component package, which can contain one of more related component plugins. Each subdirectory has the same basic structure:
 * A '''src''' directory containing the plugin code.
 * An optional '''lib''' directory containing jar files required by the plugin.
@@ Line 9: / Line 9: @@
 The application ant build script (which is made available to collaborative developers) will also create a '''classes''' directory which will contain the executable code. To create a new plugin called "example" a new directory with the same name will be created under the components module and CVS accounts will be issued to the members of the component development team. All developers in that team will become members of a new Unix group which will own the subdirectory (the rest of the world will have read-only rights).
-A full development environment can be then obtained by checking out the 2 project CVS modules, "geWorkbench" and "components". In this development space the plugin development team will be able to change the code of their plugin as they please, check it in and out of CVS, use all the available build scripts, etc. However, they will only have read rights to the core "geworkbench" module.
+A full development environment can be then obtained by checking out the the project "geWorkbench" and one project for each subdirectory under "components". In this development space the plugin development team will be able to change the code of their plugin as they please, check it out of subversion.

@@ Line 1: / Line 1: @@
 {{DevelopersTopNav}}
-We encourage developers of geWorkbench plugins to use our CVS server infrastructure. Our source code tree comprises 2 separate CVS modules named ''geWorkbench'' and ''components'' which corespond to the core and plugin code portions outlined in the "[[Developers]]" section.
+We encourage developers of geWorkbench plugins to use our CVS server infrastructure. Our source code tree comprises 2 separate CVS modules named ''geworkbench'' and ''components'' which corespond to the core and plugin code portions outlined in the "[[Developers]]" section.
 Collaborative development takes place under the components module. The module contains a number of subdirectories, each corresponding to one geWorkbench plugin. Each subdirectory has the same basic structure:
@@ Line 9: / Line 9: @@
 The application ant build script (which is made available to collaborative developers) will also create a '''classes''' directory which will contain the executable code. To create a new plugin called "example" a new directory with the same name will be created under the components module and CVS accounts will be issued to the members of the component development team. All developers in that team will become members of a new Unix group which will own the subdirectory (the rest of the world will have read-only rights).
-A full development environment can be then obtained by checking out the 2 project CVS modules, "geWorkbench" and "components". In this development space the plugin development team will be able to change the code of their plugin as they please, check it in and out of CVS, use all the available build scripts, etc. However, they will only have read rights to the core "geWorkbench" module.
+A full development environment can be then obtained by checking out the 2 project CVS modules, "geWorkbench" and "components". In this development space the plugin development team will be able to change the code of their plugin as they please, check it in and out of CVS, use all the available build scripts, etc. However, they will only have read rights to the core "geworkbench" module.

← Older revision		Revision as of 15:40, 21 February 2006
Line 1:		Line 1:
		+	{{DevelopersTopNav}}
		+
	We encourage developers of geWorkbench plugins to use our CVS server infrastructure. Our source code tree comprises 2 separate CVS modules named ''geWorkbench'' and ''components'' which corespond to the core and plugin code portions outlined in the "[[Developers]]" section.		We encourage developers of geWorkbench plugins to use our CVS server infrastructure. Our source code tree comprises 2 separate CVS modules named ''geWorkbench'' and ''components'' which corespond to the core and plugin code portions outlined in the "[[Developers]]" section.