On 9/24/2010 2:08 PM, Antonio Petrelli wrote: > 2010/9/24 Marshall Schor <[email protected]>: >> The top pom and all the poms in the submodules have version numbers >> 2.3.1-SNAPSHOT. >> The top pom has *some* of the submodules also listed as <dependencies>, with >> the >> 2.3.1-SNAPSHOT version. > This does not make any sense, this is a circular dependency,
Can you please help explain where the "circularity" comes in? Are you assuming that the sub-modules have a reference to the top pom? (Maybe you assumed they used the top pom as a parent? - but they don't). > and a pom > project usually (I'd say *always*) does not need dependencies at all. Yes, in this case, I think you're right, and I could remove these dependencies in the top pom. (They were put in at one point I think when we were contemplating an alternative release strategy). But I don't think that would change my outcome (see below). > I suspect that one ore more modules depend on others. They do. They have inter-module dependencies. They build just fine. The release:prepare does invoke a build of all the submodules, and they all build OK. The only thing that doesn't seem to be happening is the updating of the pom versions on those subprojects, which I (maybe incorrectly) assumed the release plugin would do. It does update the versions ok on the top pom (only). Thanks for your help. -Marshall Schor > You have to add > dependencies to those modules, not in the pom project. > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
