Now seems like the best time to initiate Maven 2 migration. I tried
to identify logical dependencies that can be mapped to Maven modules
(see a little diagram here [1]). The same diagram in terms of Maven
project structure may look like this:
cayenne
core
cayenne-core
cayenne-core-java-1.5
cayenne-remote
cayenne-server
cayenne-server-java-1.5
cayenne-jpa
cayenne-webobjects
modeler
modeler-plugin
plugin-launcher
swing-plugin
The structure reflects the excludes used in the cayenne-ant/ant/
cayenne-java.xml to build smallest possible client jars, and also the
fact that WebObjects community uses Cayenne as a third-party open
source lib for various things [2]. We could split a number of other
small standalone modules (cayenne-xml, cayenne-datasource, cayenne-
events), but I wouldn't worry about that now, let's settle on the big
picture first.
Thoughts?
Andrus
[1] http://people.apache.org/~aadamchik/module-dependencies.png
[2] http://objectstyle.org/woproject-old/lists/woproject-dev/
2006/07/0206.html
