Community
Participate
Working Groups
We are working on upgrading BIRT Eclipse Platform to 4.12 Eclipse Release and when we assemble the plugins from the repositories, we have a mixed scenario where some of the batik plugins are 1.11.0 (from eclipse) and some 1.9.1 (BIRT). Plugins like “org.apache.batik.util” are in duplicate (1.11.0 from eclipse and 1.9.1 from BIRT core). In OSGI, this is not an issue – but the problem is that some of the Orbit Batik Plugins do not specify a version binding and at runtime, these are getting bound to the wrong version of the Batik plugins. This is causing a runtime exception in our application and export to PDF feature is broken.