Moreover, Cave can act as OBR frontend on top of any existing Maven repo.
As a reminder, the simplest Maven remote repo is just a HTTP server
exposing a directory following the Maven directories structure
(groupId/artifactId/version/artifactId-version[-classifier].type).
For instance, I have
For a couple reasons:
1/ Nexus Pro is not able to run directly inside Karaf
2/ Nexus Pro is not an Apache project
3/ Cave is largely lightweight and integrated in Karaf
And there are much more ;)
Regards
JB
On 04/20/2015 09:08 AM, Morgan Hautman wrote:
I'm a little confused now, since Cave is
Cave is more like a OBR only,
while Archiva is more like plain nexus
regards, Achim
2015-04-20 9:08 GMT+02:00 Morgan Hautman :
> I'm a little confused now, since Cave is the same as Nexus "pro", why
> adding OBR support to Archiva when you got Cave already?
>
> Regards,
> Morgan
>
>
> 20/04/201
Hi Frank,
Yes you're right ->
https://books.sonatype.com/nexus-book/reference/osgi-sect-intro.html
Regards
Morgan
On 20/04/2015 9:20, Frank Lyaruu wrote:
I think Nexus community edition also supports OBR now, they have a
plugin for that.
regards, Frank
On Mon, Apr 20, 2015 at 9:08 AM, Mor
I think Nexus community edition also supports OBR now, they have a plugin
for that.
regards, Frank
On Mon, Apr 20, 2015 at 9:08 AM, Morgan Hautman
wrote:
> I'm a little confused now, since Cave is the same as Nexus "pro", why
> adding OBR support to Archiva when you got Cave already?
>
> Regard
I'm a little confused now, since Cave is the same as Nexus "pro", why
adding OBR support to Archiva when you got Cave already?
Regards,
Morgan
20/04/2015 9:05, Jean-Baptiste Onofré wrote:
Correct, Nexus Pro has OBR support.
By the way, I'm working on Archiva to add OBR support too.
Regards
J
Correct, Nexus Pro has OBR support.
By the way, I'm working on Archiva to add OBR support too.
Regards
JB
On 04/20/2015 08:06 AM, Morgan Hautman wrote:
To me it sounds like a nexus "pro" repo since they only have OBR in
their "pro" version.
Is this correct?
Regards
Morgan
On 19/04/2015 20:0
To me it sounds like a nexus "pro" repo since they only have OBR in
their "pro" version.
Is this correct?
Regards
Morgan
On 19/04/2015 20:04, Jean-Baptiste Onofré wrote:
No, Cave is on top of the local dev server. Or the CI can deploy on
the Cave server.
The Karaf instance bootstrapped by t
No, Cave is on top of the local dev server. Or the CI can deploy on the
Cave server.
The Karaf instance bootstrapped by the itests can use the OBR server.
Regards
JB
On 04/19/2015 07:57 PM, Ryan Moquin wrote:
Yes, sorry, I meant as an OBR server. I wasn't meaning use cases for
Cave, I was ju
Yes, sorry, I meant as an OBR server. I wasn't meaning use cases for Cave,
I was just trying to understand how CI servers and Cave are handled as part
of the build and deploy process. It seems that a rescan would have to be
invoked quite frequently to detect new artifacts deployed to a Maven repo
I guess that you mean when Cave is used as an OBR server. In that case,
you have to update the OBR repository metadata by performing a new scan.
There are different use cases to Cave:
1/ you need an OBR server and you only have a Maven repo (in production)
2/ you don't have any existing Maven re
Hi, I've been looking at Apache Cave and how to best leverage it. I had a
few questions as a result. My first one was about how to keep Cave up to
date with changes to a proxied company maven repository, such as
artifactory. For example, if your continuous integration server is pushing
new build
12 matches
Mail list logo
