On 16 Jun 06, at 9:00 AM 16 Jun 06, Brett Porter wrote:
Are all these required?
It's the start of a larger IT but I started it here.
I think the converter covers all the alternatives, all we want to
test here is that the discoverer and converter are tied together
correctly?
Sure, I co
Are all these required?
I think the converter covers all the alternatives, all we want to test
here is that the discoverer and converter are tied together correctly?
- Brett
[EMAIL PROTECTED] wrote:
Author: jvanzyl
Date: Fri Jun 16 05:02:05 2006
New Revision: 414809
URL: http://svn.apache.o
Brett Porter wrote:
Would you mind sending some details out to that list? I am not
subscribed so I can't get to the archives.
Neither am I, actually :-(
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
The admins were (I had to enable .htaccess via the helpdesk).
Would you mind sending some details out to that list? I am not
subscribed so I can't get to the archives.
- Brett
Felipe Leme wrote:
> BTW, when these rewrite rules were created, were the ibiblio admins been
> notified on the changes?
BTW, when these rewrite rules were created, were the ibiblio admins been
notified on the changes?
I'm asking because we mirrors ibiblio at work and the guy responsible
for the job wasn't aware of the change, even though he is subscribed to
the ibiblio-mirrors list
(http://lists.ibiblio.org/ma
I couldn't sort out the /maven thing. /maven/ works. Anyone else have
sufficient mod_rewrite skills?
As for the sync - it doesn't appear to be necessary since the m1 repo
was cleaned anyway. I will need to do the following:
* sync maven 1 plugins. Currently they are not converted to the new
repo,
get the
> >>> snapshot and a warning if somebody tries to use it.
> >> I don't think so. The Maven 1.x repository basically doesn't exist (its
> >> not web accessible). They are identical.
> >>
> >
> >
> > yep, but m1 won't follo
ings like log4j 1.1-dev,
>>> probably we should relocate this to log4j-1.1-2005 to keep it
>>> consistent. m1 would still get the 1.1-dev but m2 will get the
>>> snapshot and a warning if somebody tries to use it.
>> I don't think so. The Maven 1.x repository
On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Heh, that's interesting. I'll put a rule in for that one specifically.
That would be great.
Anyways, I''ve also found another glitch:
http://ibiblio.org/maven/jaxen/jars/jaxen-1.0-FCS-full.jar
points to:
http://ibiblio.org/maven2/jaxen/
On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Heh, that's interesting. I'll put a rule in for that one specifically.
That would be great.
Anyways, I''ve also found another glitch:
http://ibiblio.org/maven/jaxen/jars/jaxen-1.0-FCS-full.jar
points to:
http://ibiblio.org/maven2/jaxen/
Brett Porter wrote:
Heh, that's interesting. I'll put a rule in for that one specifically.
Another issue just discovered: we let all kinds of crap to sync into the
m1 repo, including development builds. We don't convert them to the
maven 2.x repo. That now breaks builds that depended on the snap
snapshot and a warning if somebody tries to use it.
>
> I don't think so. The Maven 1.x repository basically doesn't exist (its
> not web accessible). They are identical.
>
yep, but m1 won't follow pom relocations
-
y we should relocate this to log4j-1.1-2005 to keep it
> consistent. m1 would still get the 1.1-dev but m2 will get the
> snapshot and a warning if somebody tries to use it.
I don't think so. The Maven 1.x repository basically doesn't exist (its
not web
a) should be fine as in the m1 repo there are no snapshots now, they
were deleted before and copied on demand.
A problem is that we'll be publishing things like log4j 1.1-dev,
probably we should relocate this to log4j-1.1-2005 to keep it
consistent. m1 would still get the 1.1-dev but m2 will g
+1 for a
Arnaud
On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Heh, that's interesting. I'll put a rule in for that one specifically.
>
> Another issue just discovered: we let all kinds of crap to sync into the
> m1 repo, including development builds. We don't convert them to the
> maven
Heh, that's interesting. I'll put a rule in for that one specifically.
Another issue just discovered: we let all kinds of crap to sync into the
m1 repo, including development builds. We don't convert them to the
maven 2.x repo. That now breaks builds that depended on the snapshots.
Do we:
a) do a
I believe that's caused by the rewrite rules, they don't work well
with dirs but they do with artifacts
On 1/9/06, Felipe Leme <[EMAIL PROTECTED]> wrote:
> Weird, it was screwed a couple of minutes ago (the
> http://www.ibiblio.org/maven was redirecting to the
> http://www.ibiblio.org/maven/public
Weird, it was screwed a couple of minutes ago (the
http://www.ibiblio.org/maven was redirecting to the
http://www.ibiblio.org/maven/public/html/maven, which in turn didn't have
any groupId dir)...
-- Felipe
On 1/9/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
>
> http://www.ibiblio.org/maven
http://www.ibiblio.org/maven/
Emmanuel
Felipe Leme a écrit :
Hi Brett,
Sorry for the stupid question (I haven't been following the lists for a
while), but where is the old repo right now? My maven1 projects are failing
because the http://www.ibiblio.org/maven/public/html/maven/ only have 2
sub
Hi Brett,
Sorry for the stupid question (I haven't been following the lists for a
while), but where is the old repo right now? My maven1 projects are failing
because the http://www.ibiblio.org/maven/public/html/maven/ only have 2
sub-dires, maven and poms...
-- Felipe
On 1/8/06, Brett Porter <[
The rewrites are back in place, so I've turned off the sync of the m1
repo to ibiblio.
Going forward plan is to get the repo manager up and pulling in content
to only the maven2 repo, then we can toast the m1 repo altogether.
Obviously we need to be confident that the rewrite rules are working
com
ant plugin cannot download uberjar artifacts from a maven 1.x repository
Key: MNG-1820
URL: http://jira.codehaus.org/browse/MNG-1820
Project: Maven 2
Type: Bug
Components: Ant tasks
In the interests of simplifying maintenance of the Maven 1.x and Maven
2.x repositories, I have setup ibiblio to map all requests from
http://www.ibiblio.org/maven to http://www.ibiblio.org/maven2
If you are experiencing any difficulties, please let us know.
- Brett
--
Hi Rafal and others,
Can you please test: http://www.ibiblio.org/maven/test as your remote
repo. I have successfully bootstrapped m1 using this with the rules
turned on.
Thanks,
Brett
Brett Porter wrote:
> Yes, but that's what's intended. You can't navigate it in the old
> layout, but old layout
Yes, but that's what's intended. You can't navigate it in the old
layout, but old layout URLs will translate correctly.
However, I discovered that Maven 1.0 and Maven 1.1 are both choking on
the cross host redirects, so I'll need to look into that. That won't
affect the final solution, but certain
Brett Porter wrote:
We've set up for testing the following repository for Maven 1.x users:
http://repo1.maven.org/maven
This maps directly onto the Maven 2 repository, converting the layout on
the fly. Being able to do this will reduce the amount of maintenance
required and ensure libraries arr
We've set up for testing the following repository for Maven 1.x users:
http://repo1.maven.org/maven
This maps directly onto the Maven 2 repository, converting the layout on
the fly. Being able to do this will reduce the amount of maintenance
required and ensure libraries arrive to all users as so
27 matches
Mail list logo
