[
https://issues.apache.org/jira/browse/FELIX-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269441#comment-17269441
]
Pierre De Rop commented on FELIX-6282:
--------------------------------------
Hi Karl,
I do agree, it may be confusing to release the old connect while the official
Felix 7.0.0 available.
It's just that we have some products which are still based on old felix
connect. We'll migrate them to the new official Felix 7.0.0 , and probably to
Atomos, but the work is not yet started. That's why a 0.x release could help
temporarily, until we do the switch to R8 (and probably to Atomos).
but I do agree: better is to switch now to R8, and not use the old felix
connect. We will do this, you can close this jira.
By the way, is Atomos officially released to maven central ?
> Felix Connect R7 support
> ------------------------
>
> Key: FELIX-6282
> URL: https://issues.apache.org/jira/browse/FELIX-6282
> Project: Felix
> Issue Type: Improvement
> Components: Connect
> Affects Versions: connect-0.2.0
> Reporter: Pierre De Rop
> Assignee: Pierre De Rop
> Priority: Major
>
> The Felix Connect library seems to be almost ready for OSGi R7 support.
> At least, modifying the project's pom in order to depend on
> org.osgi:osgi.core:7.0.0 allows to use recent declarative service,
> configadmin, metatype, etc ...
> There is one minor issue: the support for FrameworkWiringDTO is missing (even
> if it's not really useful in the context of felix connect): in the following
> code, the adapt method returns null:
> {code:java}
> Bundle system = _ctx.getBundle(0);
> FrameworkWiringDTO wiring = system.adapt(FrameworkWiringDTO.class);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
