I think this is an interesting idea, David. The Maven Tycho plugin does an OSGi-aware compilation, and there might be something there we can start from. Tycho itself isn't right for us, because it's a manifest-first technology - it works from a special bundle-aware repository and the manifest of the bundle being compiled, and we don't have either of those! However, there might be something in the compilation mechanism that we could re-use/cannibalise/draw inspiration from. In the worst case a two phase compilation with Tycho working from the manifest generated by bnd might add *some* value, although it would be pretty tortuous.
Holly --- Want to read more? http://www.manning.com/cummins/ - Enterprise OSGi in Action On Thu, Nov 24, 2011 at 7:14 PM, David Jencks <[email protected]> wrote: > We've had some problems lately with stuff like packages no longer being > exported and this turning out to break other projects. I've been wondering > what would make problems like this more visible sooner and also wondering > what could be done to make maven more osgi friendly. So, here's an idea that > might or might not be workable or useful. > > The eclipse compiler lets you supply a classloader as the "parent" rather > than the javac requiring that you supply a classpath. So what if there was a > maven compiler configuration that would supply a classloader to the eclipse > compiler that worked with the maven dependencies as bundles, i.e. was a > bundle classloader for a more-or-less fake bundle that imports all the > exports of the maven dependency bundles? > > thoughts? > > thanks > david jencks > > > >
