On 3/14/07, Eric Crahen <[EMAIL PROTECTED]> wrote:
On 3/14/07, Xavier Hanin <[EMAIL PROTECTED]> wrote: > > On 3/14/07, Eric Crahen <[EMAIL PROTECTED]> wrote: > > > > One thing that the Spring-OSGi guys are working on is a way to leverage > > the > > dependency information within Maven pom's to extrapolate OSGi > > dependencies. > > > I haven't checked their work in detail for the moment, so I may be wrong, > but the problem I see is that you have information in an osgi manifest > that > can't be found in a maven pom nor an ivy file: exports. That's why I think > with Ivy it would be better to use directly OSGi manifest if we can get > enough metadata from it. > > The goal being not to have to duplicate the dependency information. > Right, I think there is a subtle difference in what we're talking about * OSGi - > Ivy adapter for Ivy. I think the only thing that makes what we are talking about different is that I think you are saying you want Ivy to be able to understand OSGi so you have one more place for information. This helps someone who uses Ivy leverage a component that is OSGi ready; but it doesn't necessarily help someone using OSGi-Spring. USE-CASE: I have a project with dependencies that are have no Ivy descriptors and have no Maven descriptors. For some reason they do have OSGi descriptors and I'd like to leverage that. * Ivy->OSGi adapter for OSGi-Spring. What I'm saying is that OSGi-Spring is coming at the problem the opposite end. They want OSGI-Spring to be able to understand Maven, or in our case Ivy. This helps someone using OSGi-Spring leverage a component from Maven or Ivy even if that component doesn't contain OSGi descriptors, which there are various reasons for. It doesn't let someone using Ivy suddenly have more artifacts at thier disposale, but it does make it so that if you are using OSGi-Spring you can use anything thats Ivy ready. USE-CASE: I wrote OSGi component. My OSGi component has a ton of transitive dependencies. These all better be OSGi ready or I will have problems and I'm going to have to go off and transitively make all my dependencies OSGi ready. This is not good - but many components already have Ivy or Maven descriptors, wouldn't it be great if OSGi could just speak to pom.xml or ivy.xml and figure things out. This enables people to leverage Ivy who may not even be using it themselves. I might do everything by hand with ant, but when I slam everything into my OSGi-Spring container, the container is smart enough to figure out my dependencies for me using Ivy information.
Ok, thanks for the clarification. So I think both would be useful, and the second is something that would need to be contributed to Spring-OSGi. Speaking about OSGi, I think we would also need to discuss with Felix team, I think they provide a maven 2 plugin, maybe we should see what it does and if this is something that could be achieved with Ant+Ivy. For the moment, I consider these topics as very interesting, but I don't have enough time myself to invest in them. But if somebody want, I'd be glad to help whenever I can. - Xavier --
- Eric
