Hi Bill,
You nailed it right. See more comments inline.
On Jul 20, 2006, at 10:46 PM, Bill Dudney wrote:
Module Dependencies
cayenne-core - external stuff
cayenne-core-java-1.5 cayenne-core
cayenne-remote cayenne-core
cayenne-server cayenne-core, cayenne-remote
cayenne-server-java-1.5 cayenne-server
cayenne-jpa cayenne-server (shouldn't this be cayenne-core-
java-1.5?)
Actually cayenne-core-java-1.5 and cayenne-server-java-1.5 are
optional runtime dependencies for modules that use cayenne-core and
cayenne-server respectively (i.e. nothing from the cayenne-*-1.5 is
imported anywhere else at the moment). In Maven terms this probably
means that this is a complimentary *runtime* dependency that always
goes together with compile dependency of the corresponding 1.4 piece.
cayenne-webobjects cayenne-core
modeler-plugin swing-plugin, cayenne-webobjects, cayenne-server
swing-plugin plugin-launcher
plugin-launcher - external stuff
A question - in my previous message I split "core" modules and the
"modeler" modules in separate subdirectories, adding another level of
nesting just to keep it logically organized. This is escpecially
important when in the future develop more Modeler plugins.
Is this something that will cause grief with Maven?
We have 3 Assemblies:
Generic Java Runs Anywhere (modeler without platform specific
launcher)
OSX Cayenne Modeler Launcher
Windows Cayenne Modeler Launcher
Agreed.
There is one piece remaining that I just though of - the static docs,
release notes and such. Where would that go? Probably a separate module?
You can also get a free copy of 'Better Builds With Maven' from here;
http://www.mergere.com/m2book_download.jsp
Yeah, this one has been rather helpful for me.
Andrus
