Page History
...
previous path | new path under http://scm.dspace.org/svn/repo/modules/![]() |
---|---|
http://scm.dspace.org/svn/repo/dspace/trunk/dspace-api![]() | modules/dspace-api/trunk |
http://scm.dspace.org/svn/repo/dspace/trunk/dspace-xmlui![]() | modules/dspace-xmlui/trunk |
http://scm.dspace.org/svn/repo/dspace/trunk/dspace-jspui![]() | modules/dspace-jspui/trunk |
http://scm.dspace.org/svn/repo/dspace/trunk/dspace-oai![]() | modules/dspace-oai/trunk |
http://scm.dspace.org/svn/repo/dspace/trunk/dspace-sword![]() | modules/dspace-sword/trunk |
http://scm.dspace.org/svn/repo/dspace/trunk/dspace-lni![]() | modules/dspace-lni/trunk |
...
New Maven POM projects exist for DSpace in the modules directory, these pom eliminate a bottleneck in the dependency mechanism defined in the dspace-parent pom in favor of allowing individual projects manage their dependency versions. It is released separately from the DSpace release process so that it can be utilized before the official release to base new modules on.
http://scm.dspace.org/svn/repo/modules/dspace-pom/tags/
Doing this increases the flexibility to define and override dependency versions used when customizing DSpace instances in the wild. And depending on this pom provides all the basic details for the build and release process of maven without forcing specific dependencies onto the components that use it.
...