Difference between revisions of "Collaborative Development"
| Line 1: | Line 1: | ||
{{DevelopersTopNav}} | {{DevelopersTopNav}} | ||
| − | We encourage developers of geWorkbench plugins to use our | + | 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 | + | 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. | * A '''src''' directory containing the plugin code. | ||
* An optional '''lib''' directory containing jar files required by the plugin. | * 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). | 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 | + | 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. |
Revision as of 11:16, 23 March 2010
|
Developers Home | A Simple Plugin | geWorkbench Archive Files | Collaborative Development | Design Documentation | Javadocs | gForge Page | Report Defects |
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 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.
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 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.
