commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: [GUMP@vmgump]: Project commons-configuration (in module apache-commons) failed
Date Tue, 31 Mar 2009 08:59:07 GMT
On 2009-03-31, Jörg Schaible <> wrote:

> Stefan Bodewig wrote at Montag, 30. März 2009 12:27:

>> I think I see why Gump's mvn repository proxy doesn't work here - it
>> currently doesn't work for group-ids that contain dots.

>> Do you want me to turn off nags until this gets fixed (shouldn't take
>> longer than a few days, I hope)?

> I don't know Gump well enough, but what you did for vfs seems to be a
> solution that has been taken nowhere else.

Sure, no other solution has been proposed or what has been proposed
didn't work, though.

> I don't know wether you're familiar with the M2 relocation
> mechanism,

Not at all.

> but that might be useful here.  All that is needed is a POM for
> commons-vfs:commons-vfs:2.0-SNAPSHOT that relocates this artifact to
> org.apache.commons:commons-vfs:2.0-SNAPSHOT.

Where would that POM live?  Who would have tp provide it?

The configuration to vfs case is more comlpex than I thought.  First
of all Gump's proxy is never asked for VFS by configuration since it
is only a proxy for the central repo (as of now) and mvn seems to know
that it doesn't need to look there.

The second part - and that's what I don't understand - is that there
is no vfs snapshot in the Apache snapshot repository either, so where
do you get your snapshot from when you build configuration (with or
without Gump)?

I'm working on extending the Gump proxy to proxy multiple repositories
at the same time (need that for castor anyway) and hope this will make
Gump provide the correct jar.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message