Version differences between what assembly sees and manifest class path

[Robert Nicholson <ro...@gmail.com>]

So I have hibernate-core 3.6.10.Final and it depends on jta1.1

and the assembly picks up jta1.1 correctly but the MANIFEST.MF file constructs
a class path with jta1.0.1b

Is it unreasonable to expect that the classpath in MANIFEST.MF  be inline with what assembles that package the zip see?

ie. 1.1 is put in the zip and 1.0.1b is referenced in the MANIFEST.MF thus at run time it doesn’t find
the classes needed for jta leading to NoClassDefFoundErrors

mvn dependency:tree doesn’t show jta 1.1 but shows jta1.0.1b




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org