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.
How about with local development? If artifacts are installed using
OBR,
do you have to run a local Cave server in order to install
artifacts in
you local dev server? Or what about in integration tests?
Sorry if these are stupid questions, want to make sure I understand
the
best way to integrate it. :)
On Sun, Apr 19, 2015, 1:47 PM Jean-Baptiste Onofré <[email protected]
<mailto:[email protected]>> wrote:
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 repo and you are looking
for a
Maven repo to share between multiple Karaf instances (with Cellar
for
instance)
3/ you want to proxy a external repo (OBR or Maven) internally
Regards
JB
On 04/19/2015 07:40 PM, Ryan Moquin wrote:
> 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 builds to you maven repo, do you then also have it
remotely
> invoke a rescan of the proxied repository in the Cave server?
>
> What is the typical way that Cave is used in the development
and
> deployment process?
>
> Thanks!
> Ryan
>
--
Jean-Baptiste Onofré
[email protected] <mailto:[email protected]>
http://blog.nanthrax.net
Talend - http://www.talend.com
