Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <596566259.36311267462805718.JavaMail.jira@brutus.apache.org>
Date: Mon, 1 Mar 2010 17:00:05 +0000 (UTC)
From: "Guillaume Nodet (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-2144) Add global requirements and
 capabilities
In-Reply-To: <472900175.29801267436045720.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Guillaume Nodet commented on FELIX-2144:
----------------------------------------

The goal is to be able to direct a bit and constraint the set of available resources.
Another way would be to simply allow the resolver to be given a set of resources to resolve against instead of repositories.
This is actually what is done to support those global constraints (i.e. filter the resources before starting the resolution).

This way, the user could choose to use local resources, remote resources and more importantly, which one.
This could also be used to filter for licensing reasons or such.

> 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.