[ https://issues.apache.org/activemq/browse/SM-563?page=all ]
Philip Dodds resolved SM-563.
-----------------------------
Fix Version/s: 3.0-M3
Resolution: Fixed
Fix for SM-563 - its not pretty but it does work - basically the maven-project
is not maintaining the order of the dependencies on the model - therefore we
re-parse the model to get it back to its original state and thus back in the
correct order. This issue with Maven has been fixed and should be available in
2.0.5 (commented the code to note this).
> service unite declaration orderi in jbi.xml does not correspond to the
> service assembly pom
> -------------------------------------------------------------------------------------------
>
> Key: SM-563
> URL: https://issues.apache.org/activemq/browse/SM-563
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Affects Versions: incubation
> Reporter: Raffaele Spazzoli
> Fix For: 3.0-M3
>
> Attachments: sample-sa.zip
>
>
> I declare the following ordering in service assembly pom:
> 1,2,3,4
> and the generated jbi.xml has the following order
> 1,4,3,2
> This is a problem when there are dependencies between service unit.
> I think the jbi maven plugin can be fixed to preserve the order, nevertheless
> I suggest to use maven dependency mechanism to deduct the right order.
> So if su2 depends on su1 in its pom there should be dependency to su1 just
> there is a dependcy to its component.
> I attach the example that gives the error to me. Note that:
> 1. you'll find a referred component that I'm developing so the project is non
> deployable. Should not be necessary to debug.
> 2. I don't use the dependecy form su to component, but the property
> declaration. The dependency give me problems that I still don't understand.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
