That's because the war is an attached artifact. in fact it is most likely the primary artifact of that module.
If you refactor your build so that the webapp module only produces one artifact, then you can use the trick you tried. Best practice in maven is one artifact per module. -Stephen 2010/1/14 rrrrutdk <utdkr...@tom.com>: > > Each time I run 'mvn clean deploy' on my web project, Maven uploads the > generated war file into my public repository. > > Is there any way to disable war file uploading? > > I tried to use this segment: > > <plugin> > <artifactId>maven-deploy-plugin</artifactId> > <configuration> > <skip>true</skip> > </configuration> > </plugin> > > but it cancelled uploading another artifact with a classifier too. > -- > View this message in context: > http://old.nabble.com/How-to-disable-war-uploading--tp27155459p27155459.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
