[
https://issues.apache.org/jira/browse/TUSCANY-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125910#comment-13125910
]
Eric Larsen commented on TUSCANY-3880:
--------------------------------------
When implementing this, I discovered that it causes a compliance test (10004)
relating to the uses clause in exports. I looked into this and discovered the
only reason we are passing this test is due to the current practice of using
String compare on import and export package strings. Additionally, this test
case is invalid if uses is implemented to the spec the test case will fail as
it is written.
Implementation of the logic for uses clauses at first glance seems like it is
rather complex. The problem is the way uses clauses work is that they can
conflict with a prior package resolution, so some sort of backtracking and
master list of packages is needed. If I remember correctly the approach used
when resolving packages is one at a time with little to no knowledge of future
and prior resolutions.
> Contribution java import/export versioning is not fully supported
> -----------------------------------------------------------------
>
> Key: TUSCANY-3880
> URL: https://issues.apache.org/jira/browse/TUSCANY-3880
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0-M5
> Reporter: Simon Laws
> Fix For: Java-SCA-2.0
>
> Attachments: JIRA-3880-contribution.patch
>
>
> The OASIS Java CAA spec (section 10) defines how Java contribution
> import/exports are versioned. It doesn't look like we support this fully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
