|JasperReport Dependencies [message #1134048]
||Sat, 12 October 2013 07:35
| Jeremie Bresson
Registered: October 2011
I have tried the JasperReport tutorial...|
Thanks to the writer!
I had some difficulties for Part 1, because I oversaw "Add all jars from the lib folder"... In the current version (5.2.0) there are 57 jar dependencies. Each dependency needs to be added. We modified the SDK to support multi select in the FileChooser dialog (Available in the nightly build, will be released with M3).
Because I missed the lib-dependencies during my first tries, I search on Google for OSGi ready bundle of jasperreport. This is something they consider: issues 2811-0.
But this does not solve the problem of dependencies. It seems to me that they use a wildcard import in their MANIFEST.MF:
When creating the bundle with scout, the SDK build a fat-bundle (all dependencies are contained in the bundle). It is a practical solution. Not sure if this can work in a bigger application.
It would be nice to have a real OSGi Bundle, with the real declaration of the imported packages including the appropriate version. Of course this also means that there is a need for OSGi Bundles of each dependency.
In comparison, I also had a look at the "net.sf.jasperreports" bundle provided by Jasper Studio on this update site:
This bundle is too big for my use case... It has dependencies such as JDT...
When I see all the dependencies of JasperReport I also wonder if the legal aspect of the dependencies was checked... With this amount a library, it is not clear to me if they are IP-Clear or not.
Powered by FUDForum
. Page generated in 0.01802 seconds