Apache Geronimo › Development

Could not build Geronimo server from SVN branch 2.2

Classic

List

Threaded

17 messages Options

Fei LI-2

Could not build Geronimo server from SVN branch 2.2

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 did not work too.

So far, I tried 2.1.4, 2.2 and trunk and no one works.

Anybody ever clean your repo and build from nothing just kie me? Try! Please!!! Tell me how to build then.

Thanks

Fei Li

See my error:

[INFO] [enforcer:enforce {execution: default}]
[WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for p

roject com.envoisolutions.sxc:sxc-runtime at C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
[WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for p

roject com.envoisolutions.sxc:sxc-runtime at C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
[INFO] [plugin:descriptor]
[INFO] Using 'UTF-8' encoding to read mojo metadata.
[INFO] Applying mojo extractor for language: java
[WARNING] org.apache.geronimo.mavenplugins.car.ArchiveCarMojo#jarArchiver:
[WARNING]   The syntax
[WARNING]     @parameter expression="${component.<role>#<roleHint>}"
[WARNING]   is deprecated, please use
[WARNING]     @component role="<role>" roleHint="<roleHint>"
[WARNING]   instead.
[INFO] Mojo extractor for language: java found 10 mojo descriptors.
[INFO] Applying mojo extractor for language: bsh
[INFO] Mojo extractor for language: bsh found 0 mojo descriptors.
[WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for p

roject com.envoisolutions.sxc:sxc-runtime at C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
[INFO] [remote-resources:process {execution: default}]
[WARNING] Attempting to build MavenProject instance for Artifact (com.envoisolutions.sxc:sxc-runtime:0.7.2) of type: jar; constructing POM artifact instead.

[WARNING] Invalid project model for artifact [sxc-runtime:com.envoisolutions.sxc:0.7.2]. It will be ignored by the remote resources Mojo.

[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory C:\g22\framework\buildsupport\car-maven-plugin\src\main\filtered-resources
[INFO] Copying 3 resources
[WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for p

roject com.envoisolutions.sxc:sxc-runtime at C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
[INFO] [compiler:compile]
[INFO] Compiling 20 source files to C:\g22\framework\buildsupport\car-maven-plugin\target\classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
error: error reading C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar; error in opening zip file

error: error reading C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar; error in opening zip file

Jay D. McHugh-2-3

Re: Could not build Geronimo server from SVN branch 2.2

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 starting from scratch (like yourself) or cleared their
local repo - then they would start getting errors.

We will try to see if we can find a good copy of the artifacts (or to
have a good copy reloaded into the repos).

Sorry for the trouble. Hopefully, we will be able to get things
straightened out soon (for you and us as well).

Jay

Fei LI wrote:

>
> 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 did not work too.
>
> So far, I tried 2.1.4, 2.2 and trunk and no one works.
>
>
> Anybody ever clean your repo and build from nothing just kie me? Try!
> Please!!! Tell me how to build then.
>
>
> Thanks
>
> Fei Li
>
> See my error:
>
> [INFO] [enforcer:enforce {execution: default}]
> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
> is invalid. It will be ignored for artifact resolution. Reason: Not a
> v4.0.0 POM. for p
>
> roject com.envoisolutions.sxc:sxc-runtime at
> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
> is invalid. It will be ignored for artifact resolution. Reason: Not a
> v4.0.0 POM. for p
>
> roject com.envoisolutions.sxc:sxc-runtime at
> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
> [INFO] [plugin:descriptor]
> [INFO] Using 'UTF-8' encoding to read mojo metadata.
> [INFO] Applying mojo extractor for language: java
> [WARNING] org.apache.geronimo.mavenplugins.car.ArchiveCarMojo#jarArchiver:
> [WARNING] The syntax
> [WARNING] @parameter expression="${component.<role>#<roleHint>}"
> [WARNING] is deprecated, please use
> [WARNING] @component role="<role>" roleHint="<roleHint>"
> [WARNING] instead.
> [INFO] Mojo extractor for language: java found 10 mojo descriptors.
> [INFO] Applying mojo extractor for language: bsh
> [INFO] Mojo extractor for language: bsh found 0 mojo descriptors.
> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
> is invalid. It will be ignored for artifact resolution. Reason: Not a
> v4.0.0 POM. for p
>
> roject com.envoisolutions.sxc:sxc-runtime at
> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
> is invalid. It will be ignored for artifact resolution. Reason: Not a
> v4.0.0 POM. for p
>
> roject com.envoisolutions.sxc:sxc-runtime at
> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
> [INFO] [remote-resources:process {execution: default}]
> [WARNING] Attempting to build MavenProject instance for Artifact
> (com.envoisolutions.sxc:sxc-runtime:0.7.2) of type: jar; constructing
> POM artifact instead.
>
> [WARNING] Invalid project model for artifact
> [sxc-runtime:com.envoisolutions.sxc:0.7.2]. It will be ignored by the
> remote resources Mojo.
>
> [INFO] [resources:resources]
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO] skip non existing resourceDirectory
> C:\g22\framework\buildsupport\car-maven-plugin\src\main\filtered-resources
> [INFO] Copying 3 resources
> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
> is invalid. It will be ignored for artifact resolution. Reason: Not a
> v4.0.0 POM. for p
>
> roject com.envoisolutions.sxc:sxc-runtime at
> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
> is invalid. It will be ignored for artifact resolution. Reason: Not a
> v4.0.0 POM. for p
>
> roject com.envoisolutions.sxc:sxc-runtime at
> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
> [INFO] [compiler:compile]
> [INFO] Compiling 20 source files to
> C:\g22\framework\buildsupport\car-maven-plugin\target\classes
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Compilation failure
> error: error reading
> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar;
> error in opening zip file
>
>
> error: error reading
> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar;
> error in opening zip file
>
>

Jay D. McHugh-2-3

Re: Could not build Geronimo server from SVN branch 2.2

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">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a
href="http://download.java.net/maven/1/com.envoisolutions.sxc/poms/sxc-runtime-0.7.2.pom">here</a>.</p>
<hr>
<address>Apache Server at maven-repository.dev.java.net Port 443</address>
</body></html>

So that is why it isn't working anymore.

Jay

Jay D. McHugh wrote:

> 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 starting from scratch (like yourself) or cleared their
> local repo - then they would start getting errors.
>
> We will try to see if we can find a good copy of the artifacts (or to
> have a good copy reloaded into the repos).
>
> Sorry for the trouble. Hopefully, we will be able to get things
> straightened out soon (for you and us as well).
>
> Jay
>
> Fei LI wrote:
>> 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 did not work too.
>>
>> So far, I tried 2.1.4, 2.2 and trunk and no one works.
>>
>>
>> Anybody ever clean your repo and build from nothing just kie me? Try!
>> Please!!! Tell me how to build then.
>>
>>
>> Thanks
>>
>> Fei Li
>>
>> See my error:
>>
>> [INFO] [enforcer:enforce {execution: default}]
>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>> v4.0.0 POM. for p
>>
>> roject com.envoisolutions.sxc:sxc-runtime at
>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>> v4.0.0 POM. for p
>>
>> roject com.envoisolutions.sxc:sxc-runtime at
>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>> [INFO] [plugin:descriptor]
>> [INFO] Using 'UTF-8' encoding to read mojo metadata.
>> [INFO] Applying mojo extractor for language: java
>> [WARNING] org.apache.geronimo.mavenplugins.car.ArchiveCarMojo#jarArchiver:
>> [WARNING] The syntax
>> [WARNING] @parameter expression="${component.<role>#<roleHint>}"
>> [WARNING] is deprecated, please use
>> [WARNING] @component role="<role>" roleHint="<roleHint>"
>> [WARNING] instead.
>> [INFO] Mojo extractor for language: java found 10 mojo descriptors.
>> [INFO] Applying mojo extractor for language: bsh
>> [INFO] Mojo extractor for language: bsh found 0 mojo descriptors.
>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>> v4.0.0 POM. for p
>>
>> roject com.envoisolutions.sxc:sxc-runtime at
>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>> v4.0.0 POM. for p
>>
>> roject com.envoisolutions.sxc:sxc-runtime at
>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>> [INFO] [remote-resources:process {execution: default}]
>> [WARNING] Attempting to build MavenProject instance for Artifact
>> (com.envoisolutions.sxc:sxc-runtime:0.7.2) of type: jar; constructing
>> POM artifact instead.
>>
>> [WARNING] Invalid project model for artifact
>> [sxc-runtime:com.envoisolutions.sxc:0.7.2]. It will be ignored by the
>> remote resources Mojo.
>>
>> [INFO] [resources:resources]
>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>> [INFO] Copying 1 resource
>> [INFO] skip non existing resourceDirectory
>> C:\g22\framework\buildsupport\car-maven-plugin\src\main\filtered-resources
>> [INFO] Copying 3 resources
>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>> v4.0.0 POM. for p
>>
>> roject com.envoisolutions.sxc:sxc-runtime at
>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>> v4.0.0 POM. for p
>>
>> roject com.envoisolutions.sxc:sxc-runtime at
>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>> [INFO] [compiler:compile]
>> [INFO] Compiling 20 source files to
>> C:\g22\framework\buildsupport\car-maven-plugin\target\classes
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Compilation failure
>> error: error reading
>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar;
>> error in opening zip file
>>
>>
>> error: error reading
>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar;
>> error in opening zip file
>>
>>

Joe Bohn-3

Re: Could not build Geronimo server from SVN branch 2.2

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 and it seems that some other project must
include this maven-repository.dev.java.net and is attempting to pull
some common dependencies from it (like log4j and yoko). Instead of
returning a failure the repo is returning this bogus pom. So it seems
that 2 things need to happen:

1) What ever project that is (need to find it) - it needs to update to
the new repository.
2) A failure should be returned from the old repo rather than these
bogus poms.

Joe

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">
> <html><head>
> <title>301 Moved Permanently</title>
> </head><body>
> <h1>Moved Permanently</h1>
> <p>The document has moved <a
> href="http://download.java.net/maven/1/com.envoisolutions.sxc/poms/sxc-runtime-0.7.2.pom">here</a>.</p>
> <hr>
> <address>Apache Server at maven-repository.dev.java.net Port 443</address>
> </body></html>
>
> So that is why it isn't working anymore.
>
> Jay
>
> Jay D. McHugh wrote:
>> 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 starting from scratch (like yourself) or cleared their
>> local repo - then they would start getting errors.
>>
>> We will try to see if we can find a good copy of the artifacts (or to
>> have a good copy reloaded into the repos).
>>
>> Sorry for the trouble. Hopefully, we will be able to get things
>> straightened out soon (for you and us as well).
>>
>> Jay
>>
>> Fei LI wrote:
>>> 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 did not work too.
>>>
>>> So far, I tried 2.1.4, 2.2 and trunk and no one works.
>>>
>>>
>>> Anybody ever clean your repo and build from nothing just kie me? Try!
>>> Please!!! Tell me how to build then.
>>>
>>>
>>> Thanks
>>>
>>> Fei Li
>>>
>>> See my error:
>>>
>>> [INFO] [enforcer:enforce {execution: default}]
>>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>> v4.0.0 POM. for p
>>>
>>> roject com.envoisolutions.sxc:sxc-runtime at
>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>> v4.0.0 POM. for p
>>>
>>> roject com.envoisolutions.sxc:sxc-runtime at
>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>> [INFO] [plugin:descriptor]
>>> [INFO] Using 'UTF-8' encoding to read mojo metadata.
>>> [INFO] Applying mojo extractor for language: java
>>> [WARNING] org.apache.geronimo.mavenplugins.car.ArchiveCarMojo#jarArchiver:
>>> [WARNING] The syntax
>>> [WARNING] @parameter expression="${component.<role>#<roleHint>}"
>>> [WARNING] is deprecated, please use
>>> [WARNING] @component role="<role>" roleHint="<roleHint>"
>>> [WARNING] instead.
>>> [INFO] Mojo extractor for language: java found 10 mojo descriptors.
>>> [INFO] Applying mojo extractor for language: bsh
>>> [INFO] Mojo extractor for language: bsh found 0 mojo descriptors.
>>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>> v4.0.0 POM. for p
>>>
>>> roject com.envoisolutions.sxc:sxc-runtime at
>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>> v4.0.0 POM. for p
>>>
>>> roject com.envoisolutions.sxc:sxc-runtime at
>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>> [INFO] [remote-resources:process {execution: default}]
>>> [WARNING] Attempting to build MavenProject instance for Artifact
>>> (com.envoisolutions.sxc:sxc-runtime:0.7.2) of type: jar; constructing
>>> POM artifact instead.
>>>
>>> [WARNING] Invalid project model for artifact
>>> [sxc-runtime:com.envoisolutions.sxc:0.7.2]. It will be ignored by the
>>> remote resources Mojo.
>>>
>>> [INFO] [resources:resources]
>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>> [INFO] Copying 1 resource
>>> [INFO] skip non existing resourceDirectory
>>> C:\g22\framework\buildsupport\car-maven-plugin\src\main\filtered-resources
>>> [INFO] Copying 3 resources
>>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>> v4.0.0 POM. for p
>>>
>>> roject com.envoisolutions.sxc:sxc-runtime at
>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>> [WARNING] POM for 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>> v4.0.0 POM. for p
>>>
>>> roject com.envoisolutions.sxc:sxc-runtime at
>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>> [INFO] [compiler:compile]
>>> [INFO] Compiling 20 source files to
>>> C:\g22\framework\buildsupport\car-maven-plugin\target\classes
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Compilation failure
>>> error: error reading
>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar;
>>> error in opening zip file
>>>
>>>
>>> error: error reading
>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar;
>>> error in opening zip file
>>>
>>>
>

kevan

Re: Could not build Geronimo server from SVN branch 2.2

Administrator

In reply to this post by Jay D. McHugh-2-3

On Nov 9, 2009, at 5:28 PM, Jay D. McHugh wrote:

Some background, I think -- http://old.nabble.com/Stuck%2C-cannot-build%2C-repository-down---td24941611.html

I've seen both pom's and jar's end up with the above html content.

--kevan

Joe Bohn-3

Re: Could not build Geronimo server from SVN branch 2.2

In reply to this post by Joe Bohn-3

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 2.2.1 (I was using 2.0.10) doesn't handle the redirects
any better and so doesn't fix the problem.
- For tags/2.1.4 maven 2.2.1 also causes other problems so it's best to
stick with maven 2.1.10 of you are building Geronimo 2.1.*
- org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a repository list that
points to https://maven-repository.dev.java.net/nonav/repositorid of
java.net so this is why we are pulling in that repo
- If I add the following to my settings.xml for maven I can avoid the
redirect (and hence avoid the bogus poms/jars) and get beyond this
problem to build Geronimo 2.1.4 using maven 2.0.10.

<mirrors>
<mirror>
<id>java.net</id>
<name>Mirror of
https://maven-repository.dev.java.net/nonav/repository/</name>
<url>http://download.java.net/maven/1/</url>
<mirrorOf>java.net</mirrorOf>
</mirror>
</mirrors>

Joe

Joe Bohn wrote:

> 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 and it seems that some other project must
> include this maven-repository.dev.java.net and is attempting to pull
> some common dependencies from it (like log4j and yoko). Instead of
> returning a failure the repo is returning this bogus pom. So it seems
> that 2 things need to happen:
>
> 1) What ever project that is (need to find it) - it needs to update to
> the new repository.
> 2) A failure should be returned from the old repo rather than these
> bogus poms.
>
>
> Joe
>
>
>
> 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">
>> <html><head>
>> <title>301 Moved Permanently</title>
>> </head><body>
>> <h1>Moved Permanently</h1>
>> <p>The document has moved <a
>> href="http://download.java.net/maven/1/com.envoisolutions.sxc/poms/sxc-runtime-0.7.2.pom">here</a>.</p>
>>
>> <hr>
>> <address>Apache Server at maven-repository.dev.java.net Port
>> 443</address>
>> </body></html>
>>
>> So that is why it isn't working anymore.
>>
>> Jay
>>
>> Jay D. McHugh wrote:
>>> 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 starting from scratch (like yourself) or cleared their
>>> local repo - then they would start getting errors.
>>>
>>> We will try to see if we can find a good copy of the artifacts (or to
>>> have a good copy reloaded into the repos).
>>>
>>> Sorry for the trouble. Hopefully, we will be able to get things
>>> straightened out soon (for you and us as well).
>>>
>>> Jay
>>>
>>> Fei LI wrote:
>>>> 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 did not work too.
>>>>
>>>> So far, I tried 2.1.4, 2.2 and trunk and no one works.
>>>>
>>>>
>>>> Anybody ever clean your repo and build from nothing just kie me? Try!
>>>> Please!!! Tell me how to build then.
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Fei Li
>>>>
>>>> See my error:
>>>>
>>>> [INFO] [enforcer:enforce {execution: default}]
>>>> [WARNING] POM for
>>>> 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>>> v4.0.0 POM. for p
>>>>
>>>> roject com.envoisolutions.sxc:sxc-runtime at
>>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>>>
>>>> [WARNING] POM for
>>>> 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>>> v4.0.0 POM. for p
>>>>
>>>> roject com.envoisolutions.sxc:sxc-runtime at
>>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>>>
>>>> [INFO] [plugin:descriptor]
>>>> [INFO] Using 'UTF-8' encoding to read mojo metadata.
>>>> [INFO] Applying mojo extractor for language: java
>>>> [WARNING]
>>>> org.apache.geronimo.mavenplugins.car.ArchiveCarMojo#jarArchiver:
>>>> [WARNING] The syntax
>>>> [WARNING] @parameter expression="${component.<role>#<roleHint>}"
>>>> [WARNING] is deprecated, please use
>>>> [WARNING] @component role="<role>" roleHint="<roleHint>"
>>>> [WARNING] instead.
>>>> [INFO] Mojo extractor for language: java found 10 mojo descriptors.
>>>> [INFO] Applying mojo extractor for language: bsh
>>>> [INFO] Mojo extractor for language: bsh found 0 mojo descriptors.
>>>> [WARNING] POM for
>>>> 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>>> v4.0.0 POM. for p
>>>>
>>>> roject com.envoisolutions.sxc:sxc-runtime at
>>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>>>
>>>> [WARNING] POM for
>>>> 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>>> v4.0.0 POM. for p
>>>>
>>>> roject com.envoisolutions.sxc:sxc-runtime at
>>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>>>
>>>> [INFO] [remote-resources:process {execution: default}]
>>>> [WARNING] Attempting to build MavenProject instance for Artifact
>>>> (com.envoisolutions.sxc:sxc-runtime:0.7.2) of type: jar; constructing
>>>> POM artifact instead.
>>>>
>>>> [WARNING] Invalid project model for artifact
>>>> [sxc-runtime:com.envoisolutions.sxc:0.7.2]. It will be ignored by the
>>>> remote resources Mojo.
>>>>
>>>> [INFO] [resources:resources]
>>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>>> [INFO] Copying 1 resource
>>>> [INFO] skip non existing resourceDirectory
>>>> C:\g22\framework\buildsupport\car-maven-plugin\src\main\filtered-resources
>>>>
>>>> [INFO] Copying 3 resources
>>>> [WARNING] POM for
>>>> 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>>> v4.0.0 POM. for p
>>>>
>>>> roject com.envoisolutions.sxc:sxc-runtime at
>>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>>>
>>>> [WARNING] POM for
>>>> 'com.envoisolutions.sxc:sxc-runtime:pom:0.7.2:compile'
>>>> is invalid. It will be ignored for artifact resolution. Reason: Not a
>>>> v4.0.0 POM. for p
>>>>
>>>> roject com.envoisolutions.sxc:sxc-runtime at
>>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.pom
>>>>
>>>> [INFO] [compiler:compile]
>>>> [INFO] Compiling 20 source files to
>>>> C:\g22\framework\buildsupport\car-maven-plugin\target\classes
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [ERROR] BUILD FAILURE
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] Compilation failure
>>>> error: error reading
>>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar;
>>>>
>>>> error in opening zip file
>>>>
>>>>
>>>> error: error reading
>>>> C:\m2repo\com\envoisolutions\sxc\sxc-runtime\0.7.2\sxc-runtime-0.7.2.jar;
>>>>
>>>> error in opening zip file
>>>>
>>>>
>>
>
>

kevan

Re: Could not build Geronimo server from SVN branch 2.2

Administrator

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 was requested and persists it as such.
> - Using Maven 2.2.1 (I was using 2.0.10) doesn't handle the
> redirects any better and so doesn't fix the problem.
> - For tags/2.1.4 maven 2.2.1 also causes other problems so it's best
> to stick with maven 2.1.10 of you are building Geronimo 2.1.*
> - org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a repository list
> that points to https://maven-repository.dev.java.net/nonav/
> repositorid of java.net so this is why we are pulling in that repo
> - If I add the following to my settings.xml for maven I can avoid
> the redirect (and hence avoid the bogus poms/jars) and get beyond
> this problem to build Geronimo 2.1.4 using maven 2.0.10.
>
> <mirrors>
> <mirror>
> <id>java.net</id>
> <name>Mirror of https://maven-repository.dev.java.net/nonav/repository
> /</name>
> <url>http://download.java.net/maven/1/</url>
> <mirrorOf>java.net</mirrorOf>
> </mirror>
> </mirrors>

Thanks Joe! I tried a mirror setting, but must not have gotten the
mirror setting correct...

--kevan

Joe Bohn-3

Re: Could not build Geronimo server from SVN branch 2.2

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 actual
>> file that was requested and persists it as such.
>> - Using Maven 2.2.1 (I was using 2.0.10) doesn't handle the redirects
>> any better and so doesn't fix the problem.
>> - For tags/2.1.4 maven 2.2.1 also causes other problems so it's best
>> to stick with maven 2.1.10 of you are building Geronimo 2.1.*
>> - org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a repository list
>> that points to https://maven-repository.dev.java.net/nonav/repositorid
>> of java.net so this is why we are pulling in that repo
>> - If I add the following to my settings.xml for maven I can avoid the
>> redirect (and hence avoid the bogus poms/jars) and get beyond this
>> problem to build Geronimo 2.1.4 using maven 2.0.10.
>>
>> <mirrors>
>> <mirror>
>> <id>java.net</id>
>> <name>Mirror of
>> https://maven-repository.dev.java.net/nonav/repository/</name>
>> <url>http://download.java.net/maven/1/</url>
>> <mirrorOf>java.net</mirrorOf>
>> </mirror>
>> </mirrors>
>
> Thanks Joe! I tried a mirror setting, but must not have gotten the
> mirror setting correct...
>
> --kevan
>

I think they key is that the <mirrorOf> value in your mirror must match
the <id> that is used in the original reference to the repository. In
the case of 2.1.4 it was pulling in yoko which had a parent pom with the
following repository entry:

<repository>
<id>java.net</id>
<name>java.net Maven Repository</name>

<url>https://maven-repository.dev.java.net/nonav/repository/</url>
<layout>legacy</layout>
</repository>

So when I created my mirror in settings.xml I included "java.net" in my
<mirrorOf> value. I also included the same value in the <id> of my
mirror but I don't think that is necessary.

Joe

jeffche

Re: Could not build Geronimo server from SVN branch 2.2

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 <[hidden email]> wrote:

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 actual file that was requested and persists it as such.
- Using Maven 2.2.1 (I was using 2.0.10) doesn't handle the redirects any better and so doesn't fix the problem.
- For tags/2.1.4 maven 2.2.1 also causes other problems so it's best to stick with maven 2.1.10 of you are building Geronimo 2.1.*
- org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a repository list that points to https://maven-repository.dev.java.net/nonav/repositorid of java.net so this is why we are pulling in that repo
- If I add the following to my settings.xml for maven I can avoid the redirect (and hence avoid the bogus poms/jars) and get beyond this problem to build Geronimo 2.1.4 using maven 2.0.10.

<mirrors>
<mirror>
<id>java.net</id>
<name>Mirror of https://maven-repository.dev.java.net/nonav/repository/</name>
<url>http://download.java.net/maven/1/</url>
<mirrorOf>java.net</mirrorOf>
</mirror>
</mirrors>

Thanks Joe! I tried a mirror setting, but must not have gotten the mirror setting correct...

--kevan

I think they key is that the <mirrorOf> value in your mirror must match the <id> that is used in the original reference to the repository. In the case of 2.1.4 it was pulling in yoko which had a parent pom with the following repository entry:

<repository>
<id>java.net</id>
<name>java.net Maven Repository</name>

<url>https://maven-repository.dev.java.net/nonav/repository/</url>
<layout>legacy</layout>
</repository>

So when I created my mirror in settings.xml I included "java.net" in my <mirrorOf> value. I also included the same value in the <id> of my mirror but I don't think that is necessary.

Joe

Fei LI-2

RE: Could not build Geronimo server from SVN branch 2.2

In reply to this post by Fei LI-2

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 tell me how many problems you find. Not 1, not 2, not 3 even not 4, many, as far as I can tell you.

Anyway, I will monitor the trunk to see if someday I can compile it. The trunk is where I should start.

Thanks for guys who helped me.

Fei Li

From: chi runhua [mailto:[hidden email]]
Sent: Tue 10/11/2009 6:46 AM
To: [hidden email]
Subject: Re: Could not build Geronimo server from SVN branch 2.2

If you intend to build the 2.2 server, you may download the very .jar from [1] and then place it in your local maven repository.

[1] http://www.jarvana.com/jarvana/browse/com/envoisolutions/sxc/sxc-runtime/0.7.2/

This workaround can bypass the build error successfully.

Any problem, please let us know.

Jeff C

On Tue, Nov 10, 2009 at 9:42 PM, ericp56 <[hidden email]> wrote:

It looks like the build process has the same problem:

http://old.nabble.com/-BUILD--branches-2.2%3A-Failed-for-Revision%3A-834455-ts26283051s134.html
http://old.nabble.com/-BUILD--branches-2.2%3A-Failed-for-Revision%3A-834455-ts26283051s134.html

I've had problems in the past - mostly windows issues.

I've had success building, using Maven 2.2.0 and Java JDK 6_0_14.

I've been trying recently and I'm running into issues, too. I see David
Jencks making comments about build dependency issues.

I'm guessing the Geronimo-Dev is a better forum for build issues? I'll see
you there...

Eric
--
View this message in context: http://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.

Joe Bohn-3

Re: Could not build Geronimo server from SVN branch 2.2

In reply to this post by jeffche

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 removed
from https://maven-repository.dev.java.net/nonav/repository/ ... but the
net result would be that our builds would still fail because we would
never get the artifacts that we need from that repo or its replacement.

Any ideas?

Joe

chi runhua wrote:

> 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 <[hidden email]
> <mailto:[hidden email]>> wrote:
>
> 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 actual file that was requested and persists it as such.
> - Using Maven 2.2.1 (I was using 2.0.10) doesn't handle the
> redirects any better and so doesn't fix the problem.
> - For tags/2.1.4 maven 2.2.1 also causes other problems so
> it's best to stick with maven 2.1.10 of you are building
> Geronimo 2.1.*
> - org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a
> repository list that points to
> https://maven-repository.dev.java.net/nonav/repositorid of
> java.net <http://java.net/> so this is why we are pulling in
> that repo
> - If I add the following to my settings.xml for maven I can
> avoid the redirect (and hence avoid the bogus poms/jars) and
> get beyond this problem to build Geronimo 2.1.4 using maven
> 2.0.10.
>
> <mirrors>
> <mirror>
> <id>java.net <http://java.net/></id>
> <name>Mirror of
> https://maven-repository.dev.java.net/nonav/repository/</name>
> <url>http://download.java.net/maven/1/</url>
> <mirrorOf>java.net <http://java.net/></mirrorOf>
> </mirror>
> </mirrors>
>
>
> Thanks Joe! I tried a mirror setting, but must not have gotten
> the mirror setting correct...
>
> --kevan
>
>
> I think they key is that the <mirrorOf> value in your mirror must
> match the <id> that is used in the original reference to the
> repository. In the case of 2.1.4 it was pulling in yoko which had a
> parent pom with the following repository entry:
>
> <repository>
> <id>java.net <http://java.net/></id>
> <name>java.net <http://java.net/> Maven Repository</name>
>
> <url>https://maven-repository.dev.java.net/nonav/repository/</url>
> <layout>legacy</layout>
> </repository>
>
> So when I created my mirror in settings.xml I included "java.net
> <http://java.net/>" in my <mirrorOf> value. I also included the
> same value in the <id> of my mirror but I don't think that is necessary.
>
> Joe
>
>
>

kevan

Re: Could not build Geronimo server from SVN branch 2.2

Administrator

In reply to this post by Fei LI-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 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 tell me how many problems you find. Not 1, not 2, not 3 even not 4, many, as far as I can tell you.

Anyway, I will monitor the trunk to see if someday I can compile it. The trunk is where I should start.

Hi Fei Li,
There are multiple threads on multiple mailing lists for this same problem.

There was a general problem that seems to be a combination of an issue with configuration changes to the maven repository at maven2-repository.dev.java.net and potentially a bug in the maven dependency report plugin. See http://old.nabble.com/Stuck%2C-cannot-build%2C-repository-down---td24941611.html for additional information.

To fix your issue:

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 was requested and persists it as such.
- Using Maven 2.2.1 (I was using 2.0.10) doesn't handle the redirects any better and so doesn't fix the problem.
- For tags/2.1.4 maven 2.2.1 also causes other problems so it's best to stick with maven 2.1.10 of you are building Geronimo 2.1.*
- org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a repository list that points to https://maven-repository.dev.java.net/nonav/repositorid of java.net so this is why we are pulling in that repo
- If I add the following to my settings.xml for maven I can avoid the redirect (and hence avoid the bogus poms/jars) and get beyond this problem to build Geronimo 2.1.4 using maven 2.0.10.

   <mirrors>
       <mirror>
           <id>java.net</id>
           <name>Mirror of https://maven-repository.dev.java.net/nonav/repository/</name>
           <url>http://download.java.net/maven/1/</url>
           <mirrorOf>java.net</mirrorOf>
       </mirror>
   </mirrors>

Now documented at http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html

If you are interested in working on the development of Geronimo 3.0, you'd be more than welcome. If you are interested in using Geronimo, I would not recommend using trunk. You should be using geronimo/server/branches/2.2 or geronimo/server/tags/2.1.4, instead.

--kevan

Joe Bohn-3

Re: Could not build Geronimo server from SVN branch 2.2

In reply to this post by Joe Bohn-3

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:
https://svn.apache.org/repos/asf/geronimo/server/branches/2.2
Maven 2.2.1
jdk 1.6.0_15 (mac)

2.1.4:
https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4
Maven 2.0.10
jdk 1.5.0_20 (mac)

Joe

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 this repo? We could push to get the redirect removed
> from https://maven-repository.dev.java.net/nonav/repository/ ... but the
> net result would be that our builds would still fail because we would
> never get the artifacts that we need from that repo or its replacement.
>
> Any ideas?
>
> Joe
>
>
> chi runhua wrote:
>> 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 <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>> 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 actual file that was requested and persists it as
>> such.
>> - Using Maven 2.2.1 (I was using 2.0.10) doesn't handle the
>> redirects any better and so doesn't fix the problem.
>> - For tags/2.1.4 maven 2.2.1 also causes other problems so
>> it's best to stick with maven 2.1.10 of you are building
>> Geronimo 2.1.*
>> - org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a
>> repository list that points to
>> https://maven-repository.dev.java.net/nonav/repositorid of
>> java.net <http://java.net/> so this is why we are pulling in
>> that repo
>> - If I add the following to my settings.xml for maven I can
>> avoid the redirect (and hence avoid the bogus poms/jars) and
>> get beyond this problem to build Geronimo 2.1.4 using maven
>> 2.0.10.
>>
>> <mirrors>
>> <mirror>
>> <id>java.net <http://java.net/></id>
>> <name>Mirror of
>>
>> https://maven-repository.dev.java.net/nonav/repository/</name>
>> <url>http://download.java.net/maven/1/</url>
>> <mirrorOf>java.net <http://java.net/></mirrorOf>
>> </mirror>
>> </mirrors>
>>
>>
>> Thanks Joe! I tried a mirror setting, but must not have gotten
>> the mirror setting correct...
>>
>> --kevan
>>
>>
>> I think they key is that the <mirrorOf> value in your mirror must
>> match the <id> that is used in the original reference to the
>> repository. In the case of 2.1.4 it was pulling in yoko which had a
>> parent pom with the following repository entry:
>>
>> <repository>
>> <id>java.net <http://java.net/></id>
>> <name>java.net <http://java.net/> Maven Repository</name>
>>
>> <url>https://maven-repository.dev.java.net/nonav/repository/</url>
>> <layout>legacy</layout>
>> </repository>
>>
>> So when I created my mirror in settings.xml I included "java.net
>> <http://java.net/>" in my <mirrorOf> value. I also included the
>> same value in the <id> of my mirror but I don't think that is
>> necessary.
>>
>> Joe
>>
>>
>>
>
>

Joe Bohn-3

Re: Could not build Geronimo server from SVN branch 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 1.5.0_20 (mac)

Joe

Joe Bohn wrote:

> 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:
> https://svn.apache.org/repos/asf/geronimo/server/branches/2.2
> Maven 2.2.1
> jdk 1.6.0_15 (mac)
>
> 2.1.4:
> https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4
> Maven 2.0.10
> jdk 1.5.0_20 (mac)
>
>
> Joe
>
> 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 this repo? We could push to get the redirect
>> removed from https://maven-repository.dev.java.net/nonav/repository/
>> ... but the net result would be that our builds would still fail
>> because we would never get the artifacts that we need from that repo
>> or its replacement.
>>
>> Any ideas?
>>
>> Joe
>>
>>
>> chi runhua wrote:
>>> 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 <[hidden email]
>>> <mailto:[hidden email]>> wrote:
>>>
>>> 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 actual file that was requested and persists it as
>>> such.
>>> - Using Maven 2.2.1 (I was using 2.0.10) doesn't handle the
>>> redirects any better and so doesn't fix the problem.
>>> - For tags/2.1.4 maven 2.2.1 also causes other problems so
>>> it's best to stick with maven 2.1.10 of you are building
>>> Geronimo 2.1.*
>>> - org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a
>>> repository list that points to
>>> https://maven-repository.dev.java.net/nonav/repositorid of
>>> java.net <http://java.net/> so this is why we are pulling in
>>> that repo
>>> - If I add the following to my settings.xml for maven I can
>>> avoid the redirect (and hence avoid the bogus poms/jars) and
>>> get beyond this problem to build Geronimo 2.1.4 using maven
>>> 2.0.10.
>>>
>>> <mirrors>
>>> <mirror>
>>> <id>java.net <http://java.net/></id>
>>> <name>Mirror of
>>>
>>> https://maven-repository.dev.java.net/nonav/repository/</name>
>>> <url>http://download.java.net/maven/1/</url>
>>> <mirrorOf>java.net <http://java.net/></mirrorOf>
>>> </mirror>
>>> </mirrors>
>>>
>>>
>>> Thanks Joe! I tried a mirror setting, but must not have gotten
>>> the mirror setting correct...
>>>
>>> --kevan
>>>
>>>
>>> I think they key is that the <mirrorOf> value in your mirror must
>>> match the <id> that is used in the original reference to the
>>> repository. In the case of 2.1.4 it was pulling in yoko which had a
>>> parent pom with the following repository entry:
>>>
>>> <repository>
>>> <id>java.net <http://java.net/></id>
>>> <name>java.net <http://java.net/> Maven Repository</name>
>>>
>>> <url>https://maven-repository.dev.java.net/nonav/repository/</url>
>>> <layout>legacy</layout>
>>> </repository>
>>>
>>> So when I created my mirror in settings.xml I included "java.net
>>> <http://java.net/>" in my <mirrorOf> value. I also included the
>>> same value in the <id> of my mirror but I don't think that is
>>> necessary.
>>>
>>> Joe
>>>
>>>
>>>
>>
>>
>
>

kevan

Re: Could not build Geronimo server from SVN branch 2.2

Administrator

In reply to this post by Joe Bohn-3

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 this repo? We could push to get the redirect
> removed from https://maven-repository.dev.java.net/nonav/
> repository/ ... but the net result would be that our builds would
> still fail because we would never get the artifacts that we need
> from that repo or its replacement.
>
> Any ideas?

I believe that the fundamental "problem" is in the maven dependency
report plugin. So, fixing that would seem to be the way to truly fix
the problem. Well, I guess java.net could move the repo back to the
original location. Anyway, seems like we have an acceptable solution,
for now...

--kevan

Fei LI-2

RE: Could not build Geronimo server from SVN branch 2.2

In reply to this post by kevan

Hi,

My build of Geronimo server branch 2.2 is successful. Great.

Thanks a lot to

Keven, Donald, Joe, Jeff and Forrest
<https://webmail.mda.ca/exchweb/bin/redir.asp?URL=http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html>
This is a big system and I need some time to learn it.

________________________________

From: Kevan Miller [mailto:[hidden email]]
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:

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 tell me how many problems you find. Not 1, not 2, not 3 even not 4, many, as far as I can tell you.

Anyway, I will monitor the trunk to see if someday I can compile it. The trunk is where I should start.

Hi Fei Li,
There are multiple threads on multiple mailing lists for this same problem.

There was a general problem that seems to be a combination of an issue with configuration changes to the maven repository at maven2-repository.dev.java.net <http://maven2-repository.dev.java.net/> and potentially a bug in the maven dependency report plugin. See http://old.nabble.com/Stuck%2C-cannot-build%2C-repository-down---td24941611.html for additional information.

To fix your issue:

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 was requested and persists it as such.
- Using Maven 2.2.1 (I was using 2.0.10) doesn't handle the redirects any better and so doesn't fix the problem.
- For tags/2.1.4 maven 2.2.1 also causes other problems so it's best to stick with maven 2.1.10 of you are building Geronimo 2.1.*
- org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a repository list that points to https://maven-repository.dev.java.net/nonav/repositorid of java.net <http://java.net/> so this is why we are pulling in that repo
- If I add the following to my settings.xml for maven I can avoid the redirect (and hence avoid the bogus poms/jars) and get beyond this problem to build Geronimo 2.1.4 using maven 2.0.10.

<mirrors>
<mirror>
<id>java.net</id>
<name>Mirror of https://maven-repository.dev.java.net/nonav/repository/</name>
<url>http://download.java.net/maven/1/</url>
<mirrorOf>java.net</mirrorOf>
</mirror>
</mirrors>

Now documented at http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html

If you are interested in working on the development of Geronimo 3.0, you'd be more than welcome. If you are interested in using Geronimo, I would not recommend using trunk. You should be using geronimo/server/branches/2.2 or geronimo/server/tags/2.1.4, instead.

--kevan

winmail.dat (10K) Download Attachment

jeffche

Re: Could not build Geronimo server from SVN branch 2.2

Congratulation~!

Feel free to drop an email if you have any other questions. We'd love to help you learn Geronimo.

Jeff

On Thu, Nov 12, 2009 at 12:24 PM, Fei LI <[hidden email]> wrote:

Hi,

My build of Geronimo server branch 2.2 is successful. Great.

Thanks a lot to

Keven, Donald, Joe, Jeff and Forrest
<https://webmail.mda.ca/exchweb/bin/redir.asp?URL=http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html>
This is a big system and I need some time to learn it.

________________________________

From: Kevan Miller [mailto:[hidden email]]
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:

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 tell me how many problems you find. Not 1, not 2, not 3 even not 4, many, as far as I can tell you.

Anyway, I will monitor the trunk to see if someday I can compile it. The trunk is where I should start.

Hi Fei Li,
There are multiple threads on multiple mailing lists for this same problem.

There was a general problem that seems to be a combination of an issue with configuration changes to the maven repository at maven2-repository.dev.java.net <http://maven2-repository.dev.java.net/> and potentially a bug in the maven dependency report plugin. See http://old.nabble.com/Stuck%2C-cannot-build%2C-repository-down---td24941611.html for additional information.

To fix your issue:

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 was requested and persists it as such.
- Using Maven 2.2.1 (I was using 2.0.10) doesn't handle the redirects any better and so doesn't fix the problem.
- For tags/2.1.4 maven 2.2.1 also causes other problems so it's best to stick with maven 2.1.10 of you are building Geronimo 2.1.*

- org/apache/yoko/yoko/1.0/yoko-1.0.pom includes a repository list that points to https://maven-repository.dev.java.net/nonav/repositorid of java.net <http://java.net/> so this is why we are pulling in that repo

- If I add the following to my settings.xml for maven I can avoid the redirect (and hence avoid the bogus poms/jars) and get beyond this problem to build Geronimo 2.1.4 using maven 2.0.10.

<mirrors>
<mirror>
<id>java.net</id>
<name>Mirror of https://maven-repository.dev.java.net/nonav/repository/</name>
<url>http://download.java.net/maven/1/</url>
<mirrorOf>java.net</mirrorOf>
</mirror>
</mirrors>

Now documented at http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html

If you are interested in working on the development of Geronimo 3.0, you'd be more than welcome. If you are interested in using Geronimo, I would not recommend using trunk. You should be using geronimo/server/branches/2.2 or geronimo/server/tags/2.1.4, instead.

--kevan