On 29/03/2011 1:59 PM, Laird Nelson wrote:
On Tue, Mar 29, 2011 at 1:22 PM, Ron Wheeler<rwhee...@artifact-software.com
wrote:
We follow Stephen's path but build aggregation poms that only contain
libraries so that our project POMs only depend on our libraries.
For example if the war file needs the Apache Commons that we support in our
development environment, the project will depend on the current version of
ours-lib-commons.pom.
Just out of curiosity, where is it written down that one can depend on an
artifact of type pom? I've always been curious about this.
L
In the case that I described, the actual dependency is on the JAR.
The aggregation POM produces a JAR that is deployed in our Nexus and is
available like any other third party library and installed in Tomcat's
/lib as part of the application upgrade.
In the days of cloud servers, a Tomcat dedicated to one application is
pretty easy to defend if anyone questions the possibility of library
conflicts between applications.
Sorry for the confusion.
A bit of sloppy writing.
I will try to defend myself by characterizing my description as "over
abstracted".
We only use scope "compile" or "provided".
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
