You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@maven.org> on 2008/07/04 04:43:06 UTC
Vetting issues for 2.1-alpha-XX
I have chopped the issue list down to what I know I'm going to look at
here:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&fixfor=13143
If you want to add things you know you want to look at, go for it.
But I would like to use a standard build for testing. I am going to
use the version of Maven built by Hudson from the 2.1 build that's
been cycling off from here:
http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/
If we sync up on a version which we all use then we have a good chance
of getting consistent results. I'm using the build from here to review
the issues currently in the queue:
http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/ws/maven-2.1.x/maven-distribution/target/
When issues are closed, another build can be done and we can use that
one to carry on. I think this is the only sane way to work through the
issues. The Hudson instance has been up the longest, it works more
reasonably then anything else we've used, and John has been working on
creating some release automation so the releases can be built on the
same machine as well. For reliability and consistency I think this is
a reasonable approach.
A PowerEdge 2900 will land at Contegix shortly that has been
provisioned to run ESX so that we can deal with Windows, Linux, BSD,
and Solaris in an automated way. Contegix also said they could wire up
a MAC mini if we wanted to automate OS X builds as well. The box is on
Contegix's system, but any PMC member can get access to the machine
and access to the support list if you need to contact support in the
middle of the night.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Henri Gomez <he...@gmail.com>.
More on this.
With maven 2.0.9 here is the 'classpath' constructed by maven to jaxws :
Maven 2.0.9
[DEBUG] Configuring mojo 'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen' -->
[DEBUG] (f) destDir = C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\target\classes
[DEBUG] (f) extension = false
[DEBUG] (f) genWsdl = true
[DEBUG] (f) keep = false
[DEBUG] (f) pluginArtifactMap =
{org.codehaus.plexus:plexus-utils=org.codehaus.plexus:plexus-utils:jar:1.1:runtime,
com.sun.xml.bind:jaxb-xjc=com.sun.xml.bind:jaxb-xjc:jar:2.1.6:runtime,
javax.xml.bind:jaxb-api=javax.xml.bind:jaxb-api:jar:2.1:runtime,
javax.xml.ws:jaxws-api=javax.xml.ws:jaxws-api:jar:2.1:runtime,
javax.jws:jsr181-api=javax.jws:jsr181-api:jar:1.0-MR1:runtime,
com.sun.xml.bind:jaxb-impl=com.sun.xml.bind:jaxb-impl:jar:2.1.6:runtime,
com.sun.xml.ws:jaxws-tools=com.sun.xml.ws:jaxws-tools:jar:2.1.3:runtime,
org.apache.maven:maven-project=org.apache.maven:maven-project:jar:2.0.4:runtime,
com.sun.xml.stream.buffer:streambuffer=com.sun.xml.stream.buffer:streambuffer:jar:0.7:runtime,
javax.xml.stream:stax-api=javax.xml.stream:stax-api:jar:1.0:runtime,
org.jvnet:mimepull=org.jvnet:mimepull:jar:1.1:runtime,
com.sun.xml.ws:jaxws-rt=com.sun.xml.ws:jaxws-rt:jar:2.1.3:runtime,
org.apache.maven:maven-plugin-api=org.apache.maven:maven-plugin-api:jar:2.0.4:runtime,
com.sun.org.apache.xml.internal:resolver=com.sun.org.apache.xml.internal:resolver:jar:20050927:runtime,
javax.xml.soap:saaj-api=javax.xml.soap:saaj-api:jar:1.3:runtime,
javax.annotation:jsr250-api=javax.annotation:jsr250-api:jar:1.0:runtime,
com.sun.xml.messaging.saaj:saaj-impl=com.sun.xml.messaging.saaj:saaj-impl:jar:1.3:runtime,
javax.activation:activation=javax.activation:activation:jar:1.1:runtime,
com.sun:tools=com.sun:tools:jar:1.5.0:system,
com.sun.xml.stream:sjsxp=com.sun.xml.stream:sjsxp:jar:1.0:runtime,
org.jvnet.staxex:stax-ex=org.jvnet.staxex:stax-ex:jar:1.2:runtime}
[DEBUG] (f) pluginArtifacts =
[com.sun.xml.ws:jaxws-tools:jar:2.1.3:runtime,
com.sun.xml.ws:jaxws-rt:jar:2.1.3:runtime,
javax.xml.ws:jaxws-api:jar:2.1:runtime,
javax.xml.bind:jaxb-api:jar:2.1:runtime,
javax.xml.stream:stax-api:jar:1.0:runtime,
javax.activation:activation:jar:1.1:runtime,
javax.xml.soap:saaj-api:jar:1.3:runtime,
javax.annotation:jsr250-api:jar:1.0:runtime,
javax.jws:jsr181-api:jar:1.0-MR1:runtime,
com.sun.xml.bind:jaxb-impl:jar:2.1.6:runtime,
com.sun.xml.messaging.saaj:saaj-impl:jar:1.3:runtime,
com.sun.xml.stream.buffer:streambuffer:jar:0.7:runtime,
org.jvnet.staxex:stax-ex:jar:1.2:runtime,
com.sun.xml.stream:sjsxp:jar:1.0:runtime,
com.sun.org.apache.xml.internal:resolver:jar:20050927:runtime,
org.jvnet:mimepull:jar:1.1:runtime,
com.sun.xml.bind:jaxb-xjc:jar:2.1.6:runtime,
org.codehaus.plexus:plexus-utils:jar:1.1:runtime,
com.sun:tools:jar:1.5.0:system,
org.apache.maven:maven-project:jar:2.0.4:runtime,
org.apache.maven:maven-plugin-api:jar:2.0.4:runtime]
[DEBUG] (f) project = MavenProject:
mycorp.com:samplewsgen:1.0.0-SNAPSHOT @ C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\pom.xml
[DEBUG] (f) resourceDestDir = C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\target\classes\com\mycorp\resources\wsdl
[DEBUG] (f) sei = samplewsgen.SampleService
[DEBUG] (f) verbose = true
[DEBUG] -- end configuration --
[INFO] [jaxws:wsgen {execution: go-wsgen}]
[DEBUG] C:\Documents and Settings\gomezhe\Bureau\sample-wsgen\target\classes
[DEBUG] c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.4\jaxws-rt-2.1.4.jar
[DEBUG] c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar
[DEBUG] c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar
[DEBUG] c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar
[DEBUG] c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar
[DEBUG] c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar
[DEBUG] c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar
[DEBUG] c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar
[DEBUG] c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.7\jaxb-impl-2.1.7.jar
[DEBUG] c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3.1\saaj-impl-1.3.1.jar
[DEBUG] c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar
[DEBUG] c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar
[DEBUG] c:\maven-repository\junit\junit\3.8\junit-3.8.jar
[DEBUG] c:\maven-repository\com\sun\xml\stream\sjsxp\1.0.1\sjsxp-1.0.1.jar
[DEBUG] c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar
[DEBUG] c:\maven-repository\org\jvnet\mimepull\1.2\mimepull-1.2.jar
[DEBUG] jaxws:wsgen args: [-verbose, -d, C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\target\classes, -cp, C:\Documents
and Settings\gomezhe\Bureau\sample-wsgen\target\classes;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.4\jaxws-rt-2.1.4.jar;c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar;c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar;c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar;c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar;c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.7\jaxb-impl-2.1.7.jar;c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3.1\saaj-impl-1.3.1.jar;c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar;c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar;c:\maven-repository\junit\junit\3.8\junit-3.8.jar;c:\maven-repository\com\sun\xml\stream\sjsxp\1.0.1\sjsxp-1.0.1.jar;c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar;c:\maven-repository\org\jvnet\mimepull\1.2\mimepull-1.2.jar;c:\maven-repository\com\sun\xml\ws\jaxws-tools\2.1.3\jaxws-tools-2.1.3.jar;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.3\jaxws-rt-2.1.3.jar;c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar;c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar;c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar;c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar;c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.6\jaxb-impl-2.1.6.jar;c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3\saaj-impl-1.3.jar;c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar;c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar;c:\maven-repository\com\sun\xml\stream\sjsxp\1.0\sjsxp-1.0.jar;c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar;c:\maven-repository\org\jvnet\mimepull\1.1\mimepull-1.1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-xjc\2.1.6\jaxb-xjc-2.1.6.jar;c:\maven-repository\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;C:\ibm-j2sdk1.5.0\jre\..\lib\tools.jar;C:\maven\lib\maven-2.0.9-uber.jar;C:\maven\lib\maven-2.0.9-uber.jar,
-wsdl, -r, C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\target\classes\com\mycorp\resources\wsdl,
samplewsgen.SampleService]
Here is what we had with maven 2.1 (the one provided with m2eclipse 0.9.4)
Maven 2.1
[DEBUG] Looking up mojo
org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen in realm
/plugins/org.codehaus.mojo:jaxws-maven-plugin:1.10@48/thread:main -
descRealmId=/plugins/org.codehaus.mojo:jaxws-maven-plugin:1.10@48/thread:main
[DEBUG] Looked up - org.codehaus.mojo.jaxws.MainWsGenMojo@1d9e2c7 -
ClassRealm[/plugins/org.codehaus.mojo:jaxws-maven-plugin:1.10@48/thread:main,
parent: ClassRealm[plexus.core, parent: null]]
[DEBUG] Configuring mojo
'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen' with basic
configurator -->
[DEBUG] (f) destDir = C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\target\classes
[DEBUG] (f) extension = false
[DEBUG] (f) genWsdl = true
[DEBUG] (f) keep = false
[DEBUG] (f) pluginArtifactMap =
{com.sun.xml.messaging.saaj:saaj-impl=com.sun.xml.messaging.saaj:saaj-impl:jar:1.3:runtime,
org.apache.maven:maven-profile=org.apache.maven:maven-profile:jar:2.0.4:runtime,
javax.xml.ws:jaxws-api=javax.xml.ws:jaxws-api:jar:2.1:runtime,
org.codehaus.plexus:plexus-container-default=org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:runtime,
javax.annotation:jsr250-api=javax.annotation:jsr250-api:jar:1.0:runtime,
org.apache.maven:maven-artifact-manager=org.apache.maven:maven-artifact-manager:jar:2.0.4:runtime,
classworlds:classworlds=classworlds:classworlds:jar:1.1-alpha-2:runtime,
com.sun.xml.ws:jaxws-tools=com.sun.xml.ws:jaxws-tools:jar:2.1.3:runtime,
javax.activation:activation=javax.activation:activation:jar:1.1:runtime,
org.apache.maven:maven-project=org.apache.maven:maven-project:jar:2.0.4:runtime,
com.sun.xml.bind:jaxb-impl=com.sun.xml.bind:jaxb-impl:jar:2.1.6:runtime,
junit:junit=junit:junit:jar:3.8.1:runtime,
javax.xml.bind:jaxb-api=javax.xml.bind:jaxb-api:jar:2.1:runtime,
com.sun.xml.bind:jaxb-xjc=com.sun.xml.bind:jaxb-xjc:jar:2.1.6:runtime,
org.apache.maven:maven-artifact=org.apache.maven:maven-artifact:jar:2.0.4:runtime,
javax.xml.stream:stax-api=javax.xml.stream:stax-api:jar:1.0:runtime,
org.apache.maven:maven-model=org.apache.maven:maven-model:jar:2.0.4:runtime,
com.sun.xml.stream:sjsxp=com.sun.xml.stream:sjsxp:jar:1.0:runtime,
com.sun.xml.ws:jaxws-rt=com.sun.xml.ws:jaxws-rt:jar:2.1.3:runtime,
javax.xml.soap:saaj-api=javax.xml.soap:saaj-api:jar:1.3:runtime,
org.apache.maven:maven-repository-metadata=org.apache.maven:maven-repository-metadata:jar:2.0.4:runtime,
org.apache.maven.wagon:wagon-provider-api=org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6:runtime,
com.sun.xml.stream.buffer:streambuffer=com.sun.xml.stream.buffer:streambuffer:jar:0.7:runtime,
org.jvnet:mimepull=org.jvnet:mimepull:jar:1.1:runtime,
org.codehaus.plexus:plexus-utils=org.codehaus.plexus:plexus-utils:jar:1.1:runtime,
org.jvnet.staxex:stax-ex=org.jvnet.staxex:stax-ex:jar:1.2:runtime,
org.apache.maven:maven-plugin-api=org.apache.maven:maven-plugin-api:jar:2.0.4:runtime,
javax.jws:jsr181-api=javax.jws:jsr181-api:jar:1.0-MR1:runtime,
com.sun.org.apache.xml.internal:resolver=com.sun.org.apache.xml.internal:resolver:jar:20050927:runtime,
org.apache.maven:maven-settings=org.apache.maven:maven-settings:jar:2.0.4:runtime}
[DEBUG] (f) pluginArtifacts =
[com.sun.xml.ws:jaxws-tools:jar:2.1.3:runtime,
com.sun.xml.ws:jaxws-rt:jar:2.1.3:runtime,
javax.xml.ws:jaxws-api:jar:2.1:runtime,
javax.xml.bind:jaxb-api:jar:2.1:runtime,
javax.xml.stream:stax-api:jar:1.0:runtime,
javax.activation:activation:jar:1.1:runtime,
javax.xml.soap:saaj-api:jar:1.3:runtime,
javax.annotation:jsr250-api:jar:1.0:runtime,
javax.jws:jsr181-api:jar:1.0-MR1:runtime,
com.sun.xml.bind:jaxb-impl:jar:2.1.6:runtime,
com.sun.xml.messaging.saaj:saaj-impl:jar:1.3:runtime,
com.sun.xml.stream.buffer:streambuffer:jar:0.7:runtime,
org.jvnet.staxex:stax-ex:jar:1.2:runtime,
junit:junit:jar:3.8.1:runtime,
com.sun.xml.stream:sjsxp:jar:1.0:runtime,
com.sun.org.apache.xml.internal:resolver:jar:20050927:runtime,
org.jvnet:mimepull:jar:1.1:runtime,
com.sun.xml.bind:jaxb-xjc:jar:2.1.6:runtime,
org.apache.maven:maven-project:jar:2.0.4:runtime,
org.apache.maven:maven-settings:jar:2.0.4:runtime,
org.apache.maven:maven-model:jar:2.0.4:runtime,
org.codehaus.plexus:plexus-utils:jar:1.1:runtime,
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:runtime,
classworlds:classworlds:jar:1.1-alpha-2:runtime,
org.apache.maven:maven-profile:jar:2.0.4:runtime,
org.apache.maven:maven-artifact-manager:jar:2.0.4:runtime,
org.apache.maven:maven-repository-metadata:jar:2.0.4:runtime,
org.apache.maven:maven-artifact:jar:2.0.4:runtime,
org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6:runtime,
org.apache.maven:maven-plugin-api:jar:2.0.4:runtime]
[DEBUG] (f) project = MavenProject:
mycorp.com:samplewsgen:1.0.0-SNAPSHOT @ C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\pom.xml
[DEBUG] (f) resourceDestDir = C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\target\classes\com\mycorp\resources\wsdl
[DEBUG] (f) sei = samplewsgen.SampleService
[DEBUG] (f) verbose = true
[DEBUG] -- end configuration --
[INFO] [jaxws:wsgen]
[DEBUG] Setting context classloader for plugin to:
/plugins/org.codehaus.mojo:jaxws-maven-plugin:1.10@48/thread:main
(instance is: ClassRealm[/plugins/org.codehaus.mojo:jaxws-maven-plugin:1.10@48/thread:main,
parent: ClassRealm[plexus.core, parent: null]])
[DEBUG] C:\Documents and Settings\gomezhe\Bureau\sample-wsgen\target\classes
[DEBUG] c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.4\jaxws-rt-2.1.4.jar
[DEBUG] c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar
[DEBUG] c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar
[DEBUG] c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar
[DEBUG] c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar
[DEBUG] c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar
[DEBUG] c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar
[DEBUG] c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar
[DEBUG] c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.7\jaxb-impl-2.1.7.jar
[DEBUG] c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3.1\saaj-impl-1.3.1.jar
[DEBUG] c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar
[DEBUG] c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar
[DEBUG] c:\maven-repository\junit\junit\3.8\junit-3.8.jar
[DEBUG] c:\maven-repository\com\sun\xml\stream\sjsxp\1.0.1\sjsxp-1.0.1.jar
[DEBUG] c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar
[DEBUG] c:\maven-repository\org\jvnet\mimepull\1.2\mimepull-1.2.jar
[DEBUG] jaxws:wsgen args: [-verbose, -d, C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\target\classes, -cp, C:\Documents
and Settings\gomezhe\Bureau\sample-wsgen\target\classes;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.4\jaxws-rt-2.1.4.jar;c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar;c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar;c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar;c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar;c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.7\jaxb-impl-2.1.7.jar;c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3.1\saaj-impl-1.3.1.jar;c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar;c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar;c:\maven-repository\junit\junit\3.8\junit-3.8.jar;c:\maven-repository\com\sun\xml\stream\sjsxp\1.0.1\sjsxp-1.0.1.jar;c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar;c:\maven-repository\org\jvnet\mimepull\1.2\mimepull-1.2.jar;c:\maven-repository\com\sun\xml\ws\jaxws-tools\2.1.3\jaxws-tools-2.1.3.jar;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.3\jaxws-rt-2.1.3.jar;c:\maven-repository\javax\xml\ws\jaxws-api\2.1\jaxws-api-2.1.jar;c:\maven-repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;c:\maven-repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar;c:\maven-repository\javax\activation\activation\1.1\activation-1.1.jar;c:\maven-repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;c:\maven-repository\javax\annotation\jsr250-api\1.0\jsr250-api-1.0.jar;c:\maven-repository\javax\jws\jsr181-api\1.0-MR1\jsr181-api-1.0-MR1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-impl\2.1.6\jaxb-impl-2.1.6.jar;c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3\saaj-impl-1.3.jar;c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.7\streambuffer-0.7.jar;c:\maven-repository\org\jvnet\staxex\stax-ex\1.2\stax-ex-1.2.jar;c:\maven-repository\junit\junit\3.8.1\junit-3.8.1.jar;c:\maven-repository\com\sun\xml\stream\sjsxp\1.0\sjsxp-1.0.jar;c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar;c:\maven-repository\org\jvnet\mimepull\1.1\mimepull-1.1.jar;c:\maven-repository\com\sun\xml\bind\jaxb-xjc\2.1.6\jaxb-xjc-2.1.6.jar;c:\maven-repository\org\apache\maven\maven-project\2.0.4\maven-project-2.0.4.jar;c:\maven-repository\org\apache\maven\maven-settings\2.0.4\maven-settings-2.0.4.jar;c:\maven-repository\org\apache\maven\maven-model\2.0.4\maven-model-2.0.4.jar;c:\maven-repository\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;c:\maven-repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-9\plexus-container-default-1.0-alpha-9.jar;c:\maven-repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;c:\maven-repository\org\apache\maven\maven-profile\2.0.4\maven-profile-2.0.4.jar;c:\maven-repository\org\apache\maven\maven-artifact-manager\2.0.4\maven-artifact-manager-2.0.4.jar;c:\maven-repository\org\apache\maven\maven-repository-metadata\2.0.4\maven-repository-metadata-2.0.4.jar;c:\maven-repository\org\apache\maven\maven-artifact\2.0.4\maven-artifact-2.0.4.jar;c:\maven-repository\org\apache\maven\wagon\wagon-provider-api\1.0-alpha-6\wagon-provider-api-1.0-alpha-6.jar;c:\maven-repository\org\apache\maven\maven-plugin-api\2.0.4\maven-plugin-api-2.0.4.jar,
-wsdl, -r, C:\Documents and
Settings\gomezhe\Bureau\sample-wsgen\target\classes\com\mycorp\resources\wsdl,
samplewsgen.SampleService]
[DEBUG] disposing managed ClassRealm with id:
/plugins/org.codehaus.mojo:jaxws-maven-plugin:1.10@48/thread:main
As you could see no tools.jar
With a patched pom for jaxws same problem :
original pom :
<profiles>
<profile>
<!-- This is only for non MAC OS X builds, hence the property below -->
<id>default-tools.jar</id>
<activation>
<property>
<name>java.vendor</name>
<value>Sun Microsystems Inc.</value>
</property>
</activation>
<dependencies>
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.5.0</version>
<scope>system</scope>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>
</dependencies>
</profile>
</profiles>
...
patched pom (to have tools.jar added not just for Sun SDK) :
<profiles>
<profile>
<!-- This is only for non MAC OS X builds, hence the property below -->
<id>default-tools.jar</id>
<activation>
<file>
<exists>${java.home}/../lib/tools.jar</exists>
</file>
</activation>
<dependencies>
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.5.0</version>
<scope>system</scope>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>
</dependencies>
</profile>
</profiles>
May be not a show stopper but it seems the system scope is not handled
correctly ;(
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Henri Gomez <he...@gmail.com>.
2008/7/4 Brett Porter <br...@apache.org>:
> I was just looking at this Henri - though I'm not longer able to compile the
> provided test project so it's impossible to test.
>
> Can you review the project to help make it reproducible?
Done.
Redone the test with m2eclipse 0.9.4 (using embedded)
>From file: C:\Documents and Settings\gomezhe\Bureau\sample-wsgen\pom.xml
Reason: Failed to execute wsgen
java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174)
at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at com.sun.tools.ws.WsGen.doMain(WsGen.java:69)
at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97)
at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
Error stacktrace:
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
in the plugin manager executing goal
'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen': Mojo execution
failed.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo
execution failed.
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
... 12 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
execute wsgen
at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:102)
at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
... 13 more
Caused by: java.lang.NoClassDefFoundError:
com/sun/mirror/apt/AnnotationProcessorFactory
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174)
at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at com.sun.tools.ws.WsGen.doMain(WsGen.java:69)
at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97)
... 15 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILED
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13 seconds
[INFO] Finished at: Fri Jul 04 11:03:27 CEST 2008
[INFO] Final Memory: 3M/11M
[INFO] ------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Brett Porter <br...@apache.org>.
I was just looking at this Henri - though I'm not longer able to
compile the provided test project so it's impossible to test.
Can you review the project to help make it reproducible?
Thanks,
Brett
On 04/07/2008, at 5:12 PM, Henri Gomez wrote:
> Did the MNG-3586 is allready fixed or fix is delayed ?
>
> I got this mail :
>
> ---------
>
> Jason van Zyl updated MNG-3586:
> -------------------------------
>
> Fix Version/s: (was: 2.1-alpha-1)
> 2.1-alpha-2
>
> ----------
>
>
> Very annoying bug for those of us using m2eclipse 0.9.4 and have jaxws
> operation in their pom (since maven embedded failed during IDE
> operations).
>
> Regards
>
>
> 2008/7/4 Brett Porter <br...@apache.org>:
>>
>> On 04/07/2008, at 12:43 PM, Jason van Zyl wrote:
>>
>>> I have chopped the issue list down to what I know I'm going to
>>> look at
>>> here:
>>>
>>>
>>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&fixfor=13143
>>>
>>> If you want to add things you know you want to look at, go for it.
>>
>> I generally agree with the ones pushed back, they were what I was
>> eyeing at
>> pushing out once done with the others.
>>
>> There are 3 I think need to be fixed first:
>> MNG-3366 (site generation is completely hosed)
>> MNG-3281 (extensions don't work and there's no alternative)
>> MNG-3576 (regression when using the assembly plugin)
>>
>> I'll move them back in.
>>
>> - Brett
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://blogs.exist.com/bporter/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Henri Gomez <he...@gmail.com>.
Did the MNG-3586 is allready fixed or fix is delayed ?
I got this mail :
---------
Jason van Zyl updated MNG-3586:
-------------------------------
Fix Version/s: (was: 2.1-alpha-1)
2.1-alpha-2
----------
Very annoying bug for those of us using m2eclipse 0.9.4 and have jaxws
operation in their pom (since maven embedded failed during IDE
operations).
Regards
2008/7/4 Brett Porter <br...@apache.org>:
>
> On 04/07/2008, at 12:43 PM, Jason van Zyl wrote:
>
>> I have chopped the issue list down to what I know I'm going to look at
>> here:
>>
>>
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&fixfor=13143
>>
>> If you want to add things you know you want to look at, go for it.
>
> I generally agree with the ones pushed back, they were what I was eyeing at
> pushing out once done with the others.
>
> There are 3 I think need to be fixed first:
> MNG-3366 (site generation is completely hosed)
> MNG-3281 (extensions don't work and there's no alternative)
> MNG-3576 (regression when using the assembly plugin)
>
> I'll move them back in.
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Brett Porter <br...@apache.org>.
On 04/07/2008, at 12:43 PM, Jason van Zyl wrote:
> I have chopped the issue list down to what I know I'm going to look
> at here:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&fixfor=13143
>
> If you want to add things you know you want to look at, go for it.
I generally agree with the ones pushed back, they were what I was
eyeing at pushing out once done with the others.
There are 3 I think need to be fixed first:
MNG-3366 (site generation is completely hosed)
MNG-3281 (extensions don't work and there's no alternative)
MNG-3576 (regression when using the assembly plugin)
I'll move them back in.
- Brett
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Jason van Zyl <ja...@maven.org>.
We'll get a Solaris VM running at Contegix but I'll try it when Nigel
gives me access. The Hadoop stuff seems to be running all the time and
it takes over an hour so our ITs would probably kill the machine.
On 6-Jul-08, at 9:33 AM, Brett Porter wrote:
>
> On 05/07/2008, at 2:17 AM, Jason van Zyl wrote:
>
>> As part of getting adequate coverage for vetting, I have just asked
>> Nigel and Justin who watch over the Hudson instance here at Apache
>> to setup the Maven jobs we require for validation. They are running
>> on Solaris which will be a good compliment to what we have running
>> at Contegix.
>
> I think Brian tried this initially and had a number of obscure
> problems. Hopefully they've since sorted them out, but worth keeping
> in mind if anything pops up.
>
> Cheers,
> Brett
>
>>
>>
>> Hopefully this will be setup today and then we'll have Linux and
>> Solaris dealth with in a reliable, automated way. I've asked
>> Contegix to order a Mac Mini they will modify and put in our rack,
>> and we will have a big machine that will run ESX coming soon as
>> well so we'll be able to deal with different flavors of Windows and
>> *nix.
>>
>> On 3-Jul-08, at 10:43 PM, Jason van Zyl wrote:
>>
>>> I have chopped the issue list down to what I know I'm going to
>>> look at here:
>>>
>>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&fixfor=13143
>>>
>>> If you want to add things you know you want to look at, go for it.
>>>
>>> But I would like to use a standard build for testing. I am going
>>> to use the version of Maven built by Hudson from the 2.1 build
>>> that's been cycling off from here:
>>>
>>> http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/
>>>
>>> If we sync up on a version which we all use then we have a good
>>> chance of getting consistent results. I'm using the build from
>>> here to review the issues currently in the queue:
>>>
>>> http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/ws/maven-2.1.x/maven-distribution/target/
>>>
>>> When issues are closed, another build can be done and we can use
>>> that one to carry on. I think this is the only sane way to work
>>> through the issues. The Hudson instance has been up the longest,
>>> it works more reasonably then anything else we've used, and John
>>> has been working on creating some release automation so the
>>> releases can be built on the same machine as well. For reliability
>>> and consistency I think this is a reasonable approach.
>>>
>>> A PowerEdge 2900 will land at Contegix shortly that has been
>>> provisioned to run ESX so that we can deal with Windows, Linux,
>>> BSD, and Solaris in an automated way. Contegix also said they
>>> could wire up a MAC mini if we wanted to automate OS X builds as
>>> well. The box is on Contegix's system, but any PMC member can get
>>> access to the machine and access to the support list if you need
>>> to contact support in the middle of the night.
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> jason at sonatype dot com
>>> ----------------------------------------------------------
>>>
>>> happiness is like a butterfly: the more you chase it, the more it
>>> will
>>> elude you, but if you turn your attention to other things, it will
>>> come
>>> and sit softly on your shoulder ...
>>>
>>> -- Thoreau
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>> Three people can keep a secret provided two of them are dead.
>>
>> -- Unknown
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Brett Porter <br...@apache.org>.
On 05/07/2008, at 2:17 AM, Jason van Zyl wrote:
> As part of getting adequate coverage for vetting, I have just asked
> Nigel and Justin who watch over the Hudson instance here at Apache
> to setup the Maven jobs we require for validation. They are running
> on Solaris which will be a good compliment to what we have running
> at Contegix.
I think Brian tried this initially and had a number of obscure
problems. Hopefully they've since sorted them out, but worth keeping
in mind if anything pops up.
Cheers,
Brett
>
>
> Hopefully this will be setup today and then we'll have Linux and
> Solaris dealth with in a reliable, automated way. I've asked
> Contegix to order a Mac Mini they will modify and put in our rack,
> and we will have a big machine that will run ESX coming soon as well
> so we'll be able to deal with different flavors of Windows and *nix.
>
> On 3-Jul-08, at 10:43 PM, Jason van Zyl wrote:
>
>> I have chopped the issue list down to what I know I'm going to look
>> at here:
>>
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&fixfor=13143
>>
>> If you want to add things you know you want to look at, go for it.
>>
>> But I would like to use a standard build for testing. I am going to
>> use the version of Maven built by Hudson from the 2.1 build that's
>> been cycling off from here:
>>
>> http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/
>>
>> If we sync up on a version which we all use then we have a good
>> chance of getting consistent results. I'm using the build from here
>> to review the issues currently in the queue:
>>
>> http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/ws/maven-2.1.x/maven-distribution/target/
>>
>> When issues are closed, another build can be done and we can use
>> that one to carry on. I think this is the only sane way to work
>> through the issues. The Hudson instance has been up the longest, it
>> works more reasonably then anything else we've used, and John has
>> been working on creating some release automation so the releases
>> can be built on the same machine as well. For reliability and
>> consistency I think this is a reasonable approach.
>>
>> A PowerEdge 2900 will land at Contegix shortly that has been
>> provisioned to run ESX so that we can deal with Windows, Linux,
>> BSD, and Solaris in an automated way. Contegix also said they could
>> wire up a MAC mini if we wanted to automate OS X builds as well.
>> The box is on Contegix's system, but any PMC member can get access
>> to the machine and access to the support list if you need to
>> contact support in the middle of the night.
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>> happiness is like a butterfly: the more you chase it, the more it
>> will
>> elude you, but if you turn your attention to other things, it will
>> come
>> and sit softly on your shoulder ...
>>
>> -- Thoreau
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
> Three people can keep a secret provided two of them are dead.
>
> -- Unknown
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Jason van Zyl <ja...@maven.org>.
As part of getting adequate coverage for vetting, I have just asked
Nigel and Justin who watch over the Hudson instance here at Apache to
setup the Maven jobs we require for validation. They are running on
Solaris which will be a good compliment to what we have running at
Contegix.
Hopefully this will be setup today and then we'll have Linux and
Solaris dealth with in a reliable, automated way. I've asked Contegix
to order a Mac Mini they will modify and put in our rack, and we will
have a big machine that will run ESX coming soon as well so we'll be
able to deal with different flavors of Windows and *nix.
On 3-Jul-08, at 10:43 PM, Jason van Zyl wrote:
> I have chopped the issue list down to what I know I'm going to look
> at here:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&fixfor=13143
>
> If you want to add things you know you want to look at, go for it.
>
> But I would like to use a standard build for testing. I am going to
> use the version of Maven built by Hudson from the 2.1 build that's
> been cycling off from here:
>
> http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/
>
> If we sync up on a version which we all use then we have a good
> chance of getting consistent results. I'm using the build from here
> to review the issues currently in the queue:
>
> http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/ws/maven-2.1.x/maven-distribution/target/
>
> When issues are closed, another build can be done and we can use
> that one to carry on. I think this is the only sane way to work
> through the issues. The Hudson instance has been up the longest, it
> works more reasonably then anything else we've used, and John has
> been working on creating some release automation so the releases can
> be built on the same machine as well. For reliability and
> consistency I think this is a reasonable approach.
>
> A PowerEdge 2900 will land at Contegix shortly that has been
> provisioned to run ESX so that we can deal with Windows, Linux, BSD,
> and Solaris in an automated way. Contegix also said they could wire
> up a MAC mini if we wanted to automate OS X builds as well. The box
> is on Contegix's system, but any PMC member can get access to the
> machine and access to the support list if you need to contact
> support in the middle of the night.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will
> come
> and sit softly on your shoulder ...
>
> -- Thoreau
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
Three people can keep a secret provided two of them are dead.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Jason van Zyl <ja...@maven.org>.
On 4-Jul-08, at 3:14 AM, Henri Gomez wrote:
>> Here's some tips for folks trying to debug Maven/Plexus/Plugins in
>> Eclipse.
>
>> Using m2e you can actually debug/execute plugin _inside_ Eclipse.
>> That means
>> the plugin executes from the workspace in-situ. Extremely handy.
>>
>> http://docs.codehaus.org/display/M2ECLIPSE/Developing+and+debugging+Maven+plugins
>
> Did you also experiment m2eclipse to developp and debug maven 2.1 (in
> embedded and standalone mode ?)
We do, you can give the method that Igor outlines here:
http://docs.codehaus.org/display/MAVEN/Running+and+debugging+Maven+2.1+from+m2e+workspace
We would be interested in feedback and we will enable some UI around
it shortly. Until then we're happy to help anyone who want to try and
load the whole platform to develop.
>
>
> Regards
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.
-- Eric Hoffer, Reflections on the Human Condition
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Henri Gomez <he...@gmail.com>.
> Here's some tips for folks trying to debug Maven/Plexus/Plugins in Eclipse.
> Using m2e you can actually debug/execute plugin _inside_ Eclipse. That means
> the plugin executes from the workspace in-situ. Extremely handy.
>
> http://docs.codehaus.org/display/M2ECLIPSE/Developing+and+debugging+Maven+plugins
Did you also experiment m2eclipse to developp and debug maven 2.1 (in
embedded and standalone mode ?)
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Vetting issues for 2.1-alpha-XX
Posted by Jason van Zyl <ja...@maven.org>.
Here's some tips for folks trying to debug Maven/Plexus/Plugins in
Eclipse. Using m2e you can actually debug/execute plugin _inside_
Eclipse. That means the plugin executes from the workspace in-situ.
Extremely handy.
http://docs.codehaus.org/display/M2ECLIPSE/Developing+and+debugging+Maven+plugins
On 3-Jul-08, at 10:43 PM, Jason van Zyl wrote:
> I have chopped the issue list down to what I know I'm going to look
> at here:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&fixfor=13143
>
> If you want to add things you know you want to look at, go for it.
>
> But I would like to use a standard build for testing. I am going to
> use the version of Maven built by Hudson from the 2.1 build that's
> been cycling off from here:
>
> http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/
>
> If we sync up on a version which we all use then we have a good
> chance of getting consistent results. I'm using the build from here
> to review the issues currently in the queue:
>
> http://ci.sonatype.org/view/Maven%202.1x/job/Maven-2.1.x/ws/maven-2.1.x/maven-distribution/target/
>
> When issues are closed, another build can be done and we can use
> that one to carry on. I think this is the only sane way to work
> through the issues. The Hudson instance has been up the longest, it
> works more reasonably then anything else we've used, and John has
> been working on creating some release automation so the releases can
> be built on the same machine as well. For reliability and
> consistency I think this is a reasonable approach.
>
> A PowerEdge 2900 will land at Contegix shortly that has been
> provisioned to run ESX so that we can deal with Windows, Linux, BSD,
> and Solaris in an automated way. Contegix also said they could wire
> up a MAC mini if we wanted to automate OS X builds as well. The box
> is on Contegix's system, but any PMC member can get access to the
> machine and access to the support list if you need to contact
> support in the middle of the night.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will
> come
> and sit softly on your shoulder ...
>
> -- Thoreau
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org