[
https://issues.apache.org/activemq/browse/SM-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45156#action_45156
]
Gert Vanthienen commented on SM-1455:
-------------------------------------
servicemix-utils and servicemix-services have been moved out of the 3.3
container and into their own project at
http://svn.eu.apache.org/repos/asf/servicemix/utils/trunk/
The 3.3 container, the shared library and the binding components' pom.xml files
have all been updated to use the new JBI spec and servicemix-utils bundles
instead.
For most artifacts, this means it now only needs a <scope>test</scope>
dependency on a container. The only classes forcing us to keep using the
previously released container JARs for some artifacts are
{{MessageExchangeListener}}, {{JbiContainer}} and {{ComponentMBeanImpl}}.
Would it be worth biting the bullet while we are at it and also figuring out a
way to migrate those classes outside of the container?
> Reduce dependency cycle between ServiceMix 3 container and the components
> --------------------------------------------------------------------------
>
> Key: SM-1455
> URL: https://issues.apache.org/activemq/browse/SM-1455
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 3.3
> Reporter: Gert Vanthienen
> Priority: Critical
> Fix For: 3.3
>
>
> Currently, building the components depends on a successful build of the
> container and vica versa.
> We should reduce this dependency cycle as it is impossible to do a release
> this way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
