THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Principles:
- top level in svn tree:
- (same) uima - overall top
- (same) uimaj - java sdk for framework
- (same) uimacpp - cpp for framework
- (same) uima-as - uima addon for asynch scaleout
- (same) sandbox - for developing things, not all released, not necessarily well documented, etc.
- (same) site
- (same) uima - overall top
- new top level things:
- under uima
- (no)internal-tools - things not in normal binary distributions, but used in building, etc. Reason for not doing: not needed, reduce change. Instead, change rest of build to pull these when needed as mvn dependencies.
- super-poms - non-aggregate poms in the super-pom hierarchy
- annotators - released and more fully documented/supported annotators from the sandbox (called out because of importance)
- add-ons - released and more fully documented/ supported add-ons, such as simple-server
- under uima
...
- For example, with sandbox/trunk/projXyz the tag would be sandbox/tags/projXyz-version-number-etc
- see what the convention is for maven "release" plugin and follow that?
- To give a counter-example, what we're not doing is something like
- (not doing) sandbox/projXyz/trunk
- (not doing) sandbox/projXyz/tags/version-number-etc ...
- separate "aggregate" and "super" poms
- for super poms - put in containing super-poms project
- for aggregate poms - just leave in flat organization - tools should now support this
- scm element in pom needs to point to where this pom is, in the svn tree (to make releasing conventional)
- change relative links in pom structure to assume the layout that m2eclipse would create