-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
IMO, maven should probably create a resolved pom as part of the
build
process and deploy that along with the artifact, but I don't have
time
to figure out how to make it do that.
This was done (briefly) in a few Maven
What kind of problems was it causing? Something to do with the idea of
creating a resolved pom, or bugs in the implementation?
Will it be added back in? If so, is there any timeline for doing so?
Feel free to read the JIRA and the related JIRAs:
http://jira.codehaus.org/browse/MNG-2971
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Apache CXF has several poms that follow this pattern:
properties
jetty.version6.1.24/jetty.version
/properties
...
dependencies
dependency
groupIdg/groupId
IMO, maven should probably create a resolved pom as part of the build
process and deploy that along with the artifact, but I don't have time
to figure out how to make it do that.
This was done (briefly) in a few Maven versions and it caused a lot of
problems, so it was pulled out/disabled.
Apache CXF has several poms that follow this pattern:
properties
jetty.version6.1.24/jetty.version
/properties
...
dependencies
dependency
groupIdg/groupId
artifactIda/artifactId
version${jetty.version}/version
/dependency
/dependencies
