I've committed a fix in github that fix all the issues i've found with the OSGi metadata. That's not a small patch because I wanted to use version ranges in most places. Note that the patch on abdera-security also changes a dependency from xalan/xerces to the standard jaxp transform api (I hope it's not a problem). Let me know if you need more info or if anything looks bad to you.
On Thu, Nov 11, 2010 at 00:51, Guillaume Nodet <[email protected]> wrote: > I've raised ABDERA-270 and will attach a patch son. > > On Wed, Nov 10, 2010 at 21:48, ant elder <[email protected]> wrote: >> What you say sounds correct to me and if you can provide a patch that >> would be terrific. Now that the axiom release is out was about to do a >> releases to pick up the performance fixes in ABDERA-267, so it would >> be great to get OSGi fixes in that release as well. >> >> ...ant >> >> On Wed, Nov 10, 2010 at 7:28 PM, Guillaume Nodet <[email protected]> wrote: >>> Not sure if anyone has been successfull with using abdera in OSGi, but >>> the OSGi metadata seems broken for me. >>> If you look at the abdera-core / abdera-parser bundles, they both >>> include the o.a.abdera.parser package, but none is exporting it, >>> meaning they both use their own version of this package. >>> Given the source code for this package is in the core module, i >>> suppose that's the one that should export the package. >>> If that's right, I'll raise a JIRA and provide a patch for that. >>> >>> >>> -- >>> Cheers, >>> Guillaume Nodet >>> ------------------------ >>> Blog: http://gnodet.blogspot.com/ >>> ------------------------ >>> Open Source SOA >>> http://fusesource.com >>> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
