If all you want to do is ensure that the child2 is not deployed to the maven repo, then you would turn on the http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#skipparameter in that module, ideally by using a release profile and having that release profile with a definition in the release root and child2. the child2 definition will turn on skip for deploy.
On 19 July 2011 08:18, Hansjoerg <[email protected]> wrote: > Hi > > I'm trying to figure out, how I can exclude a child module from beeing > released to our company repository during the execution of release:perform. > > The situation is this: > parent pom > ... > <modules> > <module>child1</module> > <module>child2</module> > <modules> > > child 2 shouldn't be put directly to the maven repository, so I tried to > reconfigure the release plugin the child2 pom.xml. > > <build> > <plugins> > <plugin> > <artifactId>maven-release-plugin</artifactId> > <version>2.2</version> > <inherited>false</inherited> > </plugin> > </plugins> > </build> > > > In the end I would like to see, that only parent and child1 are released > with the new version into our company repository. However, child2 gets > "released" as well. I also tried to overwrite the configuration for the > deploy plugin, but that doesn't work as well. > > So my question: Does anybody have an idea, how I could exclude a > Child-Module from beeing released to the company repository during the run > of release:perform? > > Thanks. > Hansjoerg > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-to-exclude-a-child-module-from-being-released-during-release-perform-tp4611383p4611383.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
