[
https://issues.apache.org/activemq/browse/SMX4KNL-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49313#action_49313
]
Guillaume Nodet commented on SMX4KNL-179:
-----------------------------------------
We may consider upgrading to felix 1.2.2 if it can be done seamlessly.
I've just hit https://issues.apache.org/jira/browse/FELIX-606 which is an issue
I reported a long time ago and which was fixed in 1.2.1.
Furthermore,we upgraded to 1.2.1 some months ago, but reverted back to 1.0.4.
I think this revert was unintented (I committed that, but i can't recall any
reason). So I wil upgrade to 1.2.2 for the kernel 1.1.0 release and see how it
goes.
> Upgrade Felix dependency
> ------------------------
>
> Key: SMX4KNL-179
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-179
> Project: ServiceMix Kernel
> Issue Type: New Feature
> Affects Versions: 1.1.0
> Reporter: Chris Custine
> Assignee: Chris Custine
>
> We need to upgrade Felix to a recent version in order to gain some of the
> fixes and OSGi spec features that are not present in the older 1.0.x version
> we are using. I have all of the changes necessary to make this work but I
> have experienced some issues with Felix 1.4.x. I am testing against the
> current Felix SVN code and waiting for the 1.6 release which should work
> better for us. This update will also require a recent Spring DM fix that
> will be in the 1.2 RC and final (its not in 1.2 M2).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
