Dependency problems in net.sf.jasperreports:jasperreports:6.3.0

Why on earth does your bugtracker kill line formatting?

try 6.3.1

Same result.

Changed Status from New to Feedback Requested

Changed Assigned User from - to @teodord

---

Hi,What do you think would be an appropriate solution for this problem? I never used this Maven plugin and I'm not sure what it does and why its warnings matter.Thanks,Teodor

Hi,

in theory, the plugin is used to prevent your project from referencing different versions of the same artifact (even transitively), so that you don't end up with Java's version of DLL-hell. In case of Jasper, the plugin throws warnings for it on it's own, as different parts of the library depend on different versions of the same libs (see messages above).

The best solution would be to unify those versions to a common standard. Usually, that is managed by defining a dependencyManagement block in the root or parent pom.xml. (In this case for commons-collections and commons-beanutils.)

 

Best regards,

Nicholas

Hi,

 

I probably don't get this right. Is there an actual problem with the dependencies that our pom.xml brings, even transiently?

I read about the dependencyManagement block in the Maven documentation and it seems to be related to projects having parent artifacts and sharing dependencies. Not sure if it is the case with JasperReports library at the moment.

 

Thanks,

Teodor

 

Sorry,

I haven't used JP in a long time. This ticket is more than three years old...

 

If you don't have a common parent pom, it at least explains the broken dependencies. In general: This doesn't have to break anything unless the wrong library version is picked by Maven.

 

It's still bad practice, though.

 

Nicholas

Changed Resolution from Open to Won't Fix

Changed Status from Feedback Requested to Resolved

---

Hi,If solving this means adding to our pom.xml the exact version for every possible transient dependency we might get, even if marked as optional, then I'm afraid we are just not going to do it. I prefer to keep the pom.xml minimal, especially since we are not facing an actual error here, as far as I can tell.Thank you,Teodor