You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jerome Lacoste (JIRA)" <ji...@codehaus.org> on 2007/12/14 09:50:57 UTC
[jira] Created: (SUREFIRE-409) Upgrading to surefire 2.4-SNAPSHOT
breaks my build
Upgrading to surefire 2.4-SNAPSHOT breaks my build
--------------------------------------------------
Key: SUREFIRE-409
URL: http://jira.codehaus.org/browse/SUREFIRE-409
Project: Maven Surefire
Issue Type: Bug
Components: classloading
Affects Versions: 2.4
Reporter: Jerome Lacoste
Attachments: mvn_2.3_with_systemClassLoader.log, mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, mvn_2.4_without_systemClassLoader.log, pom.diff, pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt
If I upgrade surefire in the Mowebstart plugin project, I get test failures:
Caused by: java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63
)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
... 43 more
It sounds like SUREFIRE-347.
Note that my build was broke on Windows. I usually build on Linux so I didn't notice the problem. Maybe it has been there for a while. I also attach here the error I was getting when building with 2.3 on Windows. So I removed the useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't try on Linux).
Then I upgraded to surefire plugin 2.4 and started to see failures in test. I added the useSystemClassLoader=true section in the surefire plugin config still the same issue.
I will try on linux when I get the time...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-409) Upgrading to surefire 2.4-SNAPSHOT
breaks my build
Posted by "Jerome Lacoste (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116783 ]
Jerome Lacoste commented on SUREFIRE-409:
-----------------------------------------
sorry for the bad title. I can't change it. Better one: "test fails (due to bad plexus isolation?) after upgrading from 2.3 to latest 2.4 SNAPSHOT"
> Upgrading to surefire 2.4-SNAPSHOT breaks my build
> --------------------------------------------------
>
> Key: SUREFIRE-409
> URL: http://jira.codehaus.org/browse/SUREFIRE-409
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
> Affects Versions: 2.4
> Reporter: Jerome Lacoste
> Attachments: mvn_2.3_with_systemClassLoader.log, mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, mvn_2.4_without_systemClassLoader.log, pom.diff, pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt
>
>
> If I upgrade surefire in the Mowebstart plugin project, I get test failures:
> Caused by: java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
> at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63
> )
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at java.lang.Class.newInstance0(Class.java:350)
> at java.lang.Class.newInstance(Class.java:303)
> at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
> ... 43 more
> It sounds like SUREFIRE-347.
> Note that my build was broke on Windows. I usually build on Linux so I didn't notice the problem. Maybe it has been there for a while. I also attach here the error I was getting when building with 2.3 on Windows. So I removed the useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't try on Linux).
> Then I upgraded to surefire plugin 2.4 and started to see failures in test. I added the useSystemClassLoader=true section in the surefire plugin config still the same issue.
> I will try on linux when I get the time...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-409) Upgrading to surefire 2.4-SNAPSHOT
breaks my build
Posted by "Jerome Lacoste (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerome Lacoste updated SUREFIRE-409:
------------------------------------
Attachment: pom_2.4_with_systemClassLoader.xml
pom.diff
mvn_2.4_without_systemClassLoader.log
> Upgrading to surefire 2.4-SNAPSHOT breaks my build
> --------------------------------------------------
>
> Key: SUREFIRE-409
> URL: http://jira.codehaus.org/browse/SUREFIRE-409
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
> Affects Versions: 2.4
> Reporter: Jerome Lacoste
> Attachments: mvn_2.3_with_systemClassLoader.log, mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, mvn_2.4_without_systemClassLoader.log, pom.diff, pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt
>
>
> If I upgrade surefire in the Mowebstart plugin project, I get test failures:
> Caused by: java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
> at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63
> )
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at java.lang.Class.newInstance0(Class.java:350)
> at java.lang.Class.newInstance(Class.java:303)
> at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
> ... 43 more
> It sounds like SUREFIRE-347.
> Note that my build was broke on Windows. I usually build on Linux so I didn't notice the problem. Maybe it has been there for a while. I also attach here the error I was getting when building with 2.3 on Windows. So I removed the useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't try on Linux).
> Then I upgraded to surefire plugin 2.4 and started to see failures in test. I added the useSystemClassLoader=true section in the surefire plugin config still the same issue.
> I will try on linux when I get the time...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-409) test fails (due to bad plexus
isolation?) after upgrading from 2.3 to latest 2.4 SNAPSHOT
Posted by "Jerome Lacoste (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117358 ]
Jerome Lacoste commented on SUREFIRE-409:
-----------------------------------------
so upgrading surefire just reveals a bug that existed before.
In my case the issue was that plexus-utils had been relocated (from plexus to org.codehaus.plexus) and the dependency resolver doesn't appear to be able to take this into account. Thus the duplication.
I've added 4-5 excludes and now the plexus deps are not duplicated in the classpath. I will have now to check that this indeed solves the build problem on Windows.
Thanks a lot for the troubleshooting.I owe you one.
> test fails (due to bad plexus isolation?) after upgrading from 2.3 to latest 2.4 SNAPSHOT
> -----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-409
> URL: http://jira.codehaus.org/browse/SUREFIRE-409
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
> Affects Versions: 2.4
> Reporter: Jerome Lacoste
> Attachments: mvn_2.3_with_systemClassLoader.log, mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, mvn_2.4_without_systemClassLoader.log, pom.diff, pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt
>
>
> If I upgrade surefire in the Mowebstart plugin project, I get test failures:
> Caused by: java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
> at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63
> )
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at java.lang.Class.newInstance0(Class.java:350)
> at java.lang.Class.newInstance(Class.java:303)
> at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
> ... 43 more
> It sounds like SUREFIRE-347.
> Note that my build was broke on Windows. I usually build on Linux so I didn't notice the problem. Maybe it has been there for a while. I also attach here the error I was getting when building with 2.3 on Windows. So I removed the useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't try on Linux).
> Then I upgraded to surefire plugin 2.4 and started to see failures in test. I added the useSystemClassLoader=true section in the surefire plugin config still the same issue.
> I will try on linux when I get the time...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-409) test fails (due to bad plexus
isolation?) after upgrading from 2.3 to latest 2.4 SNAPSHOT
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated SUREFIRE-409:
-----------------------------------
Summary: test fails (due to bad plexus isolation?) after upgrading from 2.3 to latest 2.4 SNAPSHOT (was: Upgrading to surefire 2.4-SNAPSHOT breaks my build)
> test fails (due to bad plexus isolation?) after upgrading from 2.3 to latest 2.4 SNAPSHOT
> -----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-409
> URL: http://jira.codehaus.org/browse/SUREFIRE-409
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
> Affects Versions: 2.4
> Reporter: Jerome Lacoste
> Attachments: mvn_2.3_with_systemClassLoader.log, mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, mvn_2.4_without_systemClassLoader.log, pom.diff, pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt
>
>
> If I upgrade surefire in the Mowebstart plugin project, I get test failures:
> Caused by: java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
> at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63
> )
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at java.lang.Class.newInstance0(Class.java:350)
> at java.lang.Class.newInstance(Class.java:303)
> at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
> ... 43 more
> It sounds like SUREFIRE-347.
> Note that my build was broke on Windows. I usually build on Linux so I didn't notice the problem. Maybe it has been there for a while. I also attach here the error I was getting when building with 2.3 on Windows. So I removed the useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't try on Linux).
> Then I upgraded to surefire plugin 2.4 and started to see failures in test. I added the useSystemClassLoader=true section in the surefire plugin config still the same issue.
> I will try on linux when I get the time...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-409) Upgrading to surefire 2.4-SNAPSHOT
breaks my build
Posted by "Jerome Lacoste (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerome Lacoste updated SUREFIRE-409:
------------------------------------
Attachment: test-failure-2.4.txt
svn_info.txt
> Upgrading to surefire 2.4-SNAPSHOT breaks my build
> --------------------------------------------------
>
> Key: SUREFIRE-409
> URL: http://jira.codehaus.org/browse/SUREFIRE-409
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
> Affects Versions: 2.4
> Reporter: Jerome Lacoste
> Attachments: mvn_2.3_with_systemClassLoader.log, mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, mvn_2.4_without_systemClassLoader.log, pom.diff, pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt
>
>
> If I upgrade surefire in the Mowebstart plugin project, I get test failures:
> Caused by: java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
> at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63
> )
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at java.lang.Class.newInstance0(Class.java:350)
> at java.lang.Class.newInstance(Class.java:303)
> at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
> ... 43 more
> It sounds like SUREFIRE-347.
> Note that my build was broke on Windows. I usually build on Linux so I didn't notice the problem. Maybe it has been there for a while. I also attach here the error I was getting when building with 2.3 on Windows. So I removed the useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't try on Linux).
> Then I upgraded to surefire plugin 2.4 and started to see failures in test. I added the useSystemClassLoader=true section in the surefire plugin config still the same issue.
> I will try on linux when I get the time...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-409) test fails (due to bad plexus
isolation?) after upgrading from 2.3 to latest 2.4 SNAPSHOT
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-409.
---------------------------------
Resolution: Incomplete
When I run this test, I find that I can't get it to work at all in Surefire 2.3 (on my Windows XP box); as far as I can tell, useSystemClassLoader was totally broken on Windows in 2.3.
When I run it in 2.4, I reproduce the test failures that you experienced, but I'm 99% sure that this isn't SUREFIRE-347 or any other plexus bleedover bug in Surefire. Surefire now shades its copy of plexus-utils (1.4.9), relocating its package to org.apache.maven.surefire.shaded.org.codehaus.plexus so as to guarantee that it won't conflict with anything else.
When I run the test and look at TEST-org.codehaus.mojo.webstart.JarUnsignMojoTest.xml, I see in the surefire.test.class.path variable that there are two copies of plexus-utils on your classpath: 1.0.2 and also 1.4.8. 1.4.8 comes second on the list.
I'm not entirely certain why your project depends on two copies of plexus-utils, but neither of them are the version of plexus that Surefire uses, so I'm pretty sure this isn't a Surefire problem, but rather a bug in your project.
<property value="C:\Dan\scratch\trash\webstart-maven-plugin\plugin\target\classes;C:\Dan\scratch\trash\webstart-maven-plugin\plugin\target\test-classes;c:\weirdlocalrepo\commons-logging\commons-logging\1.0.4\commons-logging-1.0.4.jar;c:\weirdlocalrepo\plexus\plexus-utils\1.0.2\plexus-utils-1.0.2.jar;c:\weirdlocalrepo\org\apache\maven\wagon\wagon-ssh-common\1.0-beta-2\wagon-ssh-common-1.0-beta-2.jar;c:\weirdlocalrepo\org\codehaus\mojo\keytool-maven-plugin\1.0-beta-2-SNAPSHOT\keytool-maven-plugin-1.0-beta-2-SNAPSHOT.jar;c:\weirdlocalrepo\org\codehaus\mojo\webstart-jarsigner-api\1.0-alpha-2-SNAPSHOT\webstart-jarsigner-api-1.0-alpha-2-SNAPSHOT.jar;c:\weirdlocalrepo\org\codehaus\plexus\plexus-i18n\1.0-beta-6\plexus-i18n-1.0-beta-6.jar;c:\weirdlocalrepo\org\codehaus\plexus\plexus-container-default\1.0-alpha-9-stable-1\plexus-container-default-1.0-alpha-9-stable-1.jar;c:\weirdlocalrepo\classworlds\classworlds\1.1\classworlds-1.1.jar;c:\weirdlocalrepo\org\apache\maven\reporting\maven-reporting-api\2.0.6\maven-reporting-api-2.0.6.jar;c:\weirdlocalrepo\org\apache\maven\wagon\wagon-http-shared\1.0-beta-2\wagon-http-shared-1.0-beta-2.jar;c:\weirdlocalrepo\commons-validator\commons-validator\1.2.0\commons-validator-1.2.0.jar;c:\weirdlocalrepo\org\apache\maven\maven-artifact-manager\2.0.6\maven-artifact-manager-2.0.6.jar;c:\weirdlocalrepo\org\apache\maven\wagon\wagon-provider-api\1.0-beta-2\wagon-provider-api-1.0-beta-2.jar;c:\weirdlocalrepo\org\codehaus\mojo\pack200-jdk15\1.0-alpha-2-SNAPSHOT\pack200-jdk15-1.0-alpha-2-SNAPSHOT.jar;c:\weirdlocalrepo\xmlunit\xmlunit\1.0\xmlunit-1.0.jar;c:\weirdlocalrepo\velocity\velocity-dep\1.4\velocity-dep-1.4.jar;c:\weirdlocalrepo\oro\oro\2.0.7\oro-2.0.7.jar;c:\weirdlocalrepo\org\apache\maven\wagon\wagon-http-lightweight\1.0-beta-2\wagon-http-lightweight-1.0-beta-2.jar;c:\weirdlocalrepo\org\apache\maven\wagon\wagon-file\1.0-beta-2\wagon-file-1.0-beta-2.jar;c:\weirdlocalrepo\org\apache\maven\maven-repository-metadata\2.0.6\maven-repository-metadata-2.0.6.jar;c:\weirdlocalrepo\org\apache\maven\maven-plugin-parameter-documenter\2.0.6\maven-plugin-parameter-documenter-2.0.6.jar;c:\weirdlocalrepo\org\apache\maven\reporting\maven-reporting-impl\2.0.4\maven-reporting-impl-2.0.4.jar;c:\weirdlocalrepo\org\apache\maven\shared\maven-plugin-testing-harness\1.0-beta-1\maven-plugin-testing-harness-1.0-beta-1.jar;c:\weirdlocalrepo\velocity\velocity\1.4\velocity-1.4.jar;c:\weirdlocalrepo\org\apache\maven\doxia\doxia-decoration-model\1.0-alpha-7\doxia-decoration-model-1.0-alpha-7.jar;c:\weirdlocalrepo\org\apache\maven\maven-core\2.0.6\maven-core-2.0.6.jar;c:\weirdlocalrepo\commons-logging\commons-logging-api\1.0.4\commons-logging-api-1.0.4.jar;c:\weirdlocalrepo\org\apache\maven\maven-plugin-api\2.0\maven-plugin-api-2.0.jar;c:\weirdlocalrepo\org\apache\maven\maven-model\2.0.6\maven-model-2.0.6.jar;c:\weirdlocalrepo\junit\junit\3.8.1\junit-3.8.1.jar;c:\weirdlocalrepo\org\apache\maven\maven-archiver\2.2\maven-archiver-2.2.jar;c:\weirdlocalrepo\org\apache\maven\plugins\maven-jar-plugin\2.2-SNAPSHOT\maven-jar-plugin-2.2-SNAPSHOT.jar;c:\weirdlocalrepo\ant\ant\1.6.5\ant-1.6.5.jar;c:\weirdlocalrepo\commons-collections\commons-collections\2.1\commons-collections-2.1.jar;c:\weirdlocalrepo\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;c:\weirdlocalrepo\org\codehaus\plexus\plexus-interactivity-api\1.0-alpha-4\plexus-interactivity-api-1.0-alpha-4.jar;c:\weirdlocalrepo\commons-beanutils\commons-beanutils\1.7.0\commons-beanutils-1.7.0.jar;c:\weirdlocalrepo\org\codehaus\plexus\plexus-utils\1.4.8\plexus-utils-1.4.8.jar;c:\weirdlocalrepo\org\apache\maven\maven-profile\2.0.6\maven-profile-2.0.6.jar;c:\weirdlocalrepo\org\apache\maven\maven-plugin-registry\2.0.6\maven-plugin-registry-2.0.6.jar;c:\weirdlocalrepo\org\apache\maven\maven-project\2.0.6\maven-project-2.0.6.jar;c:\weirdlocalrepo\org\apache\maven\maven-monitor\2.0.6\maven-monitor-2.0.6.jar;c:\weirdlocalrepo\commons-digester\commons-digester\1.6\commons-digester-1.6.jar;c:\weirdlocalrepo\org\codehaus\plexus\plexus-velocity\1.1.2\plexus-velocity-1.1.2.jar;c:\weirdlocalrepo\org\apache\maven\maven-settings\2.0.6\maven-settings-2.0.6.jar;c:\weirdlocalrepo\commons-cli\commons-cli\1.0\commons-cli-1.0.jar;c:\weirdlocalrepo\org\apache\maven\doxia\doxia-site-renderer\1.0-alpha-7\doxia-site-renderer-1.0-alpha-7.jar;c:\weirdlocalrepo\com\jcraft\jsch\0.1.27\jsch-0.1.27.jar;c:\weirdlocalrepo\org\apache\maven\wagon\wagon-ssh\1.0-beta-2\wagon-ssh-1.0-beta-2.jar;c:\weirdlocalrepo\org\apache\maven\maven-embedder\2.0.4\maven-embedder-2.0.4.jar;c:\weirdlocalrepo\org\apache\maven\wagon\wagon-ssh-external\1.0-beta-2\wagon-ssh-external-1.0-beta-2.jar;c:\weirdlocalrepo\org\apache\maven\maven-error-diagnostics\2.0.6\maven-error-diagnostics-2.0.6.jar;c:\weirdlocalrepo\org\apache\maven\doxia\doxia-core\1.0-alpha-7\doxia-core-1.0-alpha-7.jar;c:\weirdlocalrepo\jtidy\jtidy\4aug2000r7-dev\jtidy-4aug2000r7-dev.jar;c:\weirdlocalrepo\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;c:\weirdlocalrepo\org\apache\maven\maven-artifact\2.0.6\maven-artifact-2.0.6.jar;c:\weirdlocalrepo\org\apache\maven\maven-plugin-descriptor\2.0.6\maven-plugin-descriptor-2.0.6.jar;c:\weirdlocalrepo\xml-apis\xml-apis\1.0.b2\xml-apis-1.0.b2.jar;c:\weirdlocalrepo\org\codehaus\mojo\webstart-maven-plugin\pack200-anttasks\1.0\pack200-anttasks-1.0.jar;c:\weirdlocalrepo\org\apache\maven\doxia\doxia-sink-api\1.0-alpha-7\doxia-sink-api-1.0-alpha-7.jar;" name="surefire.test.class.path"/>
> test fails (due to bad plexus isolation?) after upgrading from 2.3 to latest 2.4 SNAPSHOT
> -----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-409
> URL: http://jira.codehaus.org/browse/SUREFIRE-409
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
> Affects Versions: 2.4
> Reporter: Jerome Lacoste
> Attachments: mvn_2.3_with_systemClassLoader.log, mvn_2.3_without_systemClassLoader.log, mvn_2.4_with_systemClassLoader.log, mvn_2.4_without_systemClassLoader.log, pom.diff, pom_2.4_with_systemClassLoader.xml, svn_info.txt, test-failure-2.4.txt
>
>
> If I upgrade surefire in the Mowebstart plugin project, I get test failures:
> Caused by: java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
> at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63
> )
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at java.lang.Class.newInstance0(Class.java:350)
> at java.lang.Class.newInstance(Class.java:303)
> at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
> ... 43 more
> It sounds like SUREFIRE-347.
> Note that my build was broke on Windows. I usually build on Linux so I didn't notice the problem. Maybe it has been there for a while. I also attach here the error I was getting when building with 2.3 on Windows. So I removed the useSystemClassLoader config (that was introduced to work-around SUREFIRE-347 w/ surefire 2.3...) in my POM and the build passed again on Windows (didn't try on Linux).
> Then I upgraded to surefire plugin 2.4 and started to see failures in test. I added the useSystemClassLoader=true section in the surefire plugin config still the same issue.
> I will try on linux when I get the time...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira