I've very briefly spoken to a couple of people about the feasibility of this. They might pipe up here. I have no idea of the work that's involved, though in theory it should happen.
I am curious why this is needed though - can you explain further? - Brett On 10/6/05, Jorg Heymans <[EMAIL PROTECTED]> wrote: > At Cocoon, we need to add osgi compliant dependency logic to m2. In a > nutshell and simplified for this case : osgi allows archives to > explicitly define which classes they export. > > We think there are 2 possible ways of achieving this: > 1) adding a custom dependency type "osgi", that respects osgi rules > during dependency resolution. > 2) plug in an osgi classloader (eclipse has this component already) into m2. > > > Can anyone comment on the feasibility of these options? > > Regards > Jorg Heymans > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
