Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <12669692.136931271325408476.JavaMail.jira@thor>
Date: Thu, 15 Apr 2010 05:56:48 -0400 (EDT)
From: "Guillaume Nodet (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Commented: (ARIES-283) Provide an implementation of
 ResourceResolver that can find/resolve resources in local .m2 repo or any
 other specified repo
In-Reply-To: <13397730.118701271264812316.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ARIES-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857251#action_12857251 ] 

Guillaume Nodet commented on ARIES-283:
---------------------------------------

I've had fixed those last week IIRC but forgot to deploy a new snapshots.  I've deployed one now, so it should work better.
If you have still issues, please raise a JIRA on felix for the maven bundle plugin so that we can discuss it there.

Imho, the subsystem should not try to mess with the RepositoryAdmin job.   We should only use it, that's all.   The relevant code in the application-obr-resolver was fine I think, i.e. it simply uses any configured repository with the only exception that we may want an additional repository generated from the content of the subsystem archive.   I don't think we should try to automatically add an obr repository based on ~/.m2/repository.   This would be the responsability of the user to add it if needed.

Wrt to the Manve2Repository, i'm not really sure how it works, but as I said, I don't think we need it at all.

Two more things:  I think it would make sense to extract the obr related code into a separate maven module.   And last, I think it would be easier to use the new api which will provide a better support for the use case.  This is some work I've done in the last couple of weeks derived from the need in applications, so it should be a good fit.   I think we should use bundlerepository 1.6.1-SNAPSHOT and the org.apache.felix.bundlerepository package instead which allows the additional or repositories onto a given resolved and not resolving optional resources (which I don't think we want, as the number of dependencies could grow very fast).

> Provide an implementation of ResourceResolver that can find/resolve resources in local .m2 repo or any other specified repo
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-283
>                 URL: https://issues.apache.org/jira/browse/ARIES-283
>             Project: Aries
>          Issue Type: Improvement
>          Components: Subsystem
>    Affects Versions: Incubation
>            Reporter: Lin Sun
>            Assignee: Lin Sun
>             Fix For: Incubation
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira