I encountered similar problem when upgrading from M2 to M3. The cause was 2 different versions of Hibernate jars on the classpath. It seems M3's transitive dependency resolution is more inclusive (more accurate?!). You may need to exclude a transitive dep (or drop use of an unnecessary dep). For conflicts like that, the offending dep's POM config sometimes benefit from scope adjusting, perhaps to "optional", to prevent same problem for others.
On Tue, Jan 18, 2011 at 3:07 AM, Marc Rohlfs <[email protected]> wrote: > See the Maven 3 compatibility note on dependency resolution: > https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-DependencyResolution. > It suggests to inspect the dependency tree that is printed when running > Maven in debug mode. > > On 18/01/11 04:17, 刘勇坡 wrote: >> >> Can you tell me what I can do? and why a project work with maven2 well >> can't not be build with maven3? > > --------------------------------------------------------------------- > 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]
