Re: JavaAgent support (SUREFIRE-179)
I took a look and the patch is quite out of date and didn't apply straight up for me. It does have tests though so with any luck I'll get a closer look at the hackathon tomorrow. The good news (sort of) is that Surefire has very few changes committed since the last release, so a release should be reasonably straightforward. - Brett On 02/11/2009, at 1:44 PM, David Blevins wrote: Is there any committer out there who has the time to review and commit this patch? Would be happy to issue a thank you blog post in the OpenEJB blog to the committer who gets this functionality in :) Would be a big bonus for OpenEJB/OpenJPA unit testers to get this or something like it in. -David - 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
Bug in Maven EAR plugin version 2.4
Hi, I came across what I think is a bug in the EAR plugin (version 2.4). Since I am not a registered contributor I cannot file this bug in JIRA myself, but I felt I want to share this with you anyway and perhaps, after verification, you can decide whether or not you will create the issue. What happens is this. Using version 2.4 the description element in the generated application.xml file is the *second* element, instead of the * first* element, which causes a schema violation. I have tested this behaviour with some earlier versions and they all generate the application.xml file correctly. So to me it looks like a regression issue where the description and display-name elements have switched places. Cheers, André Duursma Agility IT Services Trimbeets 12 8401 XC Gorredijk The Netherlands +31 (0)513 620401 +31 (0)6 50123723 an...@agility-it-services.nl http://www.agility-it-services.nl
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.
Re: [VOTE] Release Maven Runtime version 1.0-alpha-2
2009/11/2 Stephen Connolly stephen.alan.conno...@gmail.com: 2009/11/2 Mark Hobson markhob...@gmail.com: Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/ The above link is broken for me, even using the Apache Proxy :-( It wasn't synced when I sent the email, but it's working for me now. Have you still got problems accessing the site? 2009/11/2 Jason van Zyl ja...@sonatype.com: Mark, Did you close the staging repostiory? I always forget to do this so it shows up as a broken link. I did close the staging repository, but I thought Stephen was referring to the site. 2009/11/2 Benjamin Bentmann benjamin.bentm...@udo.edu: Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/ The site apparently suffers from the missing site descriptor for maven-shared-components:13, i.e. it's missing stuff like the proper skin, the Privacy Policy disclaimer etc. So I suggest before deploying the final site, you hack the POM in your local checkout of the tag to inherit from maven-shared-components:14 and deploy the site using the fixed parent. Good point, let me rollback the release and update the parent to maven-shared-components:14. I'll cancel this vote and start another one shortly. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Regression with maven-javadoc-plugin 2.6.1 and release:perform
I have the same problem. Can someone shine a light on this?
With regards,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Fri, Oct 30, 2009 at 3:42 PM, Julien HENRY henr...@yahoo.fr wrote:
Hi,
I have a multimodule project and it fails during release:perform with new
javadoc plugin.
I'm working on a simple project to open an issue, but let me explain the
issue in case someone can tell me if there is something wrong in my
configuration.
Say my project is composed of:
Parent
- moduleA
- moduleB
- moduleC
moduleB depends on moduleC.
When release:perform execture mvn deploy -Dperformrelease=true on the
freshly checkouted parent, the build fails
log says:
INFO
INFO Building MyCompany moduleA
INFO task-segment: [deploy]
INFO
[...]
INFO [javadoc:jar {execution: attach-javadocs}]
INFO The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
has not be previously called for the project:
'com.mycompany:moduleB:jar:3.1.9'. Trying to invoke it...
INFO MavenInvocationException: Error when invoking Maven, consult the
invoker log file:
D:\Projects\parent\target\checkout\moduleA\target\invoker\maven-javadoc-plugin1287795137.txt
INFO
INFO BUILD ERROR
INFO
And in the file there is:
Invoking Maven for the goals:
[org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc] with no
properties
M2_HOME=d:\apache-maven-2.2.1\bin\..
MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=256m
JAVA_HOME=C:\Program Files\Java\jdk1.6.0_14\jre\..
JAVA_OPTS=null
INFO Scanning for projects...
INFO
INFO Building MyCompany - moduleB
INFOtask-segment:
[org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc]
INFO
INFO Preparing javadoc:javadoc
INFO No goals needed for project - skipping
Downloading:
http:///com/mycompany/moduleC/3.1.9/moduleC-3.1.9.pom
INFO Unable to find resource 'com.mycompany:moduleC:pom:3.1.9' in
repository central (http://central)
INFO
ERROR BUILD ERROR
INFO
INFO Failed to resolve artifact.
Missing:
--
1) com.mycompany:moduleC:jar:3.1.9
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file xxx
Path to dependency:
1) com.mycompany:moduleB:jar:3.1.9
2) com.mycompany:moduleC:jar:3.1.9
Regards,
Julien
-
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
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
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
[VOTE] Release Maven Runtime version 1.0-alpha-2 (take 2)
Hi, This second attempt now inherits maven-shared-components:14 to fix the site skin problems. We solved 2 issues: - Added support for introspecting URLs to MavenRuntime - Added url to parsing exception messages There are no issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=component+%3D+maven-runtime+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-012/ Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/ (wait for the sync, or use the Apache proxy) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Checkstyle ready for a 2.4 release?
Hi there, Has anyone got any objections to rolling a Checkstyle 2.4 release? The big addition in this version is MCHECKSTYLE-105 [1] which upgrades Checkstyle to 5.0, and thus is compatible with Java 5. Several users have been using 2.4-SNAPSHOT successfully for a while now without problems, myself included. The remaining outstanding issue [2] is MCHECKSTYLE-123 [3]. Is there any rush to get this in 2.4 or can we defer this until 2.5? Cheers, Mark [1] http://jira.codehaus.org/browse/MCHECKSTYLE-105 [2] http://jira.codehaus.org/browse/MCHECKSTYLE/fixforversion/15336 [3] http://jira.codehaus.org/browse/MCHECKSTYLE-123 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Regression with maven-javadoc-plugin 2.6.1 and release:perform
Hi Julien,
Is it working with 2.6 and not with 2.6.1?
We have several its [1], specifically MJAVADOC-181, all seems to work.
So please create an issue [2] with a test case and your log files, we
will be able to track it.
Thanks,
Vincent
[1]
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin/src/it
[2] http://jira.codehaus.org/browse/MJAVADOC
2009/10/30 Julien HENRY henr...@yahoo.fr:
Hi,
I have a multimodule project and it fails during release:perform with new
javadoc plugin.
I'm working on a simple project to open an issue, but let me explain the
issue in case someone can tell me if there is something wrong in my
configuration.
Say my project is composed of:
Parent
- moduleA
- moduleB
- moduleC
moduleB depends on moduleC.
When release:perform execture mvn deploy -Dperformrelease=true on the freshly
checkouted parent, the build fails
log says:
INFO
INFO Building MyCompany moduleA
INFO task-segment: [deploy]
INFO
[...]
INFO [javadoc:jar {execution: attach-javadocs}]
INFO The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
has not be previously called for the project:
'com.mycompany:moduleB:jar:3.1.9'. Trying to invoke it...
INFO MavenInvocationException: Error when invoking Maven, consult the invoker
log file:
D:\Projects\parent\target\checkout\moduleA\target\invoker\maven-javadoc-plugin1287795137.txt
INFO
INFO BUILD ERROR
INFO
And in the file there is:
Invoking Maven for the goals:
[org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc] with no
properties
M2_HOME=d:\apache-maven-2.2.1\bin\..
MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=256m
JAVA_HOME=C:\Program Files\Java\jdk1.6.0_14\jre\..
JAVA_OPTS=null
INFO Scanning for projects...
INFO
INFO Building MyCompany - moduleB
INFO task-segment:
[org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc]
INFO
INFO Preparing javadoc:javadoc
INFO No goals needed for project - skipping
Downloading: http:///com/mycompany/moduleC/3.1.9/moduleC-3.1.9.pom
INFO Unable to find resource 'com.mycompany:moduleC:pom:3.1.9' in repository
central (http://central)
INFO
ERROR BUILD ERROR
INFO
INFO Failed to resolve artifact.
Missing:
--
1) com.mycompany:moduleC:jar:3.1.9
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file xxx
Path to dependency:
1) com.mycompany:moduleB:jar:3.1.9
2) com.mycompany:moduleC:jar:3.1.9
Regards,
Julien
-
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: Bug in Maven EAR plugin version 2.4
Hi André, Thanks for the notification. You can freely create an account on jira.codehaus.org and you will have access. I am bit surprised about the regression because the only thing we changed is JavaEE6 support but I'll double check if some regression was not introduced. Thanks, Stéphane On Sat, Oct 31, 2009 at 1:16 PM, André Duursma an...@agility-it-services.nl wrote: Hi, I came across what I think is a bug in the EAR plugin (version 2.4). Since I am not a registered contributor I cannot file this bug in JIRA myself, but I felt I want to share this with you anyway and perhaps, after verification, you can decide whether or not you will create the issue. What happens is this. Using version 2.4 the description element in the generated application.xml file is the *second* element, instead of the * first* element, which causes a schema violation. I have tested this behaviour with some earlier versions and they all generate the application.xml file correctly. So to me it looks like a regression issue where the description and display-name elements have switched places. Cheers, André Duursma Agility IT Services Trimbeets 12 8401 XC Gorredijk The Netherlands +31 (0)513 620401 +31 (0)6 50123723 an...@agility-it-services.nl http://www.agility-it-services.nl -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge
Re: Checkstyle ready for a 2.4 release?
Hi, maven-reporting-impl:2.0.4.3 should be release to be able to write single report, ie mvn checkstyle:checkstyle See MSHARED-120 Cheers, Vincent 2009/11/3 Mark Hobson markhob...@gmail.com: Hi there, Has anyone got any objections to rolling a Checkstyle 2.4 release? The big addition in this version is MCHECKSTYLE-105 [1] which upgrades Checkstyle to 5.0, and thus is compatible with Java 5. Several users have been using 2.4-SNAPSHOT successfully for a while now without problems, myself included. The remaining outstanding issue [2] is MCHECKSTYLE-123 [3]. Is there any rush to get this in 2.4 or can we defer this until 2.5? Cheers, Mark [1] http://jira.codehaus.org/browse/MCHECKSTYLE-105 [2] http://jira.codehaus.org/browse/MCHECKSTYLE/fixforversion/15336 [3] http://jira.codehaus.org/browse/MCHECKSTYLE-123 - 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: Bug in Maven EAR plugin version 2.4
a sample project demonstrating the problem is essential here. I've tried to reproduce but always ended up with the display name being first. Thanks Milos On Tue, Nov 3, 2009 at 2:10 PM, Stephane Nicoll stephane.nic...@gmail.comwrote: Hi André, Thanks for the notification. You can freely create an account on jira.codehaus.org and you will have access. I am bit surprised about the regression because the only thing we changed is JavaEE6 support but I'll double check if some regression was not introduced. Thanks, Stéphane On Sat, Oct 31, 2009 at 1:16 PM, André Duursma an...@agility-it-services.nl wrote: Hi, I came across what I think is a bug in the EAR plugin (version 2.4). Since I am not a registered contributor I cannot file this bug in JIRA myself, but I felt I want to share this with you anyway and perhaps, after verification, you can decide whether or not you will create the issue. What happens is this. Using version 2.4 the description element in the generated application.xml file is the *second* element, instead of the * first* element, which causes a schema violation. I have tested this behaviour with some earlier versions and they all generate the application.xml file correctly. So to me it looks like a regression issue where the description and display-name elements have switched places. Cheers, André Duursma Agility IT Services Trimbeets 12 8401 XC Gorredijk The Netherlands +31 (0)513 620401 +31 (0)6 50123723 an...@agility-it-services.nl http://www.agility-it-services.nl -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge
[VOTE] Release Maven reporting impl version 2.0.4.3
Hi, This is a maintenance release to fix MSHARED-120. Staging repo: https://repository.apache.org/content/repositories/maven-013/ Staging site: http://maven.apache.org/shared/maven-reporting-impl-2.0.4.3 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Runtime version 1.0-alpha-2 (take 2)
+1 2009/11/3 Mark Hobson markhob...@gmail.com: Hi, This second attempt now inherits maven-shared-components:14 to fix the site skin problems. We solved 2 issues: - Added support for introspecting URLs to MavenRuntime - Added url to parsing exception messages There are no issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=component+%3D+maven-runtime+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-012/ Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/ (wait for the sync, or use the Apache proxy) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Mark - 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
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
Re: maven 3.0 build failure with IBM SDK 5
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
Re: Bug in Maven EAR plugin version 2.4
Stephane Nicoll wrote at Dienstag, 3. November 2009 14:10: Hi André, Thanks for the notification. You can freely create an account on jira.codehaus.org and you will have access. I am bit surprised about the regression because the only thing we changed is JavaEE6 support but I'll double check if some regression was not introduced. Please check also HashMap vs. LinkedHashMap. With Java 5 typically the (undefined) order of the HashMap changes because of internal modifications of the algorithm. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Bug in Maven EAR plugin version 2.4
We are not using that there as far as I know but I'll check anyway Thx Sent from my iPhone On 03 Nov 2009, at 15:49, Jörg Schaible joerg.schai...@gmx.de wrote: Stephane Nicoll wrote at Dienstag, 3. November 2009 14:10: Hi André, Thanks for the notification. You can freely create an account on jira.codehaus.org and you will have access. I am bit surprised about the regression because the only thing we changed is JavaEE6 support but I'll double check if some regression was not introduced. Please check also HashMap vs. LinkedHashMap. With Java 5 typically the (undefined) order of the HashMap changes because of internal modifications of the algorithm. - 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
devoxx?
Hey guys, Who's coming at the devoxx conference this year? _o/ S. -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge
RE: devoxx?
when? where ? what is being presented? pricetag? Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Tue, 3 Nov 2009 17:25:48 +0100 Subject: devoxx? From: stephane.nic...@gmail.com To: dev@maven.apache.org Hey guys, Who's coming at the devoxx conference this year? _o/ S. -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge _ Hotmail: Trusted email with Microsoft's powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141664/direct/01/ http://clk.atdmt.com/GBL/go/177141664/direct/01/
Re: devoxx?
Oh, I thought it was well known enough. Ever heard of Javapolis? :) - 16th to 20th Nov, Antwerp - Belgium You'll find everything on the website (http://www.devoxx.com). If I am not mistaken, Jason has a BOF on Maven3. Nicolas might come. That's all I know. On a more personal note, I believe this conference has a very low pricetag given the content! S. 2009/11/3 Martin Gainty mgai...@hotmail.com when? where ? what is being presented? pricetag? Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Tue, 3 Nov 2009 17:25:48 +0100 Subject: devoxx? From: stephane.nic...@gmail.com To: dev@maven.apache.org Hey guys, Who's coming at the devoxx conference this year? _o/ S. -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge _ Hotmail: Trusted email with Microsoft's powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141664/direct/01/ http://clk.atdmt.com/GBL/go/177141664/direct/01/ -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge
Re: JavaAgent support (SUREFIRE-179)
Yeah, I wasn't sure if that patch was still good (or if it ever was). Thanks for taking a look a it! -David On Nov 3, 2009, at 12:15 AM, Brett Porter wrote: I took a look and the patch is quite out of date and didn't apply straight up for me. It does have tests though so with any luck I'll get a closer look at the hackathon tomorrow. The good news (sort of) is that Surefire has very few changes committed since the last release, so a release should be reasonably straightforward. - Brett On 02/11/2009, at 1:44 PM, David Blevins wrote: Is there any committer out there who has the time to review and commit this patch? Would be happy to issue a thank you blog post in the OpenEJB blog to the committer who gets this functionality in :) Would be a big bonus for OpenEJB/OpenJPA unit testers to get this or something like it in. -David - 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
Enable source-release assembly on Apache parent POM?
Hi, Seems like the source-release assembly is working pretty well, particularly now that Benjamin refined it. IMO it's stable enough for us to add the configuration to the ASF parent POM, so other projects can benefit. If nobody has an objection, I'll port this configuration over and stage a parent-POM release this week. Thanks, -john - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: What's blocking releasing maven-compiler-plugin?
On 2009-11-03, at 17:50-something, Benjamin Bentmann wrote: 2009/11/2 Jason van Zyl ja...@sonatype.com I'm sure we could find a clean place to inject an override for the default version of the compiler plugin in 3.x and then use that version of Maven to build as many on the grid as we can. Can't think of a better way to test a core plugin to make sure we don't hose anyone. How about this: We implement some lifecycle participant, let's call it the PluginVersionEnforcer, that would listen for afterProjectsRead() and iterates over all projects in the session in order to mutate plugin versions in their models. This lifecycle participant could be reused for all kinds of plugins if it gets configured via execution properties, that it can read from the session, e.g. -Dorg.apache.maven.plugins:maven-compiler-plugin=2.1-SNAPSHOT which could be added to the configuration of grid builds. This participant would be some little JAR that we could drop into a regular Maven 3.x distro on the grid. Benjamin +1 -Stephen P.S. hopefully your SMTP server gets working soon - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Dropping staged repository maven-archetype:2.0-alpha-5
Yes, we now have the source bundle issue resolved, just upgrade to the latest maven parents...and we are still using Nexus where you staged it last time ;-) 2009/11/3 Raphaël Piéroni raphaelpier...@gmail.com: Hello Benjamin, I am really sorry for not having concluded the release process (yet). But at that time there was a blocking issue (releasing the source). Also at that time i got no time to upgrade my release process to get the source artifact. Hence i got taken n work during the summer and part of the automn. Is there anything done about the automatic release of sources along side the binary in the default release process in the parent of plugins' pom ? Also do you know if the main repo is now using a repository manager like nexus or archiva? Regards, Raphaël 2009/11/2 Benjamin Bentmann benjamin.bentm...@udo.edu Hi, Unless somebody objects, I'm going to drop the staging repository maven-staging-003 [0] which is a left over of a failed release [1] by the end of the week. Benjamin [0] https://repository.apache.org/content/repositories/maven-staging-003/ [1] http://www.mail-archive.com/dev@maven.apache.org/msg80545.html - 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: Dropping staged repository maven-archetype:2.0-alpha-5
Hello Benjamin, I am really sorry for not having concluded the release process (yet). But at that time there was a blocking issue (releasing the source). Also at that time i got no time to upgrade my release process to get the source artifact. Hence i got taken n work during the summer and part of the automn. Is there anything done about the automatic release of sources along side the binary in the default release process in the parent of plugins' pom ? Also do you know if the main repo is now using a repository manager like nexus or archiva? Regards, Raphaël 2009/11/2 Benjamin Bentmann benjamin.bentm...@udo.edu Hi, Unless somebody objects, I'm going to drop the staging repository maven-staging-003 [0] which is a left over of a failed release [1] by the end of the week. Benjamin [0] https://repository.apache.org/content/repositories/maven-staging-003/ [1] http://www.mail-archive.com/dev@maven.apache.org/msg80545.html - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Enable source-release assembly on Apache parent POM?
+1, a few people here at the hackathon have asked it to be promoted so they can benefit on other ASF projects. On Tue, Nov 3, 2009 at 4:05 PM, John Casey jdca...@commonjava.org wrote: Hi, Seems like the source-release assembly is working pretty well, particularly now that Benjamin refined it. IMO it's stable enough for us to add the configuration to the ASF parent POM, so other projects can benefit. If nobody has an objection, I'll port this configuration over and stage a parent-POM release this week. Thanks, -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
Java versions within surefire ?
I am working on a patch to surefire and find that habitually I'm consistently grabbing got my 's and java 5 for loops. I see the following seems to apply: Some surefire-providers have an implicit java 5 requirement because (like junit 4) they support java 5 projects. But what language levels are effective in shared modules (like surefire-api), surefire-plugin and surefire-booter ? At least sine poms don't seem to be entirely correctly set up to refelect language levels either (testng provider uses java 5 features but does not seem to be at java 5 language level in the poms - AFAIK) Regards, Kristian Rosenvold - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
