Rule of thumb: If you feel like you are fighting Maven then either:
1. You are doing it wrong, do it the Maven way and you won't be fighting; or 2. You maybe should be using a different build tool that does not have its own "way". In your case you are probably trying to double-use the deploy plugin to "ship" your jars rather than what it is intended for, i.e. deploying artifacts to a maven repository. Use a different plugin to "ship" your jars... one plugin that I use for these cases is the ship-maven-plugin. A maven repository is built on the assumption that every GAV has a pom deployed, you are trying to break that assumption and hence fighting maven. -Stephen On 29 September 2011 13:21, Nazia Ghawte <ngha...@premierfarnell.com> wrote: > i have tried again but with no success. the main reason for the POM not to > be > deployed because it is only needed when i run the parent project,where as > the child modules are independant of each other and can be built on their > own as well.the parent module is only needed to be built if we want all the > artifacts in the project to be freshly built all at once. > Any solutions? > > -- > View this message in context: > http://maven-users.828.n2.nabble.com/Skip-Pom-deployment-tp6843439p6843668.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 > >
