Re: [cross-project-issues-dev] Do you use org.w3c.css.sac bundle fromOrb

["Christian W. Damus" <cdamus@xxxxxxxxxxxxx>]

Hi, Xiaoying,

No.  AFAIK, Batik 1.6 may well require the changes that the Batik team  
made in the SAC API, so it should continue to use the older  
org.w3c.css.sac_1.3.0.qualifier bundle.

Of course, in a Galileo workbench, it is very possible that multiple  
versions of Batik would end up being deployed together.  I think that  
I may need to change the Batik 1.6 bundles to force the 1.6 versions  
to bind to the old SAC bundle despite the installation of the new  
SAC.  Matching attributes should help with that; I need to read up on  
the OSGi manifest ...

In any case, I shall need the help of adopters like GMF and BIRT in  
testing the co-deployment scenario, as I am clueless about the usage  
of Batik.

cW

On 4-Feb-09, at 4:26 AM, Xiaoying Gu wrote:

> Hi Christian,
>
> Do we need to update to use org.w3c.css.sac_1.3.0.w3c_qualifier, if  
> we are still using Batik 1.6?
>
> Thanks,
> Xiaoying
>
> -----Original Message-----
> From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx 
> ] On Behalf Of Christian W. Damus
> Sent: 2009年2月3日 21:59
> To: Cross project issues
> Subject: [cross-project-issues-dev] Do you use org.w3c.css.sac  
> bundle fromOrbit?
>
> Hi, all,
>
> I didn't want David to be the only spontaneously self-confessed OSGi
> sinner in Orbit, this week.  ;-)
>
> 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.  If you are only including
> this bundle in your project because you use the Batik APIs, then you
> probably have little to worry about.  If you use the CSS API
> independently of Batik, then please read on and comment if you have
> concerns.
>
> As I explained in Orbit Bugzilla and the mailing list:
>
> http://dev.eclipse.org/mhonarc/lists/orbit-dev/msg00987.html
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=189139#c18
>
> I failed to execute the level of diligence required in tracking the
> pedigree of the W3C SAC packages that were re-distributed with Apache
> Batik 1.6 when I originally bundled it in Orbit.  In preparing to
> contribute Batik 1.7 to Orbit, I discovered that Batik changed over to
> using a different source of the W3C SAC, which provides the original
> W3C code.  The code that I bundled in Orbit for Batik 1.6 had been
> modified by the Batik project, introducing API-incompatible changes as
> compared to the original W3C API.
>
> So, the current proposal to resolve this problem is to define a new
> W3C SAC 1.3 bundle thus:
>
> org.w3c.css.sac_1.3.0.w3c_qualifier
>
> which is lexicographically higher than the current bogus bundle
> version, while still retaining the original specification version
> number.
>
> For consumers of this bundle using Require-Bundle, this change should
> just mean that you bind to this new bundle and all will be well,
> *unless* you are using the non-standard Batik variations on the W3C-
> specified API.
>
> If you are using Import-Package to bind to the org.w3c.css.sac package
> specifically, then please let me know, because that will influence how
> the package exports are expressed.
>
> Thanks for your attention,
>
> Christian
>
> --
> Christian W. Damus
> Senior Software Developer, Zeligsoft Inc.
> Component Lead, Eclipse MDT OCL and EMF-QTV
> E-mail: cdamus@xxxxxxxxxxxxx
>
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Christian W. Damus
Senior Software Developer, Zeligsoft Inc.
Component Lead, Eclipse MDT OCL and EMF-QTV
E-mail: cdamus@xxxxxxxxxxxxx