Thanks Paul, good spotting. We should be ok and my read is that no change is required by us. We have the project in our Required Plugins but only to make the Batik engine happy. We fall into the category, "If you are only including this bundle in your project because you use the Batik APIs, then you probably have little to worry about. " We also don't import packages from it (one of the cited problem cases).
Btw, when Batik 1.7 clears IP review it was my intention that we move up to it as it has a number of known fixes. Kevin Paul Webster <[email protected]> Sent by: [email protected] 02/03/2009 09:34 AM Please respond to E4 Project developer mailing list <[email protected]> To E4 Project developer mailing list <[email protected]> cc Subject [e4-dev] [CSS] Batik and CSS, org.w3c.css.sac_1.3.0 >From Cross Projects Dev: http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg02998.html "If you use the org.w3c.css.sac_1.3.0.qualifier bundle from Orbit, which comprises part of Apache Batik 1.6, then there is an imminent change that you may need to be aware of..." See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=189139#c18 Is this something of concern for us? Do we use Import-Package where possible (where the exporting bundle versions the packages)? -- Paul Webster Hi floor. Make me a sammich! - GIR _______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
