Hi Christian,
The situation will be similar to the one we have for the framework: once
the resolver will be stable, we won't have release often as the codebase
will be stable. So IMHO the good points that you raise are "temporary".
I think Guillaume won't agree to move back the resolver in Karaf and
duplicate the code in felix framework and karaf.
For the equinox point, Thomas said that he need some details about one
fix, not that he's against felix resolver.
Let see what the others think, but, at least for now, I would keep as it
is. If it's problematic in the future, we will deal to move back in Karaf.
Regards
JB
On 06/26/2015 03:26 PM, Christian Schneider wrote:
Currently we use the resolver that is embedded into the OSGi framework.
While this is a good way to avoid having duplicated code int the runtime
this approach has some big problems:
1. It takes longer to get resolver fixes or enhancements into karaf as
we first have to get a release of resolver and then of the framework.
Equinox releases are only every 6 months.
2. Resolver changes need a framework release to be useable in karaf
releases. As some of the changes are only necessary for karaf the
framework maintainers might not do a release just for us.
3. The equinox framework might not contain all changes. I recently
talked to Thomas Watson on the equinox list. For the upcoming equinox
release he told me which changes they include and which they leave out.
So we might have the situation that feature resolution works differently
depending on which framework you choose.
So I wonder if we should switch back to embedding the resolver into
feature core.
Christian
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
