Thanks for your advise. One more question, the following is our project maven
structure. There are too many pom exist after deploy. For example, not only
the ear pom.xml deploy to artifactory, but also the console A pom , the
console pom and the parent pom. They separate to different directories.
Therefore, I want to reduce the layer of the this structure. Could you mind
to give me some idea again ?
Many thanks
Parent
L---console
L----console A
L---<module> ear file
L--- pom for build ear
L---<module> war file
L ----pom for build war
L----console B
L---<module> ear file </module>
L--- pom for build ear
L---<module> war file </module>
L ----pom for build war
L---server
L----server A
L---<module> ear file
L--- pom for build ear
L---<module> war file
L ----pom for build war
L----server B
L---<module> ear file </module>
L--- pom for build ear
L---<module> war file </module>
L ----pom for build war
--
View this message in context: http://maven.40175.n5.nabble.com/skip-deploy-maven-parent-pom-to-artifactory-tp5790174p5790256.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
|