Difference between revisions of "ESciDoc Development environment"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
* Easier to checkout the whole escidoc-project | * Easier to checkout the whole escidoc-project | ||
* External libraries can be checked in the repository | * External libraries can be checked in the repository. This ensures that every developer uses the same library and application server versions | ||
* build, dist and lib paths can be made relative, instead of using local_build.property files | * build, dist and lib paths can be made relative, instead of using local_build.property files | ||
Revision as of 08:40, 17 October 2007
Subversion repository
Currently the developers are using multiple subversion repositorys for each of the components of the escidoc project. Since there are dependencys between these repositorys, the usage of a single one shall be investigated.
Some ideas why using one repository instead of multiple ones
- Easier to checkout the whole escidoc-project
- External libraries can be checked in the repository. This ensures that every developer uses the same library and application server versions
- build, dist and lib paths can be made relative, instead of using local_build.property files
Directory structure inside the single repository:
/escidoc
/dev
/src
/citationmanager_service
/bin
/src
/resource
.
.
.
.
.
.
/build
/dist
/lib
/ext
/jboss
/doc