Thanks Benson. I start to like option C, actually ;) Dawid
On Thu, Apr 28, 2011 at 2:47 PM, Benson Margulies <[email protected]>wrote: > I have no experience with success in any model but the following if > you want to share a parent pom between things that are *not* released > together. > > Model A: > > 1) The parent is its own project. You release *it*. You don't allow > the others to find it by <relativePath/> > 2) The only things grouped under an aggregate project are released > together. > > Model B: > > 1) The parent and the other things that are commonly released are an > aggregate/child set, release together. > 2) The others do not live under the parent, and consume it from > releases without <relativeParent/> > > Model C: > > Just release all of it. > > > > On Thu, Apr 28, 2011 at 3:50 AM, Dawid Weiss > <[email protected]> wrote: > > You're among my Maven gurus, so I dare to ask the question here ;) > > > > I was fiddling with a multi-module project, where certain modules (such > as > > tests, benchmarks or other stuff) need not be released to maven central > > repos. What I would like to achieve is this: > > > > 1) single parent POM so that information can be pushed to submodules, > > 2) single parent POM so that mvn compile, mvn test, etc. all descent to > the > > entire project structure, > > 3) functional maven release plugin that does not deploy certain > submodules. > > > > So far I have a parent property in the parent pom that configures > > maven-deploy plugin's skip configuration property. Submodules that don't > > need to be released override this property. > > > > Is there a better/ more graceful way to achieve the above? > > > > Dawid > > > >
