[
https://issues.apache.org/activemq/browse/SM-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45120#action_45120
]
Gert Vanthienen commented on SM-1455:
-------------------------------------
Having looked at this again, I think we should be moving some things out in
their own space:
- we move the JBI spec jar to the specs project (as a shared dependency for
SMX3, SMX4 and the components)
- we create a servicemix-commons jar to hold some basic helper classes (like
XML Source implementation, FileUtil, ... and the like) (this thing will go into
both containers and the shared library)
After this, we can get to the point where
- the components can be build without any reference to a previously released
container, they only need the JBI spec and shared library (with the common
stuff in there)
- we can use any container version as a <scope>test</scope> dependency for
integration/unit testing
- both containers can be built independently (now, SMX4 assembly pom.xml has a
dependency on 3.3-SNAPSHOT's servicemix-utils
Wdyt?
> 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.
