Thanks for reporting this, I tried to remove the old jaxws spec 1.0 in my
local repo and then still can build uddi plugins without problems.
Anyway, something like this in root pom.xml to exclude jaxws spec
dependency from uddi-ws artifact would resolve this.
<dependency>
<groupId>org.apache.juddi</groupId>
<artifactId>uddi-ws</artifactId>
<version>${juddiv3.version}</version>
<exclusions>
<exclusion>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.xml.ws</groupId>
<artifactId>jaxws-rt</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
</exclusion>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
* <exclusion>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-jaxws_2.1_spec</artifactId>
</exclusion> *
</exclusions>
</dependency>
On Fri, Jun 10, 2011 at 10:24 PM, Russell E Glaue <rgl...@cait.org> wrote:
> G3.0 compiled!
>
> That means, the issue I reported is the only problem.
> This is the geronimo-jaxws_2.2_spec 1.0 maven bundle dependency.
> I will go an create a JIRA for that.
>
> The question is about the dependency on the 1.0 bundle, when Geronimo
> primarily
> depends on 1.1-SNAPSHOT. It would seem the uddi plugin is the only part of
> Geronimo that depends on the 1.0 bundle. I remember having problems around
> this
> plugin during the build.
> - plugins/uddi/uddi-war-repackage
>
>
> The result is, the build took 13+ hours, and a lot of memory. Though it
> will
> probably take more time and memory if none of the dependencies are
> downloaded.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 13:50:50.812s
> [INFO] Finished at: Fri Jun 10 06:58:46 EDT 2011
> [INFO] Final Memory: 470M/935M
> [INFO]
> ------------------------------------------------------------------------
>
> Here is my final MAVEN_OPTS
> -Xmx968m -XX:MaxPermSize=700m -XX:ReservedCodeCacheSize=64m
>
> Looking at the results, maybe that can be set to
> -Xmx968m -XX:MaxPermSize=500m -XX:ReservedCodeCacheSize=64m
>
>
> -RG
>
>
>
> On 06/08/2011 04:32 PM, Russell E Glaue wrote:
> > I got a little further this time
> >
> > I manually install the 1.0 jaxws spec file.
> > -
> > 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
> > -
> > And I got past that problem spot.
> > So that does seem to be what the problem was.
> > And that will need to be fixed, right?
> >
> >
> > The next error I get looks like a Permenant Generation memory/heap error.
> > -
> > [ERROR] Failed to execute goal
> > org.apache.geronimo.buildsupport:car-maven-plugin:3.0-SNAPSHOT:package
> > (default-package) on project uddi-tomcat: could not package plugin:
> Unable to
> > generate the wsdl file using wsgen. InvocationTargetException: PermGen
> space ->
> > [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> please
> > read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > [ERROR]
> > [ERROR] After correcting the problems, you can resume the build with the
> command
> > [ERROR] mvn <goals> -rf :uddi-tomcat
> > -
> >
> > So I will have to increase the heap.
> > Or perhaps it was exhausted due to all the bundle downloads the build
> process
> > had to do, and if I run it again now, I might get further?
> >
> >
> > I am seeing a few OSGi related issues like this one.
> > -
> > [INFO] Started deployer:
> > org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car
> > [INFO] Started deployer:
> org.apache.geronimo.configs/j2ee-deployer/3.0-SNAPSHOT/car
> > [INFO] Started deployer:
> > org.apache.geronimo.configs/jetty8-deployer/3.0-SNAPSHOT/car
> > [INFO] Started deployer:
> > org.apache.geronimo.configs/jasper-deployer/3.0-SNAPSHOT/car
> > [org.apache.geronimo.system.configuration.DependencyManager] : Could not
> start
> > bundle: org.apache.openjpa [171]
> > org.osgi.framework.BundleException: Unresolved constraint in bundle
> > org.apache.openjpa [171]: Unable to resolve 171.0: missing requirement
> [171.0]
> > package; (package=org.apache.commons.dbcp)
> > at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409)
> > at org.apache.felix.framework.Felix.startBundle(Felix.java:1709)
> > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
> > -
> >
> > And a quite a lot of log4 issues like this one:
> > -
> > [INFO] --- car-maven-plugin:3.0-SNAPSHOT:package (default-package) @
> uddi-jetty ---
> > [INFO] Packaging module configuration:
> >
> /data/geronimo/asf-geronimo-server-trunk/plugins/uddi/uddi-jetty/target/work/plan.xml
> > log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not assignable
> to a
> > "org.apache.log4j.Appender" variable.
> > log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
> > log4j:ERROR [25.0] whereas object of type
> > log4j:ERROR "org.apache.log4j.ConsoleAppender" was loaded by
> >
> [ClassRealm[plugin>org.apache.geronimo.buildsupport:car-maven-plugin:3.0-SNAPSHOT-424111508,
> > parent: sun.misc.Launcher$AppClassLoader@11b86e7]].
> > log4j:ERROR Could not instantiate appender named "CONSOLE".
> > log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not assignable
> to a
> > "org.apache.log4j.Appender" variable.
> > log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
> > log4j:ERROR [25.0] whereas object of type
> > log4j:ERROR "org.apache.log4j.ConsoleAppender" was loaded by
> >
> [ClassRealm[plugin>org.apache.geronimo.buildsupport:car-maven-plugin:3.0-SNAPSHOT-424111508,
> > parent: sun.misc.Launcher$AppClassLoader@11b86e7]].
> > log4j:ERROR Could not instantiate appender named "A1".
> > log4j:WARN No appenders could be found for logger
> > (org.apache.geronimo.specs.geronimo-osgi-registry).
> > log4j:WARN Please initialize the log4j system properly.
> > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
> more info.
> >
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> > : Enabling SLF4J API support.
> >
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> > : Enabling Jakarta Commons Logging API support.
> >
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> > : Enabling Log4J API support.
> >
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> > : Enabling Avalon Logger API support.
> >
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> > : Enabling JULI Logger API support.
> > log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not assignable
> to a
> > "org.apache.log4j.Appender" variable.
> > log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
> > log4j:ERROR [25.0] whereas object of type
> > log4j:ERROR "org.apache.log4j.ConsoleAppender" was loaded by
> >
> [ClassRealm[plugin>org.apache.geronimo.buildsupport:car-maven-plugin:3.0-SNAPSHOT-424111508,
> > parent: sun.misc.Launcher$AppClassLoader@11b86e7]].
> > log4j:ERROR Could not instantiate appender named "A1".
> > -
> >
> >
> > -RG
> >
> >
> >
> > On 06/08/2011 02:14 PM, Russell E Glaue wrote:
> >> Okay,
> >>
> >> I think I just put 2+2 together.
> >>
> >> 1. The build process complains of the missing geronimo-jaxws_2.2_spec
> 1.0
> >>
> >> 2. The error message received after only executing 'mvn clean install'
> is
> >> complaining about javax.xml.ws.* class stuff
> >>
> >> 3. When issuing 'mvn compile' then 'mvn clean install', the packaging
> error is
> >> complaining about com.sun.tools.ws.* stuff
> >>
> >> 4. The geronimo-jaxws_2.2_spec bundle actuall contains the
> javax.xml.ws.* stuff
> >>
> >>
> >> (light-bulb) I would conclude this is the problem.
> >>
> >> And those who have been compiling G3.0 since it was branched probably
> have the
> >> geronimo-jaxws_2.2_spec 1.0 bundle in your repository, and that is why
> you do
> >> not have the problem I report.
> >>
> >>
> >> So, the question is why doesn't the build process download and install
> the 1.0
> >> dependency of geronimo-jaxws_2.2_spec??
> >>
> >> If that question is solved, perhaps it will solve this issue.
> >>
> >>
> >> -RG
> >>
> >>
> >>
> >> On 06/08/2011 02:04 PM, Russell E Glaue wrote:
> >>> On 06/07/2011 06:21 PM, Kevan Miller wrote:
> >>>>
> >>>> Can you post more of the build output near the failure? I don't have a
> clear
> >>> picture of where in the build process you're getting this failure.
> >>>>
> >>>> I'm mostly building with maven 3. I asked about your maven version
> only to try
> >>> and pin down the source of your failure...
> >>>>
> >>>
> >>>
> >>> I have deleted my local maven repository (i.e. ~/.m2/repository), and
> got a
> >>> fresh checkout of geronimo-trunk. I then executed the maven clean
> install in
> >>> both maven 3.0.3 and 2.2.1 using JDK1.6.0_25.
> >>> I attached the output from a maven 2.2.1 build.
> >>>
> >>> I get the same error repeatedly. (see below)
> >>> I now actually remember getting this error message the very first time
> I tried
> >>> building G3.0. But these errors completely went away after the first
> time I
> >>> executed "mvn compile". So I had forgotten about it.
> >>>
> >>> After the first time executing 'mvn compile', any subsequent 'mvn clean
> install'
> >>> execution successfully compiled G3.0. Even when compiling a fresh
> trunk. Just
> >>> the packaging was unsuccessful (in which the error messages are given
> previously
> >>> in this thread).
> >>>
> >>> My only guess is that the 'mvn compile' target downloads and installs
> older or
> >>> newer bundle dependencies that do not cause these errors. The maven
> bundles are
> >>> the only things that do not change when you do as I did.
> >>>
> >>> -
> >>> [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/HandlerChainAnnotationHelper.java:[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/WebServiceRefAnnotationHelper.java:[295,61]
> >>> cannot find symbol
> >>> [ERROR] symbol : method lookup()
> >>> [ERROR] location: @interface javax.xml.ws.WebServiceRef
> >>> [ERROR]
> >>> [ERROR]
> >>>
> /data/geronimo/asf-geronimo-server-trunk/plugins/j2ee/geronimo-j2ee-builder/src/main/java/org/apache/geronimo/j2ee/deployment/annotation/WebServiceRefAnnotationHelper.java:[296,47]
> >>> cannot find symbol
> >>> [ERROR] symbol : method lookup()
> >>> [ERROR] location: @interface javax.xml.ws.WebServiceRef
> >>> [ERROR]
> >>> [ERROR]
> >>>
> /data/geronimo/asf-geronimo-server-trunk/plugins/j2ee/geronimo-j2ee-builder/src/main/java/org/apache/geronimo/j2ee/deployment/annotation/WebServiceRefAnnotationHelper.java:[403,104]
> >>> cannot find symbol
> >>> [ERROR] symbol : method responses()
> >>> [ERROR] location: @interface javax.xml.ws.soap.Addressing
> >>> [ERROR]
> >>> [ERROR]
> >>>
> /data/geronimo/asf-geronimo-server-trunk/plugins/j2ee/geronimo-j2ee-builder/src/main/java/org/apache/geronimo/j2ee/deployment/annotation/WebServiceRefAnnotationHelper.java:[413,108]
> >>> cannot find symbol
> >>> [ERROR] symbol : method responses()
> >>> [ERROR] location: @interface javax.xml.ws.soap.Addressing
> >>> [ERROR] -> [Help 1]
> >>> [ERROR]
> >>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >>> [ERROR]
> >>> [ERROR] For more information about the errors and possible solutions,
> please
> >>> read the following articles:
> >>> [ERROR] [Help 1]
> >>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> >>> [ERROR]
> >>> [ERROR] After correcting the problems, you can resume the build with
> the command
> >>> [ERROR] mvn <goals> -rf :geronimo-j2ee-builder
> >>> -
> >>>
> >>> I do see this, also repeatedly, further up in the output, complaining
> of the
> >>> missing geronimo-j2ee-schema 1.0 bundle:
> >>> -
> >>> [INFO]
> ------------------------------------------------------------------------
> >>> [INFO] Building Geronimo Plugins, System Database 3.0-SNAPSHOT
> >>> [INFO]
> ------------------------------------------------------------------------
> >>> ...
> >>> [INFO]
> ------------------------------------------------------------------------
> >>> [INFO] Building Geronimo Plugins, System Database :: Derby 3.0-SNAPSHOT
> >>> [INFO]
> ------------------------------------------------------------------------
> >>> ...
> >>> [INFO]
> ------------------------------------------------------------------------
> >>> [INFO] Building Geronimo Plugins, J2EE 3.0-SNAPSHOT
> >>> [INFO]
> ------------------------------------------------------------------------
> >>> ...
> >>> [INFO]
> ------------------------------------------------------------------------
> >>> [INFO] Building Geronimo Plugins, J2EE :: Schema 3.0-SNAPSHOT
> >>> [INFO]
> ------------------------------------------------------------------------
> >>> [INFO]
> >>> [INFO] --- maven-clean-plugin:2.3:clean (default-clean) @
> geronimo-j2ee-schema ---
> >>> [INFO] Deleting file set:
> >>>
> /data/geronimo/asf-geronimo-server-trunk/plugins/j2ee/geronimo-j2ee-schema/target
> (included:
> >>> [**], excluded: [])
> >>> [INFO]
> >>> [INFO] --- genesis-maven-plugin:2.0:validate-configuration (default) @
> >>> geronimo-j2ee-schema ---
> >>> [INFO]
> >>> [INFO] --- geronimo-property-plugin:3.0-SNAPSHOT:set-property
> (set-property) @
> >>> geronimo-j2ee-schema ---
> >>> [WARNING] File
> >>>
> /home/ger/.m2/repository/org/apache/geronimo/specs/geronimo-jaxws_2.2_spec/1.0/geronimo-jaxws_2.2_spec-1.0.jar
> >>> does not exist
> >>> -
> >>> A check of that location reveals only a 1.1-SNAPSHOT bundle:
> >>> -
> >>> [ger@linux7 geronimo]# tree
> >>>
> /home/ger/.m2/repository/org/apache/geronimo/specs/geronimo-jaxws_2.2_spec/
> >>>
> /home/ger/.m2/repository/org/apache/geronimo/specs/geronimo-jaxws_2.2_spec/
> >>> `-- 1.1-SNAPSHOT
> >>> |-- _maven.repositories
> >>> |-- geronimo-jaxws_2.2_spec-1.1-20110608.123812-8.jar
> >>> |-- geronimo-jaxws_2.2_spec-1.1-20110608.123812-8.jar.sha1
> >>> |-- geronimo-jaxws_2.2_spec-1.1-20110608.123812-8.pom
> >>> |-- geronimo-jaxws_2.2_spec-1.1-20110608.123812-8.pom.lastUpdated
> >>> |-- geronimo-jaxws_2.2_spec-1.1-20110608.123812-8.pom.sha1
> >>> |-- geronimo-jaxws_2.2_spec-1.1-SNAPSHOT.jar
> >>> |-- geronimo-jaxws_2.2_spec-1.1-SNAPSHOT.pom
> >>> |-- maven-metadata-apache.snapshots.xml
> >>> |-- maven-metadata-apache.snapshots.xml.sha1
> >>> `-- resolver-status.properties
> >>>
> >>> 1 directory, 11 file
> >>> -
>
--
Shawn
