[
https://issues.apache.org/jira/browse/ARIES-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857368#action_12857368
]
Guillaume Nodet commented on ARIES-283:
---------------------------------------
Did you try the index command with an updated snapshot of the maven bundle
repository, i've uploaded a new one this morning.
As for the local m2 repo, I disagree. I think the obr repository should not be
tied to the subsystem definition in any way. The reason is that if you put
the repository url in the subsystem metadata somehow, the deployer can't
control where the artifacts will be pulled from anymore. In a tightly
controlled environment, I think the deployer would not allow the use of non
trusted repositories such as maven central or anything (and that includes any
local repository on the user's disk). The administrator would point to a know
obr repository which contains trusted resources.
Hence the need to clearly separate the subsystem from the repository resolver
and let the resolver do it's job: i.e. finding resources from the places it has
been configured.
As for testing, let me try to update the test case to add a repository ...
> 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
