I just tested with the following pom and it works like a charm:
<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
<modelVersion>4.0.0</modelVersion>
<groupId>x.y.z</groupId>
<artifactId>test</artifactId>
<version>1.0-SNAPSHOT</version>
<name>Test</name>
<packaging>pom</packaging>
<properties>
<skipDeploy>false</skipDeploy>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.7</version>
<configuration>
<skip>${skipDeploy}</skip>
</configuration>
</plugin>
</plugins>
</build>
</project>
However, there is a major flaw in this solution, because you will have
to redeclare the deploy plugin in all your children to indicate that you
want them to be deployed
I feel like this is getting complicated just to avoid the deployment of
a single pom file. Any good reason for not deploying this pom? Maybe
some Maven-guru has a better option?
Cheers,
Guillaume
Le 29/09/2011 13:11, Nazia Ghawte a écrit :
Thanks for your reply.
i have tried putting the following into the parent POM
<properties>
<skipDeploy>true</skipDeploy>
</properties>
but it still doesnt work and the pom gets deployed.
--
View this message in context:
http://maven-users.828.n2.nabble.com/Skip-Pom-deployment-tp6843439p6843521.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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
