You mean that if you run twice the exact same command, you get two
different results? Then there is something really wrong with your project.
Anyway, let's say you have a project with the following structure:
* Root
o A
o B
o C
in Root, you declare the 3 modules A,B,C (aggregation), and in A,B,C,
you declare Root as their parent (inheritance).
If you run 'mvn deploy' from Root, all four projects should get
deployed. If you run 'mvn deploy' from A, B or C, then only A, B or C
should get deployed. Isn't this what you are looking for?
Guillaume
Le 29/09/2011 14:30, Nazia Ghawte a écrit :
ok, one revelation here.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.7</version>
<configuration>
<skip>${skipDeploy}</skip>
</configuration>
</plugin>
On changing the plugin version from 2.4 to 2.7 the artifact deployment was
skipped for the first time,but it agin got deployed on running the deploy
command for the second time.
--
View this message in context:
http://maven-users.828.n2.nabble.com/Skip-Pom-deployment-tp6843439p6843702.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]
