Yes, it is a SNAPSHOT dependency. I've solved the issue, the snapshot repository hosted with artifactory was configured as followed:
Advanced/Maven Snapshot Version Behavior: Deployer - 5 Max Unique Snapshots. After changing to non-unique and deploying the projects again, maven didn't override the newer versions. It seems like maven 3.0 has problems to resolve unique snapshots. -----Ursprüngliche Nachricht----- Von: Antonio Petrelli [mailto:[email protected]] Gesendet: Freitag, 12. November 2010 09:52 An: Maven Users List Betreff: Re: Maven overrides up to date artifacts 2010/11/11 Moser, Christian <[email protected]>: > I've got the following problem with maven 3.0 and artifactory 2.2.3 (2.2.1 > won't let maven 3.0 deploy without legacy-mode flag --> metadata problem). > A quick look in the maven output shows that at the beginning of the build > maven downloads an old, already deployed version of Project B into the local > repo and overrides in the process the version of project B with the new class > installed --> so build fails! Curious. Can you post the dependency here? Is it a snapshot dependency? Did you try using -o parameter? Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
