[
https://issues.apache.org/activemq/browse/SMX4-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated SMX4-332:
------------------------------
Attachment: nmr_patch2
Thanks Chris,
I missed a few files in that first NMR patch, so I've attached another for you
to apply (nmr_patch2).
BTW the first nmr_patch and nmr_create_patch were intended to be
either-or-but-not-both (depending on your preference for applying via the patch
command or the svn-apply script).
All should build once the latest patch is applied, though I've seen some
flakiness in the assembly phase (may be environment-specific).
While looking into this, I notice there are still dependencies in some of the
META-INF/Spring configs on the old kernel-style gshell, so I'll have to figure
out how to replace this with the Karaf-specific NamespaceHandler for
command-bundles etc. This looks blueprint-specific in Karaf, as opposed to the
Spring BeanDefinitionParser-based mechanism in kernel.
This raises the general question of co-existance with Karaf's usage of
blueprint service. IIRC Guillaume intended that co-existance with Spring-DM
would be supported in Karaf, I just need confirmation that this is indeed the
case and do the appropriate testing. In the longer term , I guess the goal
would be to switch NMR and features over to blueprint also?
> Port SMX4 nmr and features over to karaf
> ----------------------------------------
>
> Key: SMX4-332
> URL: https://issues.apache.org/activemq/browse/SMX4-332
> Project: ServiceMix 4
> Issue Type: Task
> Affects Versions: 4.1.0
> Reporter: Eoghan Glynn
> Assignee: Eoghan Glynn
> Fix For: 4.1.0
>
> Attachments: features_patch, nmr_create_patch, nmr_patch, nmr_patch2
>
>
> Replace dependencies on the old SMX4 kernel with corresponding dependencies
> on Karaf.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
