Thanks for documenting this Jeff. Hopefully this will be a temporary
work-around which can later be removed once things are fixed in the
repository.
Which brings me to the next point - what can be done to really fix this?
I guess Sun owns this repo? We could push to get the redirect
Forwarding to dev list thread, also...
--kevan
On Nov 11, 2009, at 10:33 AM, Kevan Miller wrote:
On Nov 10, 2009, at 11:00 PM, Fei LI wrote:
Hi,
I am exhausted and decide to give up.
If you really want to help me out, please remove your local repo
completely, build from the ground and
I've also verified that this work-around will get Geronimo 2.2 building
again. So I've now built both 2.1.4 and 2.2 from clean repos (using
different jdk's, and maven versions) with the referenced addition to
settings.xml.
To break it down by Geronimo version:
2.2:
I've also been successful building branches/2.1 with Donald's most
recent change to revert back to genesis 1.3.1 and the mirror for
java.net in my settings.xml as mentioned earlier.
here's the details for 2.1:
https://svn.apache.org/repos/asf/geronimo/server/branches/2.1
Maven 2.0.10
jdk
On Nov 11, 2009, at 10:14 AM, Joe Bohn wrote:
Thanks for documenting this Jeff. Hopefully this will be a
temporary work-around which can later be removed once things are
fixed in the repository.
Which brings me to the next point - what can be done to really fix
this? I guess Sun owns
it.
From: Kevan Miller [mailto:kevan.mil...@gmail.com]
Sent: Wed 11/11/2009 7:35 AM
To: Geronimo Dev
Subject: Re: Could not build Geronimo server from SVN branch 2.2
Forwarding to dev list thread, also...
--kevan
On Nov 11, 2009, at 10:33 AM, Kevan Miller wrote
/11/2009 7:35 AM
To: Geronimo Dev
Subject: Re: Could not build Geronimo server from SVN branch 2.2
Forwarding to dev list thread, also...
--kevan
On Nov 11, 2009, at 10:33 AM, Kevan Miller wrote:
On Nov 10, 2009, at 11:00 PM, Fei LI wrote:
Hi,
I
It really concerns me that we can't even build 2.1.4 from the tag. I
went out there and attempted this and received the same bogus pom for
several artifacts including:
org/apache/yoko/yoko-rmi-spec/1.0/yoko-rmi-spec-1.0.pom
and
log4j/log4j/1.2.13/log4j-1.2.13.pom
I was speaking with Kevan
On Nov 9, 2009, at 5:28 PM, Jay D. McHugh wrote:
Here is what they problem is - they moved that artifact.
In its place is the following html file (rather than a pom)
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
htmlhead
title301 Moved Permanently/title
/headbody
h1Moved Permanently/h1
pThe
After looking into this some more and discussing it off-line with Jarek
I've learned the following:
- It isn't really returning a bogus pom or jar ... it is just returning
a redirect. Maven wrongly assumes that this is the actual file that was
requested and persists it as such.
- Using Maven
On Nov 10, 2009, at 3:31 PM, Joe Bohn wrote:
After looking into this some more and discussing it off-line with
Jarek I've learned the following:
- It isn't really returning a bogus pom or jar ... it is just
returning a redirect. Maven wrongly assumes that this is the actual
file that
Kevan Miller wrote:
On Nov 10, 2009, at 3:31 PM, Joe Bohn wrote:
After looking into this some more and discussing it off-line with
Jarek I've learned the following:
- It isn't really returning a bogus pom or jar ... it is just
returning a redirect. Maven wrongly assumes that this is the
I update the page on GMOxDEV based on this discussion, anything incorrect,
please let me know.
http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html
Jeff
On Wed, Nov 11, 2009 at 5:47 AM, Joe Bohn joe.b...@earthlink.net wrote:
Kevan Miller wrote:
On Nov 10, 2009, at 3:31 PM, Joe
://old.nabble.com/Could-not-build-Geronimo-server-from-SVN-branch-2.2-tp26273831s134p26283602.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
Hi,
Another failed day to build Geronimo server from SVN branch 2.2.
My OS is Windows XP.
Today I tried:
Jsdk 1.6.0_16
Jsdk 1.5.0_22
Maven 2.2.1
Maven 2.0.10
Donald woods helped me to try shorter folder like c:\g22; c:\m2repo, did
not work.
He also asked me to delete some troubled files and
Hello,
It looks like the automated build has been failing since 11/7 on that
artifact (com.envoisolutions.sxc).
So - I think that it has somehow become corrupted in the maven
repositories. If anyone had a local version that was 'good', then they
would be able to build 2.2.
If they were
Here is what they problem is - they moved that artifact.
In its place is the following html file (rather than a pom)
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
htmlhead
title301 Moved Permanently/title
/headbody
h1Moved Permanently/h1
pThe document has moved a
17 matches
Mail list logo
