[
https://issues.apache.org/jira/browse/ACE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762962#action_12762962
]
Marcel Offermans commented on ACE-46:
-------------------------------------
About 1,2,3:
What we currently need is basically just a thin API on top of some repository
like OBR, so I agree it probably would not be too hard to make Nexus support
that, especially if Nexus can support non-jar artifacts and can upload them.
I agree with Angelo that we need a way to use or import from multiple sources.
So in the end, supporting options 1, 2 and 3 would be nice.
About a,b:
Referencing the mail on Installable Units in Ace on the mailing list, having a
resolver to help you would be nice, but I don't think it's smart to *rely* on
it to only produce valid sets of bundles. If you need that, a bit more thought
and design needs to go into it, and I have not seen systems that can reliably
do that based on meta-data only.
We don't currently use and information related to requirements and capabilities
to do resolving, but we could definitely look into using existing resolvers. I
have not looked at Sigil extensively enough, but if it has an external resolver
then we could investigate if we can use it in our import/add component dialog.
> Support Nexus OBR repositories direcly
> --------------------------------------
>
> Key: ACE-46
> URL: https://issues.apache.org/jira/browse/ACE-46
> Project: Ace
> Issue Type: New Feature
> Reporter: Toni Menzel
>
> At http://osgi.sonatype.org are many (virtual) obr repositories.
> Would be good to support them directly in the server-obr setups and makes
> this whole story much more appealing (thousands, millions of bundles) when
> opening the "choose your bundle" dialog in webui (for example).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
