felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-2144) Add global requirements and capabilities
Date Tue, 02 Mar 2010 22:50:27 GMT

    [ https://issues.apache.org/jira/browse/FELIX-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840370#action_12840370

Richard S. Hall commented on FELIX-2144:

Technically, the timestamp can still be calculated by looping through all resources doing
Resource.getRepository().getLastModified()...it is more redundant, but largely equivalent
to looping through all repositories. Of course, if we keep the double linking removed, then
this won't work.

I don't have an issue with separating the deployer from the resolver, but can we do this in
a way that can still be easily wrapped into the original OSGi API? But if we want to avoid
majorly changing the original API, then keeping the double linking between Resource and Repository
seems easier.

> Add global requirements and capabilities
> ----------------------------------------
>                 Key: FELIX-2144
>                 URL: https://issues.apache.org/jira/browse/FELIX-2144
>             Project: Felix
>          Issue Type: New Feature
>          Components: Bundle Repository (OBR)
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: bundlerepository-1.6.0
> Global constraints on resources would be useful to be able to add constraints to the
resolution like:
>   * do not use a resource
>   * add version range to used resources ...

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

View raw message