I know that M2 has a transitive dependency walker built into it, but it sounds like what you are proposing is for M2's dependency walker to be pluggable; i.e. users can optionally plug in a different dependency resolution algorithm. Am I correct?
> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 06, 2005 9:10 AM > To: Maven Users List > Subject: Re: adding osgi dependency logic to m2 > > 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] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
