Niclas Hedhman wrote:
You said; libraries that are currently hosted on cvs.a.o, meaning they
exist
on cvs.a.o, and can't you just tell Maven in your pom to use that repository
as well??
I meant :
libraries that are currently hosted on cvs.a.o AND that are not hosted
on ibiblio AND that
Niclas Hedhman wrote:
What is being suggested is not that we mirror the whole of ibiblio, we
would only mirror the libraries that are currently hosted on cvs.a.o.
... You can point your pom to use the cvs.a.o directly.
What do you mean here?
- the dependency is not available on the
Pier Fumagalli wrote:
On 20 Mar 2006, at 09:19, Andrew Savory wrote:
Hi,
Jorg Heymans wrote:
If someone can offer the bandwidth and server, i'm willing to
migrate us
away from cvs.a.o. and setup a decent m2 repo where only *we* control
the poms.
Any offers? I've got some time to kill
Niclas Hedhman wrote:
If SNAPSHOTs are totally unavoidable, consider putting these in the Svn
alongside the source code. Inability to build from today's source in the
future is a serious flaw in chosen strategy.
This is exactly what we do internally. ;-)
Best Regards,
Antonio Gallardo.
On Wednesday 22 March 2006 01:00, Jorg Heymans wrote:
Niclas Hedhman wrote:
What is being suggested is not that we mirror the whole of ibiblio, we
would only mirror the libraries that are currently hosted on cvs.a.o.
... You can point your pom to use the cvs.a.o directly.
What do you
Niclas Hedhman wrote:
You said; libraries that are currently hosted on cvs.a.o, meaning
they exist
on cvs.a.o, and can't you just tell Maven in your pom to use that repository
as well??
From what I can see the build is set up to do that. The builds fail
because apparently that repository
Hi,
Jorg Heymans wrote:
If someone can offer the bandwidth and server, i'm willing to migrate us
away from cvs.a.o. and setup a decent m2 repo where only *we* control
the poms.
Any offers? I've got some time to kill this weekend ;)
We (Luminas/SourceSense) are offering. Do you know what
On 20 Mar 2006, at 09:19, Andrew Savory wrote:
Hi,
Jorg Heymans wrote:
If someone can offer the bandwidth and server, i'm willing to
migrate us
away from cvs.a.o. and setup a decent m2 repo where only *we* control
the poms.
Any offers? I've got some time to kill this weekend ;)
We
Hi,
Pier Fumagalli wrote:
Excuse me, but can someone refresh my memory on why we went down the
Maven way? I thought it was to get rid of maintaining all those lib in
our SVN, and now someone is telling me that we actually should maintain
a full maven mirror, but tweaked because we don't like
Andrew Savory wrote:
We (Luminas/SourceSense) are offering. Do you know what sort of
requirements in terms of bandwidth and server space? We have capacity
to spare, and are happy to donate it.
Thanks, see below.
Pier Fumagalli wrote:
Excuse me, but can someone refresh my memory on why we
Andrew Savory wrote:
infrastructure problems are resolved. Actually, in hindsight, it makes
more sense to see what can be done to fix maven's repo infrastructure -
but I know nothing about ibiblio etc. and don't have time to investigate
This is being worked on by maven and infra, but it's a
On Tuesday 21 March 2006 02:32, Jorg Heymans wrote:
What is being suggested is not that we mirror the whole of ibiblio, we
would only mirror the libraries that are currently hosted on cvs.a.o.
This sounds like a really odd idea. You can point your pom to use the cvs.a.o
directly.
- the
Andrew Savory wrote:
Is there any way we can set up a Cocoon mirror for the time being, until
the repository problems are resolved? I'm sure several of us here can
set up a repo, and it could be the default used by Cocoon.
If someone can offer the bandwidth and server, i'm willing to migrate
13 matches
Mail list logo
