> -----Original Message----- > > In this case, we have something like this: > > //depot/up-svcs-test/rel/R1.0/pom.xml <--- parent > //depot/up-svcs-test/rel/R1.0/A/pom.xml > //depot/up-svcs-test/rel/R1.0/B/pom.xml <--- children > //depot/up-svcs-test/rel/R1.0/C/pom.xml > > Without putting <artifactId>R1.0</artifactId> (and then changing > it for every release) in the parent pom, what should these be?
Your parent POM should have an <scm> connection path of //depot/up-svcs-test/rel/R1.0. > I'm still confused about the relationships here, but will running from > the top level allow me to release a single child module, or will it > attempt them all? No, it will only release all of them. > I like the thought of having the scm entry in the parent pom, and > nothing in the children (and running the release plugin from the top > level) but don't want to release modules just because they are there > (and have no changes since last release). I completely agree however this is not how maven and many other projects are traditionally released. if you want to release a child individually, you either need to ensure that it has its own <scm> element OR its artifactId == directory name. In the above example, the first child's artifactId should equal "A" since that is the directory name. I am planning on a refactoring of the Perforce provider in the next month or two which will make debugging easier and will make the SCM connection heuristic bulletproof (it will fall back to 'p4 where' as a last resort). mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
