On Mon, Jul 7, 2008 at 4:39 PM, Stuart McCulloch < [EMAIL PROTECTED]> wrote:
> 2008/7/7 Wouter de Vaal <[EMAIL PROTECTED]>: > >> >> On Mon, Jul 7, 2008 at 4:10 PM, Niclas Hedhman <[EMAIL PROTECTED]> >> wrote: >> >>> On Mon, Jul 7, 2008 at 10:00 PM, Stuart McCulloch >>> <[EMAIL PROTECTED]> wrote: >>> >>> > and especially for PDE users! ( I just voted for that bug, hope it's >>> fixed >>> > soon ) >>> >>> Also see https://bugs.eclipse.org/bugs/show_bug.cgi?id=239777 >>> >>> Doesn't this hit the Spring bundle repository heavily?? Or they have >>> already anticipated and done work-around? >> >> >> I've just browsed their repository ( >> http://www.springsource.com/repository/app/) >> and it looks like they have killed the use of dashes in any of their >> bundles. Looks like >> they had seen it coming. >> > > guess so - note that they also have their own groupId / artifactId scheme > which can vary a lot from the original (cf. the Apache Commons bundles) > > they're effectively providing a clean, refactored subset of the Maven repo > > not sure how scalable this will be in the future - or how this might affect > people switching between Spring-ified artifacts and the original bundles > because of the change in groupId, artifactId and the dependency tree... > I'm not using it yet, but I guess I would have to update about 30 poms to pick the changes up, after that If you just import packages and not bundles, there shouldn't be a problem. I would rather see that people would update their manifests so all external bundles would already be osgi ready, and a lot are nowadays, which I think is cool and a great recognition of OSGi. For now I'm just happy using the pax construct way, so I just hope the pde guys will fix this very annoying bug. Thanks for the support, Wouter
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
