Ralph Goers wrote:
If I read you right, then I have to treat Maven 2 as if it is Maven 1
and self-discover what all my project's runtime dependencies are going
to be?
Our configuration management dept requires that all our projects use the
same versions of xerces, xalan, etc. This is controlled via the
build.properties file. Putting it in each project's POM still leads to
the possibility that other projects will use different versions.
So it sounds like I have to have a dependencyManagement section in a
master pom and then each project has to specify all its dependencies and
this will then cause the versions specified in transitive dependencies
not to be used?
Ralph
Its an interesting problem. The goal of the maven2 team is, presumably,
to have pom files that contain everything you need to know about versions.
Personally (and this is under Ant), I tend to create the .pom files on
the fly from my templates, using the <echoxml> command to generate the
file inline, after loading in all versions. Its kind of messy, but it
works. Sounds like maybe you need something similar for m2, something to
take a stub .pom file and expand its properties to create the pom file
used for that particular build, a kind of preprocessor...
-steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
