You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2010/02/19 16:08:28 UTC

[jira] Assigned: (ARIES-191) Improvements to VersionRange and ManifestHeaderProcessor

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

Valentin Mahrwald reassigned ARIES-191:
---------------------------------------

    Assignee: Valentin Mahrwald

> Improvements to VersionRange and ManifestHeaderProcessor
> --------------------------------------------------------
>
>                 Key: ARIES-191
>                 URL: https://issues.apache.org/jira/browse/ARIES-191
>             Project: Aries
>          Issue Type: Improvement
>          Components: Application
>            Reporter: Holly Cummins
>            Assignee: Valentin Mahrwald
>         Attachments: versionrangepatch.txt
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> It would be useful to have a method on VersionRange which produces the intersection between itself and another VersionRange. The patch includes this method, updates to how equals() and hashCode() work to support this function, and new unit tests for the intersect() method.
> The ManifestHeaderProcessor should handle the objectClass attribute as a special case when generating filters. It should produce a filter element for each interface in the comma-separated list of interfaces. 
> It would also be convenient to be able to pass through nested verbatim filter text to the filter generation code. This is done in the attached patch using a org.apache.aries.application.filter.attribute attribute. The ManifestHeaderProcessor checks for this attribute and inserts the value into the generated filter string verbatim.

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