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:42:28 UTC
[jira] Created: (ARIES-188) Separate out the Isolated and Shared
bundle content in DeploymentMetadata.java
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.
[jira] Resolved: (ARIES-188) Separate out the Isolated and Shared
bundle content in DeploymentMetadata.java
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alasdair Nottingham resolved ARIES-188.
---------------------------------------
Resolution: Fixed
Fix Version/s: 0.1
> 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
> Fix For: 0.1
>
>
> 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.
[jira] Commented: (ARIES-188) Separate out the Isolated and Shared
bundle content in DeploymentMetadata.java
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835748#action_12835748 ]
Alasdair Nottingham commented on ARIES-188:
-------------------------------------------
The intent is that the Application-Content is a set of content that is core to the application and as noted in the discussion thread is "isolated". This content can be expressed as a range of versions and in the resolve process the content is locked down to a specific version within that range.
The resolve process also identifies a set of bundles that are needed to support the application, but are not part of the core content. Currently both core, and supporting bundles are in the same part of the DeploymentMetadata. I am separating them out into two parts. As an example:
Application-Content: a,b
a depends on b, c
b depends on d, q
q depends on z
This currently results in:
Deployed-Content: a, b, c, d, q, z
This item will change it so we have:
Deployed-Content: a, b
Provision-Content: c, d, q, z
You can thus tell why a bundle is in the deployment metadata quickly and easily and this can be used by the ApplicationContextManager when installing the application to determine how and where to install the bundles.
In my mental model this separates into Deployed-Content = isolated, Provision-Content = shared, but it is down to the ApplicationContextManager to put this into practise.
Alasdair
> 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.
[jira] Work started: (ARIES-188) Separate out the Isolated and
Shared bundle content in DeploymentMetadata.java
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (ARIES-188) Separate out the Isolated and Shared
bundle content in DeploymentMetadata.java
Posted by "Mark Nuttall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835747#action_12835747 ]
Mark Nuttall commented on ARIES-188:
------------------------------------
Please also update http://incubator.apache.org/aries/applications.html to reflect any new headers.
> 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.
[jira] Commented: (ARIES-188) Separate out the Isolated and Shared
bundle content in DeploymentMetadata.java
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835401#action_12835401 ]
Guillaume Nodet commented on ARIES-188:
---------------------------------------
Could you expose what you have in mind ? See discussion on the dev list. Thx
> 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.