>> One thing I have been toying with for a while is to auto-magically >> extend maven-jar-plugin to add the OSGi headers.
> I really don't think this is a great idea. I think for a bundle to be useful > someone needs to provide proper imports and exports. Right, but it make took years ;( >> I haven't given a lot of thought into what I need to do, but if I >> recall correctly, getting a simple OSGified jar isn't much work and if >> Maven did this out of the box then the maven repository would become >> OSGified over time as projects release their artifacts. > We've toyed around with this idea, but if you want something useful I think > it's really hard to infer something useful. Making a manifest that is > workable with OSGi is not that hard and the author of a package is probably > the person to do it. I think what we can do is give a brief guideline as to > what's commonly expected and help people create correct and useful bundles. > Maven central is the biggest bundle repository in waiting :-) So you recommand education and lobbying. May be ASF should show the way, there is tons of projects today still not OSGIfied in ASF repo. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
