You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Alasdair Nottingham (JIRA)" <ji...@apache.org> on 2010/02/18 17:44:27 UTC

[jira] Work started: (ARIES-188) Separate out the Isolated and Shared bundle content in DeploymentMetadata.java

     [ https://issues.apache.org/jira/browse/ARIES-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ARIES-188 started by Alasdair Nottingham.

> Separate out the Isolated and Shared bundle content in DeploymentMetadata.java
> ------------------------------------------------------------------------------
>
>                 Key: ARIES-188
>                 URL: https://issues.apache.org/jira/browse/ARIES-188
>             Project: Aries
>          Issue Type: Improvement
>          Components: Application
>            Reporter: Alasdair Nottingham
>            Assignee: Alasdair Nottingham
>
> An Application defines some content and a resolver finds dependencies. The dependencies should be sharable with other applications, but there is no way in the DeploymentMetadata to differentiate shared and non-shared content. This enhancement will separate the two out.
> I also found a bug which I'll fix here. If the Application-Content mentions bundle org.apache.aries.example;version="[1.0.0,2.0.0)" and the resolver may choose version 1.5. The problem is the DeploymentMetadata will set the Deployed-Content to be the minimum version irrespective.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.