[
https://issues.apache.org/jira/browse/FELIX-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269337#comment-17269337
]
Karl Pauls commented on FELIX-6282:
-----------------------------------
Hi [~pderop],
I'm not necessarily against doing an update and some kind of release in the 0.x
version range - however, as we discussed before, it is becoming a little
confusing to still have a "connect" when there is now something with the same
name from OSGi. The "OSGi connect" spec in R8 is supposed to address the use
cases that our old "connect" was addressing - hence, can you maybe give some
details on your use case and/or say something about why you couldn't switch to
the OSGi R8 way of doing it (the newest framework 7.0.0 does implement it)?
Again, not saying I'm against it - I just think it would be much better if you
could switch to R8 with Felix 7.0.0 and maybe use atomos instead of the old
connect. I'd be certainly willing to look into issues if something would be
missing and I'm sure [~tjwatson] would help us as well.
> 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)
