It should not occur that the older version is included if you specify a new version directly in your pom. Can you provide more details? Also, make sure the older version is not your source tree (for instance, already in src/main/webapp/WEB-INF/lib from running war:inplace or something like it)
- Stephen On 7/2/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote:
I have a project which is dependent on a resource we'll call "X". X is dependent on a resource called "Y", so in my pom, I am only specifying the direct dependency on X. My project builds a WAR, and when packaged, X and Y are included. Everything's fine so far. But it turns out, for various reasons, I actually need a newer version of Y, than the one that X is specifying. If I specify the newer version of Y in my pom.xml file, when packaged, both versions of Y are included -- not what I want. So if I specify both versions of Y in my pom.xml file, and list the scope of the older version as "provided" and the scope of the newer one as "compile", neither one is included. How can I get maven to include only the newer version of Y when packaging my WAR? Thanks, Brad --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
