Re: [VOTE] Release Apache Maven 3.0-beta-2
+0 Good news and thanks for releasing it ! 2010/8/8 Tony Chemit che...@codelutin.com: +1 (none binding) works fine on all our central safe projects. Great job :) Tony Le Sat, 07 Aug 2010 13:16:42 +0200, Benjamin Bentmann benjamin.bentm...@udo.edu a écrit : Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/maven/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x
Point of vue of a Maven user : We need to have a new beta release, ie beta-2 since the beta-1 is now 3/4 months old and Maven 2.2.1 is one year old. This will help us show our co-workers and may be more important, our IT managers, that Maven 3.0 progress. They didn't follow maven-dev list and only knowns about Maven release (including beta). And as a bonus, it will allow more time and testing for the beta-3 with Aether and Guice. Regards - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Merging in our Aether and Guice changes to Maven 3.x
2010/8/4 Stephen Connolly stephen.alan.conno...@gmail.com: I share concerns with respect to where the code is hosted. I recognise that as Apache is a meritocracy, there is a barrier for other developers getting involved. The Hudson model of You want commit access, here you go is a tad too liberal for me, but the Apache model is too far the other way IMHO. To some extend the codehaus model as practiced on mojo seems a good compromise to me... but anyway aside from all that... Maven is hosted on Apache, therefore I feel that core Maven libraries should be hosted on Apache until they have significant adoption elsewhere... the Maven Repository API... well that kind of says it all as far as I'm concerned with respect to where it should live. The Guice changes, well guice is widely adopted elsewhere, so I'm not suggesting that Guice be relocated or forked into apache, but the Maven specific parts of that integration hang about... maven specific says it all again. I have always had concerns about plexus being pretty much only adopted by Maven as far as I can see, and essentially being a maven core component, except it isn't +1 Guice allready as its own large community of users and maintainers. It's a general 'purpose' API. Aether is new, Maven related and need to create its own community. Why not moving it to ASF as a Maven subproject ? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Merging in our Aether and Guice changes to Maven 3.x
2010/8/4 Stephen Connolly stephen.alan.conno...@gmail.com: If Aether has commit access for all Maven committers automatically, (and I'm not saying it doesn't) then a large part of my concerns can be removed... I recognise the p2 stuff as being a separate concern from the m2 repo stuff and if that's the case then you need to sell Aether as such and not try to sell it as a Maven Repo API. Aether and p2 make me think this project should be best suited for the Eclipse Foundation, as subproject. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Merging in our Aether and Guice changes to Maven 3.x
2010/8/4 Stephen Connolly stephen.alan.conno...@gmail.com: Alternatively, host the Aether API in one place (hey why not codehaus), the Maven Repo impl in Apache and the p2 repo impl in Eclipse ;-) Very good idea - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-gwt-plugin 1.2 documentation
Oups, right,it should be on mojo-dev. Sorry 2010/1/11 Wayne Fay wayne...@gmail.com: It's not the wrong list, I reported some miss in the gwt plugin to Nicolas. Hopefully, he'll fix them quickly. I think Jason's point is that this discussion belongs on the mojo-dev or mojo-users list, not Maven dev, since this is a Mojo plugin... Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven-gwt-plugin 1.2 documentation
Hi to all, I'll do some GWT 2.0.x application and get a look at http://mojo.codehaus.org/gwt-maven-plugin/ The documentation is still mainly for plugin 1.1 (gwt 1.7.x) with some notice for gwt 2.0 support. Did there is an up to date documentation available somewhere for best practices with gwt-maven-plugin 1.2 released in late December. Regards - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-gwt-plugin 1.2 documentation
Thanks Nicolas :) I was not sure since I read the sentence : version 1.2 includes a preview of gwt 2.0 support Also : mvn archetype:generate \ -DarchetypeGroupId=org.codehaus.mojo \ -DarchetypeArtifactId=gwt-maven-plugin \ -DarchetypeVersion=1.1 \ -DgroupId=myGroupId \ -DartifactId=myArtifactId but archetype version 1.2 is available. In the doc reference to the gwt-maven-plugin are still to 1.1. 2010/1/11 nicolas de loof nicolas.del...@gmail.com: This doc is up-to-date. the 1.2 version is not dedicated to gwt 2.0, it just support this version as GWT = 1.4 2010/1/11 Henri Gomez henri.go...@gmail.com Hi to all, I'll do some GWT 2.0.x application and get a look at http://mojo.codehaus.org/gwt-maven-plugin/ The documentation is still mainly for plugin 1.1 (gwt 1.7.x) with some notice for gwt 2.0 support. Did there is an up to date documentation available somewhere for best practices with gwt-maven-plugin 1.2 released in late December. Regards - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-gwt-plugin 1.2 documentation
Sorry Jason, It's not the wrong list, I reported some miss in the gwt plugin to Nicolas. Hopefully, he'll fix them quickly. 2010/1/11 Jason van Zyl ja...@sonatype.com: Wrong list. On 2010-01-11, at 5:31 AM, Henri Gomez wrote: Hi to all, I'll do some GWT 2.0.x application and get a look at http://mojo.codehaus.org/gwt-maven-plugin/ The documentation is still mainly for plugin 1.1 (gwt 1.7.x) with some notice for gwt 2.0 support. Did there is an up to date documentation available somewhere for best practices with gwt-maven-plugin 1.2 released in late December. Regards - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-alpha-6
No problem here. Many projects build with m2eclipse (from trunk), with the maven3-alpha-6 BTW, I'd like to generalize to our Hudson instance, but it seems Hudson still didn't support maven 3.0 :( 2010/1/7 Olivier Lamy ol...@apache.org: Hi, +1. Tested on company builds with success. Thanks, -- Olivier 2010/1/6 Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, We solved 29 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15996 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-014/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-014/org/apache/maven/apache-maven/3.0-alpha-6/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-alpha-6
BTW, I'd like to generalize to our Hudson instance, but it seems Hudson still didn't support maven 3.0 :( Just use free-style projects and you're free to use any Maven version you like. i'd like to but about 250 projects to update ;( - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-alpha-3
+0 (non binding) I'm using m2eclipse from the trunk, using the embedded maven 3 from the trunk, to build several in-house projects. No problems for now 2009/11/9 Arnaud HERITIER aherit...@gmail.com: +1 Tested with success on several projects It becomes to be interesting :-) Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Nov 9, 2009 at 5:44 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 from me 2009/11/9 Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, OK, here we go, another alpha release of Maven, for all those brave guys that want to take it for a test drive ;-) We solved many issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14719 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamim - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: missing artifact for maven-3 dev
I see yesterday night (CET), build works now 2009/11/6 Brian Fox bri...@infinity.nu: On Fri, Nov 6, 2009 at 8:34 AM, Henri Gomez henri.go...@gmail.com wrote: Ok. For now, I'm building it thru our corp Nexus, and so I should define them. Do you recommand to use instead a pure proxy settings instead (I do such for m2eclipse builds). Just add that repo to nexus, or alternatively change your mirror to *,![repoid] - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven 3.0 build failure with IBM SDK 5
The problem dissapear after upgrading to IBM SDK SR10. 2009/11/6 Patrick Schneider pschnei...@gmail.com: Did you get this figured out? I've seen the MalformedInputException before on Windows machines when the default character endcoding is being used. Are you configuring the resource plugin at all, or relying on defaults? You might try specifying UTF-8 explicitly in there. On Tue, Nov 3, 2009 at 8:46 AM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Henri Gomez wrote: What's the JIRA for this problem (and fix in r832389) ? I'd like to verify if this bug could affect some of ours projects There is no JIRA because it's not a bug in Maven itself. As visible from the mentioned SVN revision, the failure to build Maven was due to a corrupt resource file among its sources. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven 3.0 build failure with IBM SDK 5
Hi to all,
I just added a job on our Hudson server to build Maven 3.0 from the trunk.
The job use maven 2.2.1 and a custom repository (to avoid collisions
with our others projects).
Goals are clean install and MAVEN_OPTS is set to -Xmx512m
No problem when I use a Sun JVM Java 5.
But if I select an IBM SDK 5 (SR9) as build JVM, the build fail :
[INFO]
[INFO] Building Maven Core
[INFO]task-segment: [clean, install]
[INFO]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set:
/home/hudson/jobs/maven-3/workspace/maven-3/maven-core/target
(included: [**], excluded: [])
[INFO] [modello:java {execution: standard}]
[INFO] outputDirectory:
/home/hudson/jobs/maven-3/workspace/maven-3/maven-core/target/generated-sources/modello
[INFO] Working on model: src/main/mdo/toolchains.mdo
[INFO] Generating current version: 1.0.0
[INFO] Working on model: src/main/mdo/metadata.mdo
[INFO] Generating current version: 1.0.0
[INFO] [modello:xpp3-reader {execution: standard}]
[INFO] outputDirectory:
/home/hudson/jobs/maven-3/workspace/maven-3/maven-core/target/generated-sources/modello
[INFO] Working on model: src/main/mdo/toolchains.mdo
[INFO] Generating current version: 1.0.0
[INFO] Working on model: src/main/mdo/metadata.mdo
[INFO] Generating current version: 1.0.0
[INFO] [modello:xpp3-writer {execution: standard}]
[INFO] outputDirectory:
/home/hudson/jobs/maven-3/workspace/maven-3/maven-core/target/generated-sources/modello
[INFO] Working on model: src/main/mdo/toolchains.mdo
[INFO] Generating current version: 1.0.0
[INFO] Working on model: src/main/mdo/metadata.mdo
[INFO] Generating current version: 1.0.0
[INFO] [remote-resources:process {execution: default}]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING]
Re: maven 3.0 build failure with IBM SDK 5
A note on this one.
Build works with an IBM SDK 6.
2009/11/3 Henri Gomez henri.go...@gmail.com:
Hi to all,
I just added a job on our Hudson server to build Maven 3.0 from the trunk.
The job use maven 2.2.1 and a custom repository (to avoid collisions
with our others projects).
Goals are clean install and MAVEN_OPTS is set to -Xmx512m
No problem when I use a Sun JVM Java 5.
But if I select an IBM SDK 5 (SR9) as build JVM, the build fail :
[INFO]
[INFO] Building Maven Core
[INFO] task-segment: [clean, install]
[INFO]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set:
/home/hudson/jobs/maven-3/workspace/maven-3/maven-core/target
(included: [**], excluded: [])
[INFO] [modello:java {execution: standard}]
[INFO] outputDirectory:
/home/hudson/jobs/maven-3/workspace/maven-3/maven-core/target/generated-sources/modello
[INFO] Working on model: src/main/mdo/toolchains.mdo
[INFO] Generating current version: 1.0.0
[INFO] Working on model: src/main/mdo/metadata.mdo
[INFO] Generating current version: 1.0.0
[INFO] [modello:xpp3-reader {execution: standard}]
[INFO] outputDirectory:
/home/hudson/jobs/maven-3/workspace/maven-3/maven-core/target/generated-sources/modello
[INFO] Working on model: src/main/mdo/toolchains.mdo
[INFO] Generating current version: 1.0.0
[INFO] Working on model: src/main/mdo/metadata.mdo
[INFO] Generating current version: 1.0.0
[INFO] [modello:xpp3-writer {execution: standard}]
[INFO] outputDirectory:
/home/hudson/jobs/maven-3/workspace/maven-3/maven-core/target/generated-sources/modello
[INFO] Working on model: src/main/mdo/toolchains.mdo
[INFO] Generating current version: 1.0.0
[INFO] Working on model: src/main/mdo/metadata.mdo
[INFO] Generating current version: 1.0.0
[INFO] [remote-resources:process {execution: default}]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2c4a2c4a
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva
Re: maven 3.0 build failure with IBM SDK 5
Henri Gomez wrote: Caused by: org.apache.maven.shared.filtering.MavenFilteringException at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:130) at org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources(DefaultMavenResourcesFiltering.java:262) at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:250) ... 31 more Caused by: sun.io.MalformedInputException Fixed in r832389. In future maven 2.2.2 ? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven 3.0 build failure with IBM SDK 5
Hi Benjamin, What's the JIRA for this problem (and fix in r832389) ? I'd like to verify if this bug could affect some of ours projects Regards 2009/11/3 Benjamin Bentmann benjamin.bentm...@udo.edu: Henri Gomez wrote: Caused by: org.apache.maven.shared.filtering.MavenFilteringException at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:130) at org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources(DefaultMavenResourcesFiltering.java:262) at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:250) ... 31 more Caused by: sun.io.MalformedInputException Fixed in r832389. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven 3.0 build failure with IBM SDK 5
FYI: After upgrading our IBM SDK 1.5 to SR10 (build pxi32dev-20090707 (SR10 ), maven-3 from trunk build with maven 2.2.1. SDK is now : java version 1.5.0 Java(TM) 2 Runtime Environment, Standard Edition (build pxi32dev-20090707 (SR10 )) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20090707 (JIT enabled) J9VM - 20090706_38445_lHdSMr JIT - 20090623_1334_r8 GC - 200906_09) JCL - 20090705 Regards 2009/11/3 Henri Gomez henri.go...@gmail.com: Hi Benjamin, What's the JIRA for this problem (and fix in r832389) ? I'd like to verify if this bug could affect some of ours projects Regards 2009/11/3 Benjamin Bentmann benjamin.bentm...@udo.edu: Henri Gomez wrote: Caused by: org.apache.maven.shared.filtering.MavenFilteringException at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:130) at org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources(DefaultMavenResourcesFiltering.java:262) at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:250) ... 31 more Caused by: sun.io.MalformedInputException Fixed in r832389. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Building Maven 3.0 from trunk
Hi to all, After build Maven 3 from trunk (https://svn.apache.org/repos/asf/maven/maven-3/trunk/) with ant, I tried to build it with maven 2.2.1 but the build failed about a missing svn command. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Building Maven 3.0 from trunk
If you have a missing SVN command, that may mean you do not have an SVN client installed. You should have one installed on your path so when you type svn --version (that's two dashes), you'll know what version you have. yep, I know that, svn command is installed on my OS/X but not on my Windows/Cygwin box :) I was trying to understand why the maven build need a native svn whereas the ant didn't. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Building Maven 3.0 from trunk
2009/10/29 Henri Gomez henri.go...@gmail.com: If you have a missing SVN command, that may mean you do not have an SVN client installed. You should have one installed on your path so when you type svn --version (that's two dashes), you'll know what version you have. yep, I know that, svn command is installed on my OS/X but not on my Windows/Cygwin box :) I was trying to understand why the maven build need a native svn whereas the ant didn't. Well I do a mistake, svn client is also required in the ant build. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: preparing for the next 3.x alpha release
I just tried a project build with the latest maven 3.0 snapshot (Apache Maven 3.0-SNAPSHOT (r828677; 2009-10-22 15:19:50+0200)) It seems to be a problem with the jaxws-maven-plugin 1.11 : Here is the stack trace : [DEBUG] /Users/henri/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar [DEBUG] /Users/henri/.m2/repository/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar [DEBUG] /Users/henri/.m2/repository/javax/transaction/jta/1.1/jta-1.1.jar [DEBUG] /Users/henri/.m2/repository/commons-logging/commons-logging-api/1.1/commons-logging-api-1.1.jar [DEBUG] /Users/henri/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar [DEBUG] /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-server/3.1/xmlrpc-server-3.1.jar [DEBUG] /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-common/3.1/xmlrpc-common-3.1.jar [DEBUG] /Users/henri/.m2/repository/org/apache/ws/commons/util/ws-commons-util/1.0.2/ws-commons-util-1.0.2.jar [DEBUG] /Users/henri/.m2/repository/junit/junit/4.4/junit-4.4.jar [DEBUG] /Users/henri/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar [DEBUG] /Users/henri/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar [DEBUG] /Users/henri/.m2/repository/com/lowagie/itext/2.0.6/itext-2.0.6.jar [DEBUG] /Users/henri/.m2/repository/net/sourceforge/jexcelapi/jxl/2.6.3/jxl-2.6.3.jar [DEBUG] /Users/henri/.m2/repository/commons-dbcp/commons-dbcp/1.2.2/commons-dbcp-1.2.2.jar [DEBUG] /Users/henri/.m2/repository/commons-pool/commons-pool/1.3/commons-pool-1.3.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/org.osgi.core/1.2.0/org.osgi.core-1.2.0.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/org.osgi.compendium/1.2.0/org.osgi.compendium-1.2.0.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/javax.servlet/1.0.0/javax.servlet-1.0.0.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/org.osgi.foundation/1.2.0/org.osgi.foundation-1.2.0.jar [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 7.626s [INFO] Finished at: Thu Oct 22 22:48:18 CEST 2009 [INFO] Final Memory: 14M/79M [INFO] [ERROR] [0] org.apache.maven.plugin.PluginExecutionException: : : null at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:547) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:317) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:224) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:97) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:453) at org.apache.maven.cli.MavenCli.main(MavenCli.java:105) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.PluginExecutionException: : null at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114) ... 14 more Caused by: java.lang.NullPointerException at org.codehaus.mojo.jaxws.AbstractJaxwsMojo.initClassLoader(AbstractJaxwsMojo.java:110) at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:92) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) ... 14 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [0] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: preparing for the next 3.x alpha release
More on this one. Occurs on Snow Leopard (didn't tried yet on Linux/Windows) and with the jaxws-maven-plugin 1.11. I works with the jaxws-maven-plugin 1.10 :-( 2009/10/22 Henri Gomez henri.go...@gmail.com: I just tried a project build with the latest maven 3.0 snapshot (Apache Maven 3.0-SNAPSHOT (r828677; 2009-10-22 15:19:50+0200)) It seems to be a problem with the jaxws-maven-plugin 1.11 : Here is the stack trace : [DEBUG] /Users/henri/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar [DEBUG] /Users/henri/.m2/repository/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar [DEBUG] /Users/henri/.m2/repository/javax/transaction/jta/1.1/jta-1.1.jar [DEBUG] /Users/henri/.m2/repository/commons-logging/commons-logging-api/1.1/commons-logging-api-1.1.jar [DEBUG] /Users/henri/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar [DEBUG] /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-server/3.1/xmlrpc-server-3.1.jar [DEBUG] /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-common/3.1/xmlrpc-common-3.1.jar [DEBUG] /Users/henri/.m2/repository/org/apache/ws/commons/util/ws-commons-util/1.0.2/ws-commons-util-1.0.2.jar [DEBUG] /Users/henri/.m2/repository/junit/junit/4.4/junit-4.4.jar [DEBUG] /Users/henri/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar [DEBUG] /Users/henri/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar [DEBUG] /Users/henri/.m2/repository/com/lowagie/itext/2.0.6/itext-2.0.6.jar [DEBUG] /Users/henri/.m2/repository/net/sourceforge/jexcelapi/jxl/2.6.3/jxl-2.6.3.jar [DEBUG] /Users/henri/.m2/repository/commons-dbcp/commons-dbcp/1.2.2/commons-dbcp-1.2.2.jar [DEBUG] /Users/henri/.m2/repository/commons-pool/commons-pool/1.3/commons-pool-1.3.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/org.osgi.core/1.2.0/org.osgi.core-1.2.0.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/org.osgi.compendium/1.2.0/org.osgi.compendium-1.2.0.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/javax.servlet/1.0.0/javax.servlet-1.0.0.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/org.osgi.foundation/1.2.0/org.osgi.foundation-1.2.0.jar [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 7.626s [INFO] Finished at: Thu Oct 22 22:48:18 CEST 2009 [INFO] Final Memory: 14M/79M [INFO] [ERROR] [0] org.apache.maven.plugin.PluginExecutionException: : : null at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:547) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:317) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:224) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:97) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:453) at org.apache.maven.cli.MavenCli.main(MavenCli.java:105) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.PluginExecutionException: : null at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114) ... 14 more Caused by: java.lang.NullPointerException at org.codehaus.mojo.jaxws.AbstractJaxwsMojo.initClassLoader(AbstractJaxwsMojo.java:110) at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:92) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) ... 14 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [0] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: preparing for the next 3.x alpha release
No problem with both jaxws-maven-plugin 1.10 and the latest one, jaxws-maven-plugin 1.12. Sorry for the noise 2009/10/22 Henri Gomez henri.go...@gmail.com: More on this one. Occurs on Snow Leopard (didn't tried yet on Linux/Windows) and with the jaxws-maven-plugin 1.11. I works with the jaxws-maven-plugin 1.10 :-( 2009/10/22 Henri Gomez henri.go...@gmail.com: I just tried a project build with the latest maven 3.0 snapshot (Apache Maven 3.0-SNAPSHOT (r828677; 2009-10-22 15:19:50+0200)) It seems to be a problem with the jaxws-maven-plugin 1.11 : Here is the stack trace : [DEBUG] /Users/henri/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar [DEBUG] /Users/henri/.m2/repository/javax/servlet/jsp/jsp-api/2.1/jsp-api-2.1.jar [DEBUG] /Users/henri/.m2/repository/javax/transaction/jta/1.1/jta-1.1.jar [DEBUG] /Users/henri/.m2/repository/commons-logging/commons-logging-api/1.1/commons-logging-api-1.1.jar [DEBUG] /Users/henri/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar [DEBUG] /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-server/3.1/xmlrpc-server-3.1.jar [DEBUG] /Users/henri/.m2/repository/org/apache/xmlrpc/xmlrpc-common/3.1/xmlrpc-common-3.1.jar [DEBUG] /Users/henri/.m2/repository/org/apache/ws/commons/util/ws-commons-util/1.0.2/ws-commons-util-1.0.2.jar [DEBUG] /Users/henri/.m2/repository/junit/junit/4.4/junit-4.4.jar [DEBUG] /Users/henri/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar [DEBUG] /Users/henri/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar [DEBUG] /Users/henri/.m2/repository/com/lowagie/itext/2.0.6/itext-2.0.6.jar [DEBUG] /Users/henri/.m2/repository/net/sourceforge/jexcelapi/jxl/2.6.3/jxl-2.6.3.jar [DEBUG] /Users/henri/.m2/repository/commons-dbcp/commons-dbcp/1.2.2/commons-dbcp-1.2.2.jar [DEBUG] /Users/henri/.m2/repository/commons-pool/commons-pool/1.3/commons-pool-1.3.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/org.osgi.core/1.2.0/org.osgi.core-1.2.0.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/org.osgi.compendium/1.2.0/org.osgi.compendium-1.2.0.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/javax.servlet/1.0.0/javax.servlet-1.0.0.jar [DEBUG] /Users/henri/.m2/repository/org/apache/felix/org.osgi.foundation/1.2.0/org.osgi.foundation-1.2.0.jar [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 7.626s [INFO] Finished at: Thu Oct 22 22:48:18 CEST 2009 [INFO] Final Memory: 14M/79M [INFO] [ERROR] [0] org.apache.maven.plugin.PluginExecutionException: : : null at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:547) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:317) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:224) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:97) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:453) at org.apache.maven.cli.MavenCli.main(MavenCli.java:105) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.PluginExecutionException: : null at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114) ... 14 more Caused by: java.lang.NullPointerException at org.codehaus.mojo.jaxws.AbstractJaxwsMojo.initClassLoader(AbstractJaxwsMojo.java:110) at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:92) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) ... 14 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [0] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException - To unsubscribe, e-mail
Re: Maven 2.1.0 regression with war plugin
Not really related, but what about 'un etat de l'art' of the plugins to be used with maven 2.1.0 ? I could see in the 'embedded master pom' : pluginManagement plugins plugin artifactIdmaven-antrun-plugin/artifactId version1.3/version /plugin plugin artifactIdmaven-assembly-plugin/artifactId version2.2-beta-2/version /plugin plugin artifactIdmaven-clean-plugin/artifactId version2.2/version /plugin plugin artifactIdmaven-compiler-plugin/artifactId version2.0.2/version /plugin plugin artifactIdmaven-dependency-plugin/artifactId version2.0/version /plugin plugin artifactIdmaven-deploy-plugin/artifactId version2.4/version /plugin plugin artifactIdmaven-ear-plugin/artifactId version2.3.1/version /plugin plugin artifactIdmaven-ejb-plugin/artifactId version2.1/version /plugin plugin artifactIdmaven-install-plugin/artifactId version2.2/version /plugin plugin artifactIdmaven-jar-plugin/artifactId version2.2/version /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.5/version /plugin plugin artifactIdmaven-plugin-plugin/artifactId version2.4.3/version /plugin plugin artifactIdmaven-rar-plugin/artifactId version2.2/version /plugin plugin artifactIdmaven-release-plugin/artifactId version2.0-beta-8/version /plugin plugin artifactIdmaven-resources-plugin/artifactId version2.3/version /plugin plugin artifactIdmaven-site-plugin/artifactId version2.0-beta-7/version /plugin plugin artifactIdmaven-source-plugin/artifactId version2.0.4/version /plugin plugin artifactIdmaven-surefire-plugin/artifactId version2.4.3/version /plugin plugin artifactIdmaven-war-plugin/artifactId version2.1-alpha-2/version /plugin /plugins I will be great if various plugins developpers could drop a note here about compatibility of their plugins with the new 2.1.0 :) Regards 2009/3/24 Jörg Schaible joerg.schai...@gmx.de: nicolas de loof wrote at Dienstag, 24. März 2009 17:00: Hi, my build doesn't work anymore with Maven 2.1.0. The maven-war-plugin in version 2.1-* fails with : Did you try the latest one released two days ago (2.0-beta-1) ? - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven archetypes questions
I'm creating some in-house archectypes.
I've got some questions :
- I need to add extra parameters, ie -DappId and got it resolved in
the generated pom.xml
I do :
mvn archetype:generate -DarchetypeGroupId=org.mycorp.archetypes
-DarchetypeArtifactId=myapp -DarchetypeVersion=1.0-SNAPSHOT
-DgroupId=org.mycorp.urba -DartifactId=urba-myapp -DappId=WZ
but It is not resolved and i could see :
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = archetype-resources/pom.xml [line 29,column 56]
: ${appId} is not a valid reference.
- Is it possible to move some files, ie: src/main/Skel.java to another
location in the created project (ie: src/main/appId/Skel.java).
Thanks for you help
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: The Future of OSGi Maven
2009/3/17 Georgy Bolyuba boly...@gmail.com: There is a comment [1] by Igor on [2]: Henri, Tycho already discovers OSGi dependencies from bundle manifest. Does this mean that dependencies can be osgi-bundles? Where can one find more information about it? All I am able to find on Maven + OSGi is how to build osgi-bundle. Well Tycho discovers OSGI deps from MANIFEST but what about Maven (3.x) ? Is it planned for Maven 3.x dependency scanner ? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
jspc plugins : org.codehaus.mojo.jspc/jspc-maven-plugin or org.codehaus.mojo/jspc-maven-plugin ?
Hi to all, Which maven plugin should be use for JSP compilation ? parent groupIdorg.codehaus.mojo.jspc/groupId artifactIdjspc/artifactId version2.0-alpha-3/version /parent or groupIdorg.codehaus.mojo/groupId artifactIdjspc-maven-plugin/artifactId version1.4.6/version I tried the 2.0-alpha-3 but it failed with : [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-3:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-3:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' Component descriptor cannot be found in the component repository: org.codehaus.mojo.jspc.compiler.JspCompiler. Did there is still developpers of these plugins here ? Regards - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 2.1.0 Plans (a proposal of sorts)
Question about 2.1.0 / 3.0.0. In 3.0 alpha2 Jason fix a problem with jaxws-maven. Could it be backported to 2.1.0 ? Also did this new 'mileston' will be used in m2eclipse. I know Maven 3.0 is the target for m2eclipse but during the intermin, having a stable and known 2.1 would be nice. Regards 2009/2/18 John Casey jdca...@commonjava.org: Brett Porter wrote: On 18/02/2009, at 7:23 AM, John Casey wrote: It will take less effort for me to just keep working on issues until they are done, so that's what I'll do. So, agreed, next version is 2.1.0, standard RC cycle applies. I'm fine whittling away some of what's left out there. I don't think it all has to happen in 2.1.0. IMO, we should take care of the four top-voted issues if we can - and if we can be relatively sure we're not angering the gods with our hubris - then do the rest in 2.1.1. The fourth top issue seems on the face of it to be based on a common misunderstanding about how profiles are triggered and applied...probably more of a documentation/education task than anything else. I'm not sure which one you are referring to. If you look at the 2.1.0 version bucket, enable the display of vote counts, and sort on that column, you'll see one pop out related to profiles in the parent not being applied to the child. I'm guessing it's just some explaining we need to do around that in terms of doco/education, and we're done. Beyond that, I'm alright releasing 2.1.0 final provided we can be sure that the wagon version we're using is stable. I seem to remember an issue coming up shortly after the release of 2.1.0-M1 related to one of the new Wagon implementations - WebDAV, maybe? I'm having some trouble remembering/finding that issue in my gmail, but we need to make sure that doesn't get left out of this release. If it means rolling back to an older wagon version, then let's do that. It's a regression in the SSH wagon, which I've not been able to reproduce and I never saw an issue filed for. We can wait and see what happens in the RC cycle. Do you happen to have a Nabble link for that thread? I'll keep searching, but it'd be really nice to push that to resolution, as it's probably the biggest wart on 2.1.0-M1. -john - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 2.1.0 Plans (a proposal of sorts)
2009/2/18 Brett Porter br...@apache.org: On 18/02/2009, at 7:43 PM, Henri Gomez wrote: Question about 2.1.0 / 3.0.0. In 3.0 alpha2 Jason fix a problem with jaxws-maven. Could it be backported to 2.1.0 ? I believe that problem doesn't affect 2.1.0. Nope, the jaxws maven plugin didn't works with maven 2.1.0 (at least the version in m2eclipse 0.9.7) :( The following mojo encountered an error while executing: Group-Id: org.codehaus.mojo Artifact-Id: jaxws-maven-plugin Version: 1.11 Mojo: wsgen brought in via: POM While building project: Group-Id: mycorp.can Artifact-Id: mycorp-framework Version: 2.0.0-19-SNAPSHOT From file: C:\workspace-34\mycorp-framework\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.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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) at org.codehaus.classworlds.Launcher.main(Launcher.java:31) Error stacktrace: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:jaxws-maven-plugin:1.11: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
Re: Maven 2.1.0 Plans (a proposal of sorts)
I build my JAX-WS project with maven 2.1.0-M1 and it works :) Good news, but could it be used in m2eclipse ? 2009/2/18 Brett Porter br...@apache.org: As was highlighted before in these threads, this is a completely different 2.1.0 to the one previously included in m2eclipse (it never has been included): http://www.sonatype.com/people/2008/11/a-visual-history-of-maven-2/ - Brett On 18/02/2009, at 10:32 PM, Henri Gomez wrote: 2009/2/18 Brett Porter br...@apache.org: On 18/02/2009, at 7:43 PM, Henri Gomez wrote: Question about 2.1.0 / 3.0.0. In 3.0 alpha2 Jason fix a problem with jaxws-maven. Could it be backported to 2.1.0 ? I believe that problem doesn't affect 2.1.0. Nope, the jaxws maven plugin didn't works with maven 2.1.0 (at least the version in m2eclipse 0.9.7) :( The following mojo encountered an error while executing: Group-Id: org.codehaus.mojo Artifact-Id: jaxws-maven-plugin Version: 1.11 Mojo: wsgen brought in via: POM While building project: Group-Id: mycorp.can Artifact-Id: mycorp-framework Version: 2.0.0-19-SNAPSHOT From file: C:\workspace-34\mycorp-framework\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.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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) at org.codehaus.classworlds.Launcher.main(Launcher.java:31) Error stacktrace: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:jaxws-maven-plugin:1.11: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
Re: Maven 2.1.0 Plans (a proposal of sorts)
2009/2/18 Brett Porter br...@apache.org: On 18/02/2009, at 11:59 PM, Henri Gomez wrote: I build my JAX-WS project with maven 2.1.0-M1 and it works :) Good news, but could it be used in m2eclipse ? It's really something to take up with m2eclipse... but I don't see it happening for the reason I outlined earlier regarding the embedder. Sniff ;( I'll ask on m2eclipse. Thanks Brett - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release maven 2.0.10
2009/2/11 Olivier Lamy ol...@apache.org: Hi, Tested with company builds : looks fine. +1 Thanks ! Ditto here, tried with various company projects, and no problems so far - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Maven 3.0-alpha-2
I checked it with on a simple project using jaxws wsgen and it works
now (it was failing with 3.0-alpha1), good news.
I tried on other projects where I got an maven ant involved to grab
some system informations :
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idgrab-system-infos/id
phasegenerate-resources/phase
goals
goalrun/goal
/goals
configuration
tasks
mkdir dir=${project.build.directory} /
tstamp
format property=last.updated pattern=-MM-dd
hh:mm:ss /
/tstamp
echo file=${basedir}/target/filter.properties
build.time=${last.updated}${line.separator}os.infos=${os.name}
${os.version}${line.separator}user.infos=${user.name}${line.separator}java.infos=JDK
${java.vendor} ${java.runtime.version}
/echo
/tasks
/configuration
/execution
/executions
/plugin
...
If i do a mvn clean package, target directory is removed but the
antrun task complains about it.
Did there is 'updated antrun plugin' to be used ?
Did the used phase, generate-resources, is no more correct ?
Here is the stack trace :
Project File: C:\workspace-34\mycorp-jutils\pom.xml
Error stacktrace:
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the pl
ugin manager executing goal
'org.apache.maven.plugins:maven-antrun-plugin:1.1:run': Mojo execution
failed.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:259)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:201)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:164)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:207)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:846)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo
execution failed.
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:651)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:492)
... 15 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
executing ant tasks
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:114)
at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:629)
... 16 more
Caused by: java.io.FileNotFoundException:
C:\workspace-34\mycorp-jutils\target\filter.properties (Le chemin
d'accÞs spÚcifiÚ est introuvable)
at org.apache.tools.ant.taskdefs.Echo.execute(Echo.java:57)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108)
... 18 more
Caused by: java.io.FileNotFoundException:
C:\workspace-34\mycorp-jutils\target\filter.properties (Le chemin
d'accÞs spÚcifiÚ est introuvable)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.init(FileOutputStream.java:179)
at java.io.FileOutputStream.init(FileOutputStream.java:102)
at java.io.FileWriter.init(FileWriter.java:61)
at org.apache.tools.ant.taskdefs.Echo.execute(Echo.java:54)
... 22 more
[INFO]
[INFO] BUILD FAILED
[INFO]
[INFO]
Re: [VOTE] Maven 3.0-alpha-2
Ant stuff doesn't work properly. Let's do the same thing, make a test project and we'll work through it. Do you need a sample projet using ant task or something without ant ? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Maven 3.0-alpha-2
I think your problem is specifically with ant so something that represents what you tried to do in the project that failed would be handy. I'll do a sample project. If you pull a new update-dev build of m2e you'll notice that we have the problem reporting integrated now. With latest build you can go down to the Maven menu and at the bottom you'll see the Report Issue... option. You can put in the summary, description, and select the project you want to report on and it will all get bundled up and automatically submitted to our issue tracking system. Run your project so that it fails and then report the issue and I will have all the information I need. I'll be blogging about this feature later. It's very handy! Latest update-dev build of m2e allready loaded and used :) Great feature, I'll make a try at it - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Maven 3.0-alpha-2
I'll do a sample project.
Done
If you pull a new update-dev build of m2e you'll notice that we have the
problem reporting integrated now. With latest build you can go down to the
Maven menu and at the bottom you'll see the Report Issue... option. You
can put in the summary, description, and select the project you want to
report on and it will all get bundled up and automatically submitted to our
issue tracking system. Run your project so that it fails and then report the
issue and I will have all the information I need. I'll be blogging about
this feature later. It's very handy!
Latest update-dev build of m2e allready loaded and used :)
Great feature, I'll make a try at it
I tried but it failed with 'Error gathering data'. Did the reporting
tool use non HTTP ports ?
BTW, I attached the simple pom.xml
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.mycorp/groupId
artifactIdsampleant/artifactId
namesampleant/name
version1.0.0-SNAPSHOT/version
descriptionA Sample to show Ant problem with maven 3.0/description
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idgrab-system-infos/id
phasegenerate-resources/phase
goals
goalrun/goal
/goals
configuration
tasks
mkdir dir=${project.build.directory} /
tstamp
format property=last.updated pattern=-MM-dd hh:mm:ss /
/tstamp
echo file=${basedir}/target/filter.properties
build.time=${last.updated}${line.separator}os.infos=${os.name} ${os.version}${line.separator}user.infos=${user.name}${line.separator}java.infos=JDK ${java.vendor} ${java.runtime.version}
/echo
/tasks
/configuration
/execution
/executions
/plugin
/plugins
filters
filter${basedir}/target/filter.properties/filter
/filters
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
/resources
/build
/project-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: releasing 2.0.10?
So there will be 2.0.x 2.1.x and 3.0 ? 2009/1/30 Brian E. Fox bri...@reply.infinity.nu: There's a new 2.1 cut from the 2.0.x branch that provides a space to put features. We did this back in Aug/Sept but there's been little forward progress, so a release should get it started. When we planned it out, there was a lot of interest in new features but I don't think much has been done in the last 5 months, so I don't see the point in waiting for future features, lets get 2.1 out so people will start to use it. -Original Message- From: Henri Gomez [mailto:henri.go...@gmail.com] Sent: Friday, January 30, 2009 8:39 AM To: Maven Developers List Subject: Re: releasing 2.0.10? I was thinking : 2.0.x is the current Maven 2 2.1 deprecated and will became 3.0 But what is 2.2 ? or 2.1 ? I'm puzzled 2009/1/30 Brian E. Fox bri...@reply.infinity.nu: My original intent was to shift the focus to 2.1 and bring that quickly to GA. The development on it has stalled so it's irrelevant if it's feature complete or not, it's stable and usable as it is. Future features can go into 2.1.x or 2.2. -Original Message- From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict Sent: Thursday, January 29, 2009 10:58 PM To: Maven Developers List Subject: Re: releasing 2.0.10? I don't think it's wise to EOL a product without a GA replacement. It's true that because 2.1 is in milestone releases it is not usable by many people in an approved managerial environment, but, to the same token, it's not feature complete either. Personally speaking, I definitely am eagerly awaiting the issues scheduled in 2.0.11. Please continue releasing 2.0.x until 2.1/3.0 has a GA. Paul On 28/01/2009, at 9:03 AM, Brian E. Fox wrote: Normally I would agree on the late change, but it's entirely optional usage so it wouldn't affect existing builds and I'd like to start thinking about 2.0.10 being the EOL for 2.0.x. Given there's already been a good number of fixes for 2.0.11 that haven't been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and having .11 as the EOL is a better way to go - wdyt? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven 3.0-alpha-2 tagged
binaries available ? 2009/1/31 Jason van Zyl jvan...@sonatype.com: Shane/Benjamin, Go ahead and roll your changes into trunk. The alpha-2 is tagged. No messages about the vote because of a problem with the upgrade on people.apache.org which is preventing me from deploying. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: releasing 2.0.10?
2009/2/2 Brian E. Fox bri...@reply.infinity.nu: Who knows. Maybe, maybe not depending on the timing and uptake of 3.x Well if 2.1.0 is quickly stable and you need to add more stuff, 2.2.0 could be a good idea. But 2.x.y should stop at some time when 3.0 will be available or users will be stuck by so many differents versions (and a pain for developpers to check / fix so many branches). - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: releasing 2.0.10?
I agree. But no 2.2.x is planned ? 2009/2/2 Brian E. Fox bri...@reply.infinity.nu: Yes, but hopefully 2.0.x is end of life with either 2.0.10 or 2.0.11 and 2.1.x becomes the active line. -Original Message- From: Henri Gomez [mailto:henri.go...@gmail.com] Sent: Monday, February 02, 2009 3:36 AM To: Maven Developers List Subject: Re: releasing 2.0.10? So there will be 2.0.x 2.1.x and 3.0 ? 2009/1/30 Brian E. Fox bri...@reply.infinity.nu: There's a new 2.1 cut from the 2.0.x branch that provides a space to put features. We did this back in Aug/Sept but there's been little forward progress, so a release should get it started. When we planned it out, there was a lot of interest in new features but I don't think much has been done in the last 5 months, so I don't see the point in waiting for future features, lets get 2.1 out so people will start to use it. -Original Message- From: Henri Gomez [mailto:henri.go...@gmail.com] Sent: Friday, January 30, 2009 8:39 AM To: Maven Developers List Subject: Re: releasing 2.0.10? I was thinking : 2.0.x is the current Maven 2 2.1 deprecated and will became 3.0 But what is 2.2 ? or 2.1 ? I'm puzzled 2009/1/30 Brian E. Fox bri...@reply.infinity.nu: My original intent was to shift the focus to 2.1 and bring that quickly to GA. The development on it has stalled so it's irrelevant if it's feature complete or not, it's stable and usable as it is. Future features can go into 2.1.x or 2.2. -Original Message- From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict Sent: Thursday, January 29, 2009 10:58 PM To: Maven Developers List Subject: Re: releasing 2.0.10? I don't think it's wise to EOL a product without a GA replacement. It's true that because 2.1 is in milestone releases it is not usable by many people in an approved managerial environment, but, to the same token, it's not feature complete either. Personally speaking, I definitely am eagerly awaiting the issues scheduled in 2.0.11. Please continue releasing 2.0.x until 2.1/3.0 has a GA. Paul On 28/01/2009, at 9:03 AM, Brian E. Fox wrote: Normally I would agree on the late change, but it's entirely optional usage so it wouldn't affect existing builds and I'd like to start thinking about 2.0.10 being the EOL for 2.0.x. Given there's already been a good number of fixes for 2.0.11 that haven't been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and having .11 as the EOL is a better way to go - wdyt? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: releasing 2.0.10?
I was thinking : 2.0.x is the current Maven 2 2.1 deprecated and will became 3.0 But what is 2.2 ? or 2.1 ? I'm puzzled 2009/1/30 Brian E. Fox bri...@reply.infinity.nu: My original intent was to shift the focus to 2.1 and bring that quickly to GA. The development on it has stalled so it's irrelevant if it's feature complete or not, it's stable and usable as it is. Future features can go into 2.1.x or 2.2. -Original Message- From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict Sent: Thursday, January 29, 2009 10:58 PM To: Maven Developers List Subject: Re: releasing 2.0.10? I don't think it's wise to EOL a product without a GA replacement. It's true that because 2.1 is in milestone releases it is not usable by many people in an approved managerial environment, but, to the same token, it's not feature complete either. Personally speaking, I definitely am eagerly awaiting the issues scheduled in 2.0.11. Please continue releasing 2.0.x until 2.1/3.0 has a GA. Paul On 28/01/2009, at 9:03 AM, Brian E. Fox wrote: Normally I would agree on the late change, but it's entirely optional usage so it wouldn't affect existing builds and I'd like to start thinking about 2.0.10 being the EOL for 2.0.x. Given there's already been a good number of fixes for 2.0.11 that haven't been rolled up to 2.0.10-RC, maybe pushing 2.0.10 out as is and having .11 as the EOL is a better way to go - wdyt? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven 3.0.0-alpha-1 / wsgen
I checked if the maven 2.1 / wsgen (1.11) mojo problem was fixed with maven 3.0-alpha-1, but same problem ;-( [DEBUG] jaxws:wsgen args: [-d, C:\workspace-34\slib-erable-framework\target\classes, -cp, C:\workspace-34\slib-erable-framework\target\classes;c:\maven-repository\fr\slib\sx\canopee\slib-jutils\2.0.0-15\slib-jutils-2.0.0-15.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-2\stax-api-1.0-2.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\quartz\quartz\1.5.2\quartz-1.5.2.jar;c:\maven-repository\net\sf\jt400\jt400-full\6.4\jt400-full-6.4.jar;c:\maven-repository\commons-logging\commons-logging-api\1.1\commons-logging-api-1.1.jar;c:\maven-repository\log4j\log4j\1.2.14\log4j-1.2.14.jar;c:\maven-repository\org\apache\xmlrpc\xmlrpc-server\3.1\xmlrpc-server-3.1.jar;c:\maven-repository\org\apache\xmlrpc\xmlrpc-common\3.1\xmlrpc-common-3.1.jar;c:\maven-repository\org\apache\ws\commons\util\ws-commons-util\1.0.2\ws-commons-util-1.0.2.jar;c:\maven-repository\commons-httpclient\commons-httpclient\3.0.1\commons-httpclient-3.0.1.jar;c:\maven-repository\commons-codec\commons-codec\1.2\commons-codec-1.2.jar;c:\maven-repository\com\lowagie\itext\2.0.6\itext-2.0.6.jar;c:\maven-repository\net\sourceforge\jexcelapi\jxl\2.6.3\jxl-2.6.3.jar;c:\maven-repository\commons-dbcp\commons-dbcp\1.2.2\commons-dbcp-1.2.2.jar;c:\maven-repository\commons-pool\commons-pool\1.3\commons-pool-1.3.jar;c:\maven-repository\com\sun\xml\ws\jaxws-tools\2.1.5\jaxws-tools-2.1.5.jar;c:\maven-repository\com\sun\xml\ws\jaxws-rt\2.1.5\jaxws-rt-2.1.5.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.9\jaxb-impl-2.1.9.jar;c:\maven-repository\com\sun\xml\messaging\saaj\saaj-impl\1.3.2\saaj-impl-1.3.2.jar;c:\maven-repository\com\sun\xml\stream\buffer\streambuffer\0.8\streambuffer-0.8.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\woodstox\wstx-asl\3.2.3\wstx-asl-3.2.3.jar;c:\maven-repository\com\sun\org\apache\xml\internal\resolver\20050927\resolver-20050927.jar;c:\maven-repository\org\jvnet\mimepull\1.3\mimepull-1.3.jar;c:\maven-repository\com\sun\xml\bind\jaxb-xjc\2.1.9\jaxb-xjc-2.1.9.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, fr.slib.erable.soa.services.CanopeeService] [ERROR] Internal error in the plugin manager executing goal 'org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen': Mojo execution failed. While building project with id: fr.slib.sx.canopee:slib-erable-framework:jar:2.0.0-15 Project File: C:\workspace-34\slib-erable-framework\pom.xml Error stacktrace: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen': Mojo execution failed. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:259) at
Re: maven 3.0.0-alpha-1 / wsgen
It's not in the iteration for alpha-2 either, but if you want to try and tackle this we can add it to the iteration. Yes, it was a simple test case. We really need to focus on the POM specification and recent regressions we can track. The version of the embedder in m2e is from May so we are going to try and tackle things we know that has recently been broken where we have a better chance of fixing them. We're happy to help you track down things and answering questions and we'll try to get a fix in for that in the alpha-3 iteration. Seems a good plan. I could wait for alpha-3 of course (what's the iteration plans ?) my primary concern is getting a stable m2e embedder (the current is pretty old). BTW, should we expect embedder m2e from maven 3.0 iterations available as plugin for testing purposes ? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: pre maven 3.0 binaries available ?
Jason, not sure if you remember, but m2eclipse allows to install embedder updates separately from the core. So, can publish updated embedder for early adopters consumption and it will also help to catch incompatibilities in 3.0 earlier. +1, I'll be happy to check them - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
pre maven 3.0 binaries available ?
Hi to all, I wonder if there is pre maven 3.0 tarball available somewhere. I still got problem with jaxws and maven embedded (in m2eclipse) and reopened JIRA #3586 (http://jira.codehaus.org/browse/MNG-3586). BTW, the embedded maven included in latest m2eclipse is pretty old now and may be the bug is no more available, so I'd like to get/build maven pre 3.0 to make another try. Regards - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: pre maven 3.0 binaries available ?
2008/12/29 Jason van Zyl jvan...@sonatype.com: On 29-Dec-08, at 4:48 AM, Henri Gomez wrote: Hi to all, I wonder if there is pre maven 3.0 tarball available somewhere. I still got problem with jaxws and maven embedded (in m2eclipse) and reopened JIRA #3586 (http://jira.codehaus.org/browse/MNG-3586). You can reopen issues, and you probably set the fix version unintentionally but it's not going to be fixed for 3.0 alpha-1 so I've moved it out to the regression version which is alpha-3. Any date for alpha3 ? BTW, the embedded maven included in latest m2eclipse is pretty old now and may be the bug is no more available, so I'd like to get/build maven pre 3.0 to make another try. We're not going to attempt this until alpha-2 at least. All the binaries are on the grid: https://grid.sonatype.org/ci/view/Maven%203.0.x/job/maven-3.0.x-bootstrap/ But updating will take some work and we're not going to do it until our new QE resource starts with Sonatype on January 5th. Once we have a massive battery of automated tests we will attempt to update the version of the embedder. I don't think destabilizing what is presently used in m2e is prudent so we're trying to plan this as not to cause any disruptions to users. Well, I could wait a couple of week to test it. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
custom packaging, how to get jars from wars
Hi to all,
I'm writing a custom packager to help my IT create ZIP archives from a
sum of jars/wars.
I could get the jars/wars but can't figure how to get the jars
required by wars (we didn't put them in WEB-INF/lib since we should
share them).
here is my actual code, how could I get jar dependencies from the WAR artifact ?
Thanks
---
/**
* Copy runtime wars
* @throws MojoExecutionException
*/
protected int copyWars() throws MojoExecutionException {
int count = 0;
try {
Set artifacts = project.getArtifacts();
for (Iterator iter = artifacts.iterator();
iter.hasNext();) {
Artifact artifact = (Artifact) iter.next();
ScopeArtifactFilter filter = new
ScopeArtifactFilter(
Artifact.SCOPE_RUNTIME);
if (!artifact.isOptional()
filter.include(artifact)
war.equals(artifact.getType())) {
FileUtils.copyFileToDirectory(artifact.getFile(),
warDirectory);
count++;
}
}
} catch (IOException e) {
throw new MojoExecutionException(Error copying wars,
e);
}
return (count);
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: central repository cleanup please
sync to central for groupId com.extjs occured just during a content update.I now have a gxt-1.1.jar.fileparthttp://repo1.maven.org/maven2/com/extjs/gxt/1.1/gxt-1.1.jar.filepartfile in http://repo1.maven.org/maven2/com/extjs/gxt/1.1/ Can someone please delete this 1.1 folder, so that it gets a clean sync next time ? No more filepart, but the .pom is still missing - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.0.10: Plan to update super pom dependencies?
Could be a good idea to send on this list, a list of up to date plugins for those of us who set the plugins dependencies in their enterprise POM. 2008/7/11 Paul Benedict [EMAIL PROTECTED]: What will be the procedure going forward to upgrade super POM dependencies? Before the RC is cut, I'd like to see a task-type ticket open that specifically deals with the upgrade. It will be good for tracking purposes. I hope this is done per release. Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vetting issues for 2.1-alpha-XX
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
Re: Developing Maven 2.1
I tried to build the latest maven 2.1 from trunk with mvn install but it still failed in tests. What should be done to get a build of maven 2.1 ? I need it to track a classloader issue with jaxws-maven-plugin even if it seems to be a general problem with the system scope. Regards and thanks for your help - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Developing Maven 2.1
Well I 'll put your maven 2.1 build to our Hudson instance :) 2008/7/10 Jason van Zyl [EMAIL PROTECTED]: Henri, Here's the most recent build: http://ci.sonatype.org/view/Maven%202.1x/job/maven-2.1.x-bootstrap/ws/trunk/maven-distribution/target/ On 10-Jul-08, at 10:02 AM, Henri Gomez wrote: I tried to build the latest maven 2.1 from trunk with mvn install but it still failed in tests. What should be done to get a build of maven 2.1 ? I need it to track a classloader issue with jaxws-maven-plugin even if it seems to be a general problem with the system scope. Regards and thanks for your help - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Developing Maven 2.1
It builds fine for me now with 2.0.9, we've never needed to bootstrap to build 2.1 before, so what's different now? You got it works with 2.0.9 ? Just with mvn install ? If we can't trust Maven to build our own applications here, then we have a serious problem IMO that needs to be fixed. Maven 2.1 is just another application being built, there shouldn't be any concerns of cross over between the application building and the application being built. Indeed but may be my settings is incorrect ? Just get maven-2.1 from http://svn.apache.org/repos/asf/maven/components/trunk on my F: cd maven-2.1 mvn install - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
I'll do 2008/7/7 Dan Tran [EMAIL PROTECTED]: you may want ping java.net ws group, they own this plugin -D On Mon, Jul 7, 2008 at 9:15 AM, Henri Gomez [EMAIL PROTECTED] wrote: BTW, I didn't get more success with tools.jar in plugin defs : [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing: wsgen [-d, C:\workspace\slib-er-go\target\classes, -cp, C:\workspace\slib-er-go\target\classes;c:\maven-repository\fr\slib\er\slib-er-core\1.0.0-SNAPSHOT\slib-er-core-1.0.0-SNAPSHOT.jar;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\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\fr\slib\sx\canopee\slib-sx-canopee\2.0.0\slib-sx-canopee-2.0.0.pom;c:\maven-repository\fr\slib\sx\canopee\slib-jutils\2.0.0-9\slib-jutils-2.0.0-9.jar;c:\maven-repository\quartz\quartz\1.5.2\quartz-1.5.2.jar;c:\maven-repository\net\sf\jt400\jt400-full\6.2\jt400-full-6.2.jar;c:\maven-repository\fr\slib\sx\canopee\slib-erable-framework\2.0.0-9\slib-erable-framework-2.0.0-9.jar;c:\maven-repository\fr\slib\mk\slib-mk-rif\1.5.0-3\slib-mk-rif-1.5.0-3.jar;c:\maven-repository\fr\slib\er\slib-er-mkt\2.0.0-SNAPSHOT\slib-er-mkt-2.0.0-SNAPSHOT.jar;c:\maven-repository\fr\slib\mk\slib-mk-rnf\1.5.0-1\slib-mk-rnf-1.5.0-1.jar;c:\maven-repository\fr\slib\er\slib-er-pf\2.0.0-SNAPSHOT\slib-er-pf-2.0.0-SNAPSHOT.jar;c:\maven-repository\fr\slib\er\slib-er-ca\2.0.0-SNAPSHOT\slib-er-ca-2.0.0-SNAPSHOT.jar;c:\maven-repository\fr\slib\er\slib-er-vl\2.0.0-SNAPSHOT\slib-er-vl-2.0.0-SNAPSHOT.jar;C:\ibm-j2sdk1.5.0\jre\..\lib\tools.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:\maven\lib\maven-2.0.9-uber.jar;C:\maven\lib\maven-2.0.9-uber.jar, -wsdl, -r, C:\workspace\slib-er-go\target\classes\fr\slib\erable\go\resources\wsdl, fr.slib.erable.go.service.OrderService] [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error executing: wsgen [-d, C:\workspace\slib-er-go\target\classes, -cp, C:\workspace\slib-er-go\target\classes;c:\maven-repository\fr\slib\er\slib-er-core\1.0.0-SNAPSHOT\slib-er-core-1.0.0-SNAPSHOT.jar;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
Re: jaxws-maven-plugin failure on non Sun SDK
More on this :
More on this :
In the 1.10 pom file I could see :
profiles
profile
!-- This is only for non MAC OS X builds, hence the property below --
iddefault-tools.jar/id
activation
property
namejava.vendor/name
valueSun Microsystems Inc./value
/property
/activation
dependencies
dependency
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
/dependencies
/profile
/profiles
With an IBM JDK ${java.vendor} is IBM Corporation.
Sun Microsystems Inc. is only for ${java.specification.vendor}
This profile add-on has been introduced to fix Apple JVM specific
tools location but break this plugin now on IBM JDK, both Linux and
Windows ;(
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
How could I get the latest sources ? https://svn.dev.java.net/svn/jax-ws-commons/tags/jaxws-maven-plugin-1.10 require authorization. Which one ? 2008/7/7 Dan Tran [EMAIL PROTECTED]: you may want ping java.net ws group, they own this plugin -D On Mon, Jul 7, 2008 at 9:15 AM, Henri Gomez [EMAIL PROTECTED] wrote: BTW, I didn't get more success with tools.jar in plugin defs : [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing: wsgen [-d, C:\workspace\slib-er-go\target\classes, -cp, C:\workspace\slib-er-go\target\classes;c:\maven-repository\fr\slib\er\slib-er-core\1.0.0-SNAPSHOT\slib-er-core-1.0.0-SNAPSHOT.jar;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\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\fr\slib\sx\canopee\slib-sx-canopee\2.0.0\slib-sx-canopee-2.0.0.pom;c:\maven-repository\fr\slib\sx\canopee\slib-jutils\2.0.0-9\slib-jutils-2.0.0-9.jar;c:\maven-repository\quartz\quartz\1.5.2\quartz-1.5.2.jar;c:\maven-repository\net\sf\jt400\jt400-full\6.2\jt400-full-6.2.jar;c:\maven-repository\fr\slib\sx\canopee\slib-erable-framework\2.0.0-9\slib-erable-framework-2.0.0-9.jar;c:\maven-repository\fr\slib\mk\slib-mk-rif\1.5.0-3\slib-mk-rif-1.5.0-3.jar;c:\maven-repository\fr\slib\er\slib-er-mkt\2.0.0-SNAPSHOT\slib-er-mkt-2.0.0-SNAPSHOT.jar;c:\maven-repository\fr\slib\mk\slib-mk-rnf\1.5.0-1\slib-mk-rnf-1.5.0-1.jar;c:\maven-repository\fr\slib\er\slib-er-pf\2.0.0-SNAPSHOT\slib-er-pf-2.0.0-SNAPSHOT.jar;c:\maven-repository\fr\slib\er\slib-er-ca\2.0.0-SNAPSHOT\slib-er-ca-2.0.0-SNAPSHOT.jar;c:\maven-repository\fr\slib\er\slib-er-vl\2.0.0-SNAPSHOT\slib-er-vl-2.0.0-SNAPSHOT.jar;C:\ibm-j2sdk1.5.0\jre\..\lib\tools.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:\maven\lib\maven-2.0.9-uber.jar;C:\maven\lib\maven-2.0.9-uber.jar, -wsdl, -r, C:\workspace\slib-er-go\target\classes\fr\slib\erable\go\resources\wsdl, fr.slib.erable.go.service.OrderService] [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error executing: wsgen [-d, C:\workspace\slib-er-go\target\classes, -cp, C:\workspace\slib-er-go\target\classes;c:\maven-repository\fr\slib\er\slib-er-core\1.0.0-SNAPSHOT\slib-er-core-1.0.0-SNAPSHOT.jar;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
Re: jaxws-maven-plugin failure on non Sun SDK
Any news on how to get the source of jaxws-maven-plugin via SVN ? I'd like to track in sources why the plugin try to open (and read) POM as zip when using IBM SDK and not with Sun SDK. [WrapperGen - method: placeOrder(com.mycorp.myapp.orderbook.service.PlaceOrderRequest)] [method.getDeclaringType(): com.mycorp.myapp.orderbook.service.OrderService] [requestWrapper: com.mycorp.myapp.orderbook.service.jaxws.PlaceOrder] [should process method: getOrderList hasWebMethods: true ] [endpointReferencesInterface: false] [declaring class has WebSevice: true] [returning: true] [WrapperGen - method: getOrderList(com.mycorp.myapp.orderbook.service.OrderListRequest)] [method.getDeclaringType(): com.mycorp.myapp.orderbook.service.OrderService] [requestWrapper: com.mycorp.myapp.orderbook.service.jaxws.GetOrderList] [should process method: getOrderDetail hasWebMethods: true ] [endpointReferencesInterface: false] [declaring class has WebSevice: true] [returning: true] [WrapperGen - method: getOrderDetail(com.mycorp.myapp.orderbook.service.OrderDetailReques t)] [method.getDeclaringType(): com.mycorp.myapp.orderbook.service.OrderService] [requestWrapper: com.mycorp.myapp.orderbook.service.jaxws.GetOrderDetail] [ProcessedMethods Class: java.lang.Object] com\mycorp\myapp\orderbook\service\jaxws\GetOrderDetail.java com\mycorp\myapp\orderbook\service\jaxws\GetOrderDetailResponse.java com\mycorp\myapp\orderbook\service\jaxws\GetOrderList.java com\mycorp\myapp\orderbook\service\jaxws\GetOrderListResponse.java com\mycorp\myapp\orderbook\service\jaxws\OrderExceptionBean.java com\mycorp\myapp\orderbook\service\jaxws\PlaceOrder.java com\mycorp\myapp\orderbook\service\jaxws\PlaceOrderDerivative.java com\mycorp\myapp\orderbook\service\jaxws\PlaceOrderDerivativeResponse.java com\mycorp\myapp\orderbook\service\jaxws\PlaceOrderResponse.java error: error reading c:\maven-repository\com\mycorp\sx\myfwk\mycorp-sx-myfwk\2.0.0\mycorp-sx-myfwk-2.0.0.pom; Error opening zip file c:\maven-repository\com\mycorp\sx\myfwk\mycorp-sx-myfwk\2.0.0\mycorp-sx-myfwk-2.0.0.pom Note: ap round: 2 error: error reading c:\maven-repository\com\mycorp\sx\myfwk\mycorp-sx-myfwk\2.0.0\mycorp-sx-myfwk-2.0.0.pom; Error opening zip file c:\maven-repository\com\mycorp\sx\myfwk\mycorp-sx-myfwk\2.0.0\mycorp-sx-myfwk-2.0.0.pom 1 error error: compilation failed, errors should have been reported [INFO] [ERROR] BUILD ERROR [INFO] Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
Please take this to the users list. This is not even a plugin from Apache. maven dev list is not also a list for maven plugin/mojo ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
register an account with java.net, the url is here Allready got one. https://svn.dev.java.net/svn/jax-ws-commons/ Ok I'll use my account. Next step, how to provide fixes and patches ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
No, it's for our development of the core and our plugins. ok. Your questions are user questions, users also develop plugins. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
Please take this to the users list. This is not even a plugin from Apache.
A question for the dev list.
Did the system scope is still available with maven 2.1 ?
---
dependencies
dependency
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
/dependencies
---
If system scope is no more supported , I could close a bug report on
maven 2.1 (one less) ;)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
I think it should be. it should be available or no more supported ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
It will be supported. Ok, so the bug (MNG-3586) is still open, but I feel it's a problem with the tools.jar (apt) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jaxws-maven-plugin failure on non Sun SDK
Hi to all, We still get errors with jaxws-maven-plugin when were using a non Sun JDK. DEBUG] jaxws:wsgen args: [-d, C:\workspace\slib-ws-core-service\target\classes, -cp, C:\workspace\slib-ws-core-service\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\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\fr\slib\sx\canopee\slib-sx-canopee\2.0.0\slib-sx-canopee-2.0.0.pom;c:\maven-repository\fr\slib\sx\canopee\slib-jutils\2.0.0-9\slib-jutils-2.0.0-9.jar;c:\maven-repository\quartz\quartz\1.5.2\quartz-1.5.2.jar;c:\maven-repository\fr\slib\sx\canopee\slib-erable-framework\2.0.0-9\slib-erable-framework-2.0.0-9.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:\maven\lib\maven-2.0.9-uber.jar;C:\maven\lib\maven-2.0.9-uber.jar, -wsdl, -r, C:\workspace\slib-ws-core-service\target\classes\fr\slib\xylos\ws\resources\wsdl, fr.slib.xylos.ws.service.CoreService] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to execute wsgen Embedded error: com.sun.tools.apt.Main [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute wsgen at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
Re: jaxws-maven-plugin failure on non Sun SDK
A possible workaround: You could try the CXF plugins. They generate JAX-WS compliant code. Why not as a quick workaround but we should stick with JAXWS 2.1.4 impl for now ;( - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
Well the pom you could see :
profiles
profile
!-- This is only for non MAC OS X builds, hence the property below --
iddefault-tools.jar/id
activation
property
namejava.vendor/name
valueSun Microsystems Inc./value
/property
/activation
dependencies
dependency
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
/dependencies
/profile
/profiles
tools is only included when a Sun JVM is used.
Very restrictive
2008/7/7 Dan Tran [EMAIL PROTECTED]:
Caused by: java.lang.NoClassDefFoundError: com.sun.tools.apt.Main
you forgot to include tool.jar, check the plugin doc for exampl
-D
On Mon, Jul 7, 2008 at 7:23 AM, Henri Gomez [EMAIL PROTECTED] wrote:
A possible workaround: You could try the CXF plugins. They generate
JAX-WS compliant code.
Why not as a quick workaround but we should stick with JAXWS 2.1.4
impl for now ;(
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
the dependeny must in buildpluginsplugin yes, but there is no mention about this on the plugin doc ;( - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jaxws-maven-plugin failure on non Sun SDK
\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\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\fr\slib\sx\canopee\slib-sx-canopee\2.0.0\slib-sx-canopee-2.0.0.pom;c:\maven-repository\fr\slib\sx\canopee\slib-jutils\2.0.0-9\slib-jutils-2.0.0-9.jar;c:\maven-repository\quartz\quartz\1.5.2\quartz-1.5.2.jar;c:\maven-repository\net\sf\jt400\jt400-full\6.2\jt400-full-6.2.jar;c:\maven-repository\fr\slib\sx\canopee\slib-erable-framework\2.0.0-9\slib-erable-framework-2.0.0-9.jar;c:\maven-repository\fr\slib\mk\slib-mk-rif\1.5.0-3\slib-mk-rif-1.5.0-3.jar;c:\maven-repository\fr\slib\er\slib-er-mkt\2.0.0-SNAPSHOT\slib-er-mkt-2.0.0-SNAPSHOT.jar;c:\maven-repository\fr\slib\mk\slib-mk-rnf\1.5.0-1\slib-mk-rnf-1.5.0-1.jar;c:\maven-repository\fr\slib\er\slib-er-pf\2.0.0-SNAPSHOT\slib-er-pf-2.0.0-SNAPSHOT.jar;c:\maven-repository\fr\slib\er\slib-er-ca\2.0.0-SNAPSHOT\slib-er-ca-2.0.0-SNAPSHOT.jar;c:\maven-repository\fr\slib\er\slib-er-vl\2.0.0-SNAPSHOT\slib-er-vl-2.0.0-SNAPSHOT.jar;C:\ibm-j2sdk1.5.0\jre\..\lib\tools.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:\maven\lib\maven-2.0.9-uber.jar;C:\maven\lib\maven-2.0.9-uber.jar, -wsdl, -r, C:\workspace\slib-er-go\target\classes\fr\slib\erable\go\resources\wsdl, fr.slib.erable.go.service.OrderService] at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:98) at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 16 more [INFO] [INFO] Total time: 6 seconds [INFO] Finished at: Mon Jul 07 18:13:48 CEST 2008 [INFO] Final Memory: 10M/36M [INFO] 2008/7/7 Henri Gomez [EMAIL PROTECTED]: the dependeny must in buildpluginsplugin yes, but there is no mention about this on the plugin doc ;( - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vetting issues for 2.1-alpha-XX
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 [EMAIL PROTECTED]: 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=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=10500fixfor=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 [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vetting issues for 2.1-alpha-XX
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vetting issues for 2.1-alpha-XX
2008/7/4 Brett Porter [EMAIL PROTECTED]: 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
Configuration guide for developping / contributing to maven 2.1
Hi to all, I'd like to works on maven 2.1 to locate and fix a problem with jaxws-mojo (http://jira.codehaus.org/browse/MNG-3586) (Eugene suggestion :) I grabbed the trunk from maven 2.1 into my Eclipse 3.4 workspace. I use m2eclipse 0.9.4 so I enabled Maven Dependencies Management and Enabled Nested Modules. Doing a Run Maven clean works (of course) but I got many errors when trying to package maven. ie : [INFO] Unable to load parent project from a relative path: Could not find the model file 'C:\workspace-oss\maven\..\pom\maven\pom.xml'. for project unknown ... Error was: Cannot find artifact for parent POM: group:parent::1 for project group:current:jar:1 at C:\DOCUME~1\gomezhe\LOCALS~1\Temp\DefaultModelLineageBuilder.test.47733.pom [DEBUG] Stack trace: org.apache.maven.project.ProjectBuildingException: Cannot find artifact for parent POM: group:parent::1 for project group:current:jar:1 at C:\DOCUME~1\gomezhe\LOCALS~1\Temp\DefaultModelLineageBuilder.test.47733.pom at org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentFromRepositories(DefaultModelLineageBuilder.java:550) at org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentPom(DefaultModelLineageBuilder.java:414) at org.apache.maven.project.build.model.DefaultModelLineageBuilder.buildModelLineage(DefaultModelLineageBuilder.java:131) at org.apache.maven.project.build.model.DefaultModelLineageBuilderTest.testReadPOMWithMissingParentAndAllowStubsSetToTrue(DefaultModelLineageBuilderTest.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.maven.plugins:maven-eclipse-plugin' not found in repository: Unable to download the artifact from any repository I allready read http://maven.apache.org/guides/development/guide-m2-development.html and my settings are ok. I'm behind our company firewall, and we use an Archiva Repository 1.0.2 where the following proxy repository exist : http://people.apache.org/repo/m2-incubating-repository http://people.apache.org/repo/m2-snapshot-repository http://repo1.maven.org/maven2 ... Did we need more repositories or specials settings, I didn't see them in the maven developpers documentations. Thanks for your help - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuration guide for developping / contributing to maven 2.1
It's the same problem I was working on recently, the embedder tests don't honour your settings, so they don't work with a clean local repository. I added some plugin definitions to the build itself to try and trigger it to download the right artifacts (eg, resources plugin 2.2) - do you have the latest SVN of trunk? I get it this morning (CET). You can always manually get these plugins (eg mvn org.apache.maven.plugins:maven-resources-plugin:2.2:resources). It's only needed once for the local repository. How did I get them ? We do need to continue to make improvements so this isn't needed - it's quite a pain. Yes, and won't help new people involved in maven ;( Hope that helps! Just need to know which plugin to get and where, if they're not on a regular location. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuration guide for developping / contributing to maven 2.1
Tests run: 190, Failures: 4, Errors: 0, Skipped: 0 what are the failures you are getting in the target/surefire-reports directory? in maven-project/target/surefire-reports : org.apache.maven.project.MavenProjectDynamismTest.txt : --- Test set: org.apache.maven.project.MavenProjectDynamismTest --- Tests run: 7, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.906 sec FAILURE! testRoundTrip(org.apache.maven.project.MavenProjectDynamismTest) Time elapsed: 0.047 sec FAILURE! junit.framework.ComparisonFailure: Concrete source directory should be absolute. expected:...\src\main\... but was:.../src/main/... at junit.framework.Assert.assertEquals(Assert.java:81) at org.apache.maven.project.MavenProjectDynamismTest.testRoundTrip(MavenProjectDynamismTest.java:124) testShouldPreserveAddedResourceInRestoredState(org.apache.maven.project.MavenProjectDynamismTest) Time elapsed: 0.063 sec FAILURE! junit.framework.AssertionFailedError: Missing resource with directory: F:\maven-2.1\maven-project\target\test-classes\project-dynamism\target\generated-resources\plexus in concrete resources at junit.framework.Assert.fail(Assert.java:47) at org.apache.maven.project.MavenProjectDynamismTest.assertResourcePresent(MavenProjectDynamismTest.java:519) at org.apache.maven.project.MavenProjectDynamismTest.testShouldPreserveAddedResourceInRestoredState(MavenProjectDynamismTest.java:318) testShouldPreserveAddedFilterInRestoredState(org.apache.maven.project.MavenProjectDynamismTest) Time elapsed: 0.062 sec FAILURE! junit.framework.AssertionFailedError: Missing filter with path: F:\maven-2.1\maven-project\target\test-classes\project-dynamism\target\generated-filters.properties in concrete filters at junit.framework.Assert.fail(Assert.java:47) at org.apache.maven.project.MavenProjectDynamismTest.assertFilterPresent(MavenProjectDynamismTest.java:544) at org.apache.maven.project.MavenProjectDynamismTest.testShouldPreserveAddedFilterInRestoredState(MavenProjectDynamismTest.java:352) testShouldIncorporateChangedBuildDirectoryViaExpressionsOnNextConcreteCalculation(org.apache.maven.project.MavenProjectDynamismTest) Time elapsed: 0.047 sec FAILURE! junit.framework.ComparisonFailure: First concrete build output-directory should be absolute and point to target/classes dir. expected:...\... but was:.../... at junit.framework.Assert.assertEquals(Assert.java:81) at org.apache.maven.project.MavenProjectDynamismTest.testShouldIncorporateChangedBuildDirectoryViaExpressionsOnNextConcreteCalculation(MavenProjectDynamismTest.java:385) I'm using windows and got this error with both windows and cygwin shells It's not so easy to get started in maven 2.1 trunk ;( It could be a serious show stopper for volunteers who want to help in maven 2.1 (like me) Yes, I understand - I've been having the same difficulties. and you're a core commiter, experienced in maven, imagine how difficult for a newbie :) BTW, did this problem is recent or has still been here ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
