I've been spending a little time trying to work out the issues with maven that require Cayenne to be installed. I have some hunches, but would like to ask some questions to make sure I don't mess things up:
1. The top level pom (cayenne-parent) has a module "framework". The framework (cayenne-framework-parent) pom has a parent "cayenne-parent" and has a module "cayenne-tools". The cayenne-tools pom has a parent "cayenne-parent" rather than "cayenne-framework-parent". That is, modules represent the children, and parent should be the reverse of that. But in this case, the parent points to the grandparent. 2. Why are there inconsistent groupids? org.apache.cayenne.parents and org.apache.cayenne. Can we just have one groupid for the entire project? 3. Why is the version in the 3.0 poms still referring to 3.0-SNAPSHOT, rather than 3.0-BETA1? And why do we have to change that in 20 files? Can't maven inherit from the top pom somehow? 4. Will changing the above things be disruptive to the maven universe now that artifacts have already been deployed? Because I still don't understand why maven does things a particular way, I could be off base, but my guess is that fixing (1) will resolve a few problems [1]. Ari [1] 'install' is always required for every build if you are going to get reproducible results, and I just can't get Clover to work. -- --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
