+1 However, it anyhow raises a different question, which is related to how we manage the ranges. The problem is that the maven plugin computes the range up to the next major version, which means each time we upgrade a dependency, we can't use an older one anymore, even if it would work. That would be an extra work to do however, as we'd have to split the maven dependencies from the lower version of the dependencies we can work with.
On Mon, Jun 4, 2012 at 9:43 AM, Jean-Baptiste Onofré <[email protected]> wrote: > Hi all, > > I updated Karaf trunk (3.0) to use OSGi Compendium 4.3.0. It means that now, > Karaf trunk uses both OSGi and OSGi Compendium 4.3.0 (whereas previously it > used OSGi 4.3.0 and OSGi Compendium 4.2.0). > > However, to "simplify" version range, I think it makes sense to not depend > from OSGi Compendium but directly from the service implementation itself > (for instance Felix ConfigAdmin, etc). As we already manage the version of > service implementation, I think OSGi compendium dependency is superfluous. > > I raised: > https://issues.apache.org/jira/browse/KARAF-1518 > > WDYT ? > > Thanks > Regards > JB > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ FuseSource, Integration everywhere http://fusesource.com
