Thanks for your interest to help me out here, Ron. Let me try to explain more clearly what our current scenario is:
We make use of a company pom that includes everything that may be common to all projects such as the built-in maven plugins (compiler, resources, etc) and nail down the versions there. In our multi-module projects the parent pom for the current project uses the company pom as its parent and this is where project specific dependencyManagment and pluginManagement occurs. We have some in-house plugins in use and these may be in development along side our main project's sprint and therefore we have snapshot versions of the plugins in use while in trunk. It doesnt happen as often but the same thing may occur with the company pom. We finish the current development sprint in trunk and want to cut a release candidate branch using the m-release-p, which works wonderfully by the way. We now have a branch containing snapshots for the previously mentioned plugins and perhaps parent pom. If this is not discovered by the time the RC is accepted and we run release:prepare/perform, this is the point at which we discover the plugins and company pom must first be released. We were wondering if it were possible to optionally catch the use of snapshots of the plugins/parent poms at the time of branching the RC much like prepare/perform does. I hope this clarifies our use case a bit for you, if not please feel free to inquire further. Thanks again, -Ryan On Thu, Mar 11, 2010 at 9:35 AM, Ron Wheeler <rwhee...@artifact-software.com > wrote: > Ryan Connolly wrote: > >> Hi, >> I have a question regarding the m-release-p branch goal. My team was >> wondering if it was possible to disallow snapshot versions of plugins and >> dependencies when creating certain branches, for example a release >> candidate >> branch. They were boping we could catch tbe use of snapshots before >> getting >> to the prepare/perform stage. As our projects are typically multi-module >> and modules may (more specifically, do) depend on one another I'm guessing >> this is not currently supported since module versions would want to remain >> snapshots and it would be difficult to determine the difference between a >> module dependency from any other. Could someone please confirm (or deny) >> my >> suspicions? >> >> I'm hoping this makes sense but if not I would be more than happy to try >> to >> clarify my query. >> >> Thanks. >> -Ryan >> >> >> > Your higher level poms declare what versions they want as dependencies so > they should not be able to cross over to SNAPSHOTS without someone doing > something against company policy. > > It does not seem like a good idea to have people making 1.2 release pom > that calls on a 1.2-SNAPSHOT dependency. > > It is OK to have a 1.2 SNAPSHOT depend on a 1.2 release if your > sub-components can be tested to release state independently. > > Perhaps you can give a more detailed example of how a release could call on > a snapshot artifact in your environment. > > > Ron > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- �...@n
