Conflict of dependency between vraptor versions about vraptor-contrib

[lucascs]

which dependencies are conflicting?

[dtelaroli]

I wanna use Vraptor 3.5.3, but when I execute my project a exception is dispatched (NoClassDef in GsonDeserializer), because the vraptor 3.4.1 is in the classpath.
To solve the problem I add exclusions to all vraptor and plugins dependencies.

Exemple of my dependency config.

Environment plugin 1.1.3
 - Vraptor 3.4.1

Hibernate4 plugin 
 - Vraptor 3.5.0
 - Environment plugin 1.1.2

Simplemail plugin
 - Vraptor 3.4.1
 - Environment plugin 1.1.1

[lucascs]

Are you using Maven, gradle, ivy or some other dependency manager? If so, it should be able to solve the conflicts for you, automatically.

[dtelaroli]

I use maven, but errors happen.
Is it because I use maven modules and the dependencies are added by inheritance?

[garcia-jj]

You can add the <exclusions> tag inside plugin with hell dependency, so Maven will ignore the dependency you have declared.

Since this is not bug related to vraptor-contrib, I'm closing this issue, ok?

If you have questions about how to solve this case, please, send a message to us in our mailing list with a mvn dependency:dependency.

Thank you.