support forum...
-Original Message-
From: Lakshman Srilakshmanan
[mailto:[EMAIL PROTECTED]
Sent: Sunday, August 27, 2006 10:34 PM
To: [EMAIL PROTECTED]
Cc: Maven Users List
Subject: RE: [m2] copy of Central Repository
Hi Jeff,
I am sorry I did not understand your original mail
Hi,
correct me if I misunderstand somthing, but you cannot use remote repository
(even inhouse/central housed by your company, but it IS remote repository
from Maven's aspect) as local repositry and vice versa -- they are not
interchangeable, see
there
Thanks again guys.
Thanks
Lakshman
-Original Message-
From: Jeff Jensen [mailto:[EMAIL PROTECTED]
Sent: Monday, 28 August 2006 11:49 PM
To: Lakshman Srilakshmanan
Cc: 'Maven Users List'
Subject: RE: [m2] copy of Central Repository
Proximity allows configuring which
Lakshman
-Original Message-
From: Jeff Jensen [mailto:[EMAIL PROTECTED]
Sent: Friday, 25 August 2006 10:24 PM
To: 'Maven Users List'
Subject: RE: [m2] copy of Central Repository
That's fine, these products allow manual installation as well (in
fact, they
expect you
repository.
I hope I have clarified my problem to make it more clear.
Thanks
Lakshman
-Original Message-
From: Marc L. Veary [mailto:[EMAIL PROTECTED]
Sent: Friday, 25 August 2006 7:23 PM
To: 'Maven Users List'
Subject: RE: [m2] copy of Central Repository
Hi Lakshman,
We have a number
Hi.
We started using mvn deploy:deploy-file, but then realised that if we did a
full build on the box that hosts our internal repo - this would do the job -
and it does.
However, I would like to know if there is a better or 'proper' solution to
this.
Kind regards,
--
Marc
-Original
Putting up a maven proxy might solve your problem:
the first time a jar is needed it downloads it from the central repo and
caches it.
There are 3 free implementations I know of:
maven-proxy (from the maven guys): beta?, abandoned in favor of Archiva
Archiva (from the maven guys): beta, needs
*.xml.sha1
Is it possible you are still looking at the central server at
http://repo1.maven.org/maven2 ??
Thanks
Lakshman
-Original Message-
From: Marc L. Veary [mailto:[EMAIL PROTECTED]
Sent: Friday, 25 August 2006 5:40 PM
To: 'Maven Users List'
Subject: RE: [m2] copy of Central
: [m2] copy of Central Repository
Putting up a maven proxy might solve your problem:
the first time a jar is needed it downloads it from the central repo
and
caches it.
There are 3 free implementations I know of:
maven-proxy (from the maven guys): beta?, abandoned in favor of
Archiva
Archiva
Hi All,
I think the answer lies in Maven Repository Manager. Pg 200 in the book
Better Builds with Maven.
Could someone please verify my understanding and whether a download is
available ?
Thanks
Lakshman
-Original Message-
From: Lakshman Srilakshmanan
Sent: Friday, 25 August 2006
-Original Message-
From: Lakshman Srilakshmanan
[mailto:[EMAIL PROTECTED]
Sent: 25 August 2006 09:18
To: Maven Users List
Subject: RE: [m2] copy of Central Repository
Hi Marc,
I did a full build on the box that hosts our internal repo, but as
explained, it did not work for me. I have also explained
@maven.apache.org
Subject: Re: [m2] copy of Central Repository
Putting up a maven proxy might solve your problem:
the first time a jar is needed it downloads it from the central repo
and
caches it.
There are 3 free implementations I know of:
maven-proxy (from the maven guys): beta?, abandoned
12 matches
Mail list logo