You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Toni Menzel (JIRA)" <ji...@apache.org> on 2009/10/06 15:37:31 UTC
[jira] Created: (ACE-46) Support Nexus OBR repositories direcly
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 could 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.
[jira] Commented: (ACE-46) Support Nexus OBR repositories direcly
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (ACE-46) Support Nexus OBR repositories direcly
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762712#action_12762712 ]
Marcel Offermans commented on ACE-46:
-------------------------------------
There are three directions we could go in here:
1) Adding a feature to the "choose your bundle" dialog to import artifacts from Nexus. Each imported bundle is then copied to the "internal" OBR of ACE.
2) Adding a feature to the "choose your bundle" dialog to import artifacts from Nexus without copying them to the "internal" OBR of ACE.
3) Using Nexus as the "internal" OBR of ACE.
I would prefer going with option 1, or maybe 2. 3 is more work since we would then have to support "uploading" bundles to Nexus too (and the "internal" OBR also supports adding different types of artifacts).
A more advanced version of 1) would be a version where, if you select a bundle in Nexus, it:
a) wraps it into a bundle if it is not already one (probably by using Pax URL), or
b) analyze dependencies and present you with options to import those too, maybe even automatically create a group for all those dependencies.
WDYT?
> 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 could 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.
[jira] Updated: (ACE-46) Support Nexus OBR repositories direcly
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel updated ACE-46:
---------------------------
Description:
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).
was:
At http://osgi.sonatype.org are many (virtual) obr repositories.
Would be could 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).
> 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.
[jira] Commented: (ACE-46) Support Nexus OBR repositories direcly
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762928#action_12762928 ]
Toni Menzel commented on ACE-46:
--------------------------------
Mmhh.. about 1 and 2.
I talked to Angelo about this shortly.
We basically need just a way to pass in OBR Urls instead of relying on obr.xml.
This must be then a composite to allow
1. more obrs
2. local obrs we can use to write to.
This way its pretty transpartent and one could easily extend the remote obr to nexus in a way that it can also upload things (which is not hard, too btw.)
However, this should be totally transparent, i was just currious if there is already a way to just submit a obr url. Because Felix's OBR Shell has that has well (for example).
about a:
Sure, this refers to normal repositories (M2) that a supplying not bundled jars.
osgi.sonatype.org is all bundles.
Good thing about nexus is that it already abstracts different repositories (M1,M2,OBR,P2 (!)) and you can query and retrieve things why a REST API.
About b:
I initially thought this was part of OBR or at least some side note.
A resolver based on OBR is pretty important if it is not there already (?) --> Doesn't Sigil have that ?
> 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.