Ahh yes. It won't work because you can only have one default-cli. There are ways around but they get tricky and are rather hacky.
Any reason why you can't just type mvn release:clean -DsomeProperty=... && mvn release:prepare -DsomeProperty=... && mvn release:perform -DsomeProperty=... On 26 February 2014 11:48, Anders Hammar <and...@hammar.net> wrote: > Don't think it's possible. I guess the idea is that if you have the same > parameter in multiple goals, they would have the same configuration. > > If the parameter is configurable from command-line (thourgh a property), > you could do it that way instead. Maybe not what you want, but it would > work. > > /Anders > > > On Tue, Feb 25, 2014 at 4:55 PM, Juergen Hartl <juergen.ha...@jku.at> > wrote: > > > Hi, > > > > with regards to the info given at: > > https://maven.apache.org/guides/mini/guide-default-execution-ids.html > > > > How can I configure separately each Mojo of a plugin, if these mojos are > > executed from command line? > > > > e.g. > > mvn release:clean //SomeProperty == X > > mvn release:prepare //SomeProperty == A > > mvn release:perform //SomeProperty == B > > > > both goals are executed from command line. how can I configure > > release:prepare in my pom differently from release:perform? > > > > Basically I would need execution Ids like "default-prepare-cli", > > "default-perform-cli" etc. > > > > Grateful for ideas, thanks, Juergen > > > > ad: pom.xml > > > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-release-plugin</artifactId> > > <version>2.4.2</version> > > <configuration> > > <SomeProperty>X</SomeProperty><!-- shared globally--> > > </configuration> > > <executions> > > <execution> > > <id>default-cli</id> > > <configuration> > > <SomeProperty>A</SomeProperty> > > <!--DOES NOT WORK shared by release:perform, release:prepare, > > release:clean both if executed from command line--> > > </configuration> > > </execution> > > <id>default-prepare</id> > > <configuration> > > <SomeProperty>A</SomeProperty> > > <!--DOES NOT WORK not used if executed from command line--> > > </configuration> > > </execution> > > <execution> > > <id>default-perform</id> > > <configuration> > > <SomeProperty>B</SomeProperty> > > <!--DOES NOT WORK release:perform not bound to lifecycle, but it invokes > > deploy. Also not used if executed from command line--> > > </configuration> > > </execution> > > <execution> > > <execution> > > <id>default</id> > > <phase>deploy</phase> > > <goals> > > <goal>prepare</goal> > > </goals> > > <configuration> > > <SomeProperty>A</SomeProperty> > > <!--DOES NOT WORK not used if executed from command line--> > > </configuration> > > </execution> > > </executions> > > </plugin> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
