many thanks
On Tue, Jul 19, 2011 at 6:38 AM, Simon Nash <[email protected]> wrote: > Mike Edwards wrote: > >> On 18/07/2011 20:39, Juri Vrljicak wrote: >> >>> I saw related posts but couldn't find a solution to this problem. Can >>> anyone please clarify me if >>> this is an issue in 1.6.2? >>> >>> https://issues.apache.org/**jira/browse/TUSCANY-3012?page=** >>> com.atlassian.jira.plugin.**system.issuetabpanels:all-**tabpanel<https://issues.apache.org/jira/browse/TUSCANY-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel> >>> >>> Because I am experiencing this in a test case. If so what would be the >>> suggested course of action? >>> >>> >>> thanks >>> >>> >>> Juri, >> >> I assume that you're using 1.6.2, since the recent versions of 2.x have >> the functionality working correctly for inports & exports according to the >> requirements of OASIS SCA - that is why I raised the JIRA you reference - >> and there are a set of advanced Contribution resolution tests in the OASIS >> SCA test suite which ensure that 2.x stays correct. >> >> I don't know if anyone has backported the 2.x code to 1.6 - unfortunately, >> I am too preoccupied with the 2.x codebase and OASIS conformance to help >> much with the 1.6 codebase, which I have not looked at in a long time. >> >> The 2.x code to resolve this issue has not been backported to 1.6.2. > > It is possible to make this scenario work on 1.6.2 by careful ordering > of the loading/resolution of the contributions, as long as there are > no circular dependencies. If there are circular dependencies, 1.6.2 > can't handle this situation. > > Simon > > > Can you move up to 2.x? >> >> >> Yours, Mike. >> >> >> >
