geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell E Glaue (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6004) Geronimo 3.0 trunk does not build unless you manually download and install geronimo-jaxws_2.2_spec-1.0.jar into your local maven repo
Date Fri, 10 Jun 2011 16:37:59 GMT


Russell E Glaue commented on GERONIMO-6004:

Okay, the build has the "does not exist" error I remember.

[INFO] ------------------------------------------------------------------------
[INFO] Building Geronimo Plugins, J2EE :: Builder 3.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ geronimo-j2ee-builder ---
[INFO] Deleting file set:
(included: [**], excluded: [])
[INFO] --- genesis-maven-plugin:2.0:validate-configuration (default) @
geronimo-j2ee-builder ---
[INFO] --- geronimo-property-plugin:3.0-SNAPSHOT:set-property (set-property) @
geronimo-j2ee-builder ---
does not exist
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (default) @
geronimo-j2ee-builder ---
[INFO] --- xmlbeans-maven-plugin:2.3.3:xmlbeans (default) @
geronimo-j2ee-builder ---
Time to build schema type system: 7.202 seconds
Time to generate code: 0.235 seconds
Time to compile code: 2.974 seconds

I think I may understand the issue, maybe.

The specific file
depends on the 1.0 artifact
I have not looked at the artifact source code, but the error message I reported
suggested the api has changed between versions 1.0 and 1.1

So the geronimo-j2ee-builder should have a specific dependency on the 1.0
artifact. But it doesn't, so maven assumes it can use the latest available which
is 1.1-SNAPSHOT.

The geronimo-property-plugin however sets (or keeps track of (not sure how that
works)) the dependency properties for the geronimo-j2ee-builder - which includes
the geronimo-jaxws_2.2_spec-1.0 artifact.

However, this 1.0 dependency is kept track of in maven, so the artifact is not

The geronimo-j2ee-builder is compiled by maven, but fails dues to mismatched
version referencing changed API.

So it would seem the two resolutions are:
1. Update the
to support geronimo-jaxws_2.2_spec-1.1
2. Put in a specific dependency to the geronimo-jaxws_2.2_spec-1.0 artifact in

> Geronimo 3.0 trunk does not build unless you manually download and install geronimo-jaxws_2.2_spec-1.0.jar
into your local maven repo
> -------------------------------------------------------------------------------------------------------------------------------------
>                 Key: GERONIMO-6004
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Plugins
>    Affects Versions: 3.0
>         Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4 (Tikanga)
>            Reporter: Russell E Glaue
>            Priority: Minor
>              Labels: geronimo
> When building geronimo server/trunk, a.k.a. Geronimo 3.0, with maven 2.2.1 or 3.0.3 for
the first time, a user will get a WS related error.
> -
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project geronimo-j2ee-builder: Compilation failure: Compilation failure:
> [ERROR] /data/geronimo/asf-geronimo-server-trunk/plugins/j2ee/geronimo-j2ee-builder/src/main/java/org/apache/geronimo/j2ee/deployment/annotation/[178,39]
[deprecation] name() in javax.jws.HandlerChain has been deprecated
> [ERROR] 
> [ERROR] /data/geronimo/asf-geronimo-server-trunk/plugins/j2ee/geronimo-j2ee-builder/src/main/java/org/apache/geronimo/j2ee/deployment/annotation/[295,61]
cannot find symbol
> [ERROR] symbol  : method lookup()
> [ERROR] location: @interface
> [ERROR] 
> [ERROR] /data/geronimo/asf-geronimo-server-trunk/plugins/j2ee/geronimo-j2ee-builder/src/main/java/org/apache/geronimo/j2ee/deployment/annotation/[296,47]
cannot find symbol
> [ERROR] symbol  : method lookup()
> [ERROR] location: @interface
> [ERROR] 
> [ERROR] /data/geronimo/asf-geronimo-server-trunk/plugins/j2ee/geronimo-j2ee-builder/src/main/java/org/apache/geronimo/j2ee/deployment/annotation/[403,104]
cannot find symbol
> [ERROR] symbol  : method responses()
> [ERROR] location: @interface
> [ERROR] 
> [ERROR] /data/geronimo/asf-geronimo-server-trunk/plugins/j2ee/geronimo-j2ee-builder/src/main/java/org/apache/geronimo/j2ee/deployment/annotation/[413,108]
cannot find symbol
> [ERROR] symbol  : method responses()
> [ERROR] location: @interface
> -
> If the user manually downloads and installs the geronimo-jaxws_2.2_spec-1.0 artifact,
then the build succeeds.
> -
> mvn install:install-file -DgroupId=org.apache.geronimo.specs
> -DartifactId=geronimo-jaxws_2.2_spec -Dversion=1.0 -Dpackaging=jar
> -Dfile=geronimo-jaxws_2.2_spec-1.0.jar
> -
> From what I could discover, all of Geronimo 3.0 (trunk) depends on geronimo-jaxws_2.2_spec-1.1-SNAPSHOT
except for the uddi (uddi-war-repackage) plugin. The 1.1-SNAPSHOT dependency is downloaded
and installed correctly, but the 1.0 artifact is not - though I could tell through observation
of some alternate maven processes the build is specifically looking for the 1.0 artifact.
> The resolution is to either fix the maven dependency so that the geronimo-jaxws_2.2_spec-1.0
artifact is downloaded and installed automatically, or update the uddi plugin to support the
geronimo-jaxws_2.2_spec-1.1-SNAPSHOT artifact.
> -
> [ger@linux7 asf-geronimo-server-trunk]# egrep -R geronimo-jaxws_2.2_spec * | grep -v
".svn" | grep -i "1.0" | grep DEPENDENCIES
> plugins/uddi/uddi-war-repackage/target/classes/WEB-INF/classes/META-INF/DEPENDENCIES:
 - Apache Geronimo JAX-WS 2.2 API (
> -
> I assume it would be easier to setup the dependency to include the geronimo-jaxws_2.2_spec-1.0
artifact. And possibly there could be a good reason why the uddi plugin is the only part of
G3.0 not updated to support the 1.1-SNAPSHOT (though unknown to me at this time).
> It should also be noted, though not significant, that the LICENSE files of most all (if
not all) of the components of Geronimo reference the geronimo-jaxws_2.2_spec-1.0 artifact.
> The users who attempt to build G3.0 from trunk for the first time are going to experience
this issue which causes the build to fail. However, I was able to successfully build G3.0
from trunk when doing the following three steps:
> 1. Follow the documentation for building:
> 2. Set MAVEN_OPTS to the following: -Xmx968m -XX:MaxPermSize=700m -XX:ReservedCodeCacheSize=64m
> 3. Manually install the geronimo-jaxws_2.2_spec-1.0 artifact as I described above
> -RG

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message