[
https://issues.apache.org/jira/browse/ARIES-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alasdair Nottingham resolved ARIES-661.
---------------------------------------
Resolution: Fixed
> Deployment manifest Import-Packges ends up in strange format
> ------------------------------------------------------------
>
> Key: ARIES-661
> URL: https://issues.apache.org/jira/browse/ARIES-661
> Project: Aries
> Issue Type: Bug
> Components: Application
> Affects Versions: 0.3
> Reporter: David Jencks
> Assignee: Alasdair Nottingham
>
> The initial internal generation of the deployment manifest seems reasonable
> but then it is read in to DeploymentManifestImpl where the Import-Package
> attribute is converted to ContentImpl. When writing back to a file or entry
> in the eba this DeploymentManifestImpl code is used to generate the
> Import-Package header:
> {code}
> private String getContentsAsString (Collection<Content> contents) {
> StringBuilder builder = new StringBuilder();
> boolean beginning = true;
> for (Content c : contents) {
> if (!!!beginning) {
> builder.append(",");
> }
> builder.append(c);
> beginning = false;
> }
> return builder.toString();
> }
> {code}
> However ContentImpl.toString() writes out the map attached to the package
> name as a map so the result is like this:
> javax.servlet;{version->2.6.0}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
