[jira] (SUREFIRE-812) log4j classloader problem in 2.11 that is not there in 2.10
[ https://jira.codehaus.org/browse/SUREFIRE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286725#comment-286725 ] Kristian Rosenvold commented on SUREFIRE-812: - Can you also check if there's a stack trace of any value if you run with mvn -e. Additionally, I assume this "works" if you run forkMode=once ? > log4j classloader problem in 2.11 that is not there in 2.10 > --- > > Key: SUREFIRE-812 > URL: https://jira.codehaus.org/browse/SUREFIRE-812 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.11 >Reporter: Gregor N. Purdy, Sr. > > Unit test does not fail with 2.10 but does fail with 2.11 > Output from failing unit test > log4j:ERROR A "org.apache.log4j.xml.DOMConfigurator" object is not assignable > to a "org.apache.log4j.spi.Configurator" variable. > log4j:ERROR The class "org.apache.log4j.spi.Configurator" was loaded by > log4j:ERROR [sun.misc.Launcher$AppClassLoader@37b90b39] whereas object of > type > log4j:ERROR "org.apache.log4j.xml.DOMConfigurator" was loaded by > [org.apache.maven.surefire.booter.IsolatedClassLoader@7bd63e39]. > log4j:ERROR Could not instantiate configurator > [org.apache.log4j.xml.DOMConfigurator]. > $ mvn -version > Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800) > Plugin config > > maven-surefire-plugin > 2.11 > > > default-test > test > > test > > > -Xmx2048m -Xms1024m > true > false > always > > 600 > true > > true > > > > > > -Xmx2048m -Xms1024m > true > false > always > 600 > true > > true > > > > reporting plugin configuration > > maven-surefire-report-plugin > 2.11 > > -Xmx2048m -Xms1024m > true > false > always > 600 > true > > true > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINVOKER-122) Import information into groovy scripts of the running Maven environment
Karl Heinz Marbaise created MINVOKER-122: Summary: Import information into groovy scripts of the running Maven environment Key: MINVOKER-122 URL: https://jira.codehaus.org/browse/MINVOKER-122 Project: Maven 2.x Invoker Plugin Issue Type: New Feature Affects Versions: 1.5 Reporter: Karl Heinz Marbaise Priority: Minor During the execution of a postbuild.groovy script i'm checking the contents of the build.log output (output of plugins etc.). The problem is that based on the differences between MVN 2.2.1 and MVN 3.0.? the output looks different. But inside a verify.groovy i don't know under which version of Maven the integration-tests has been run...so it's not simple to make a difference here...It might be a good idea to get this information inside the groovy script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINVOKER-122) Import information into groovy scripts of the running Maven environment
[ https://jira.codehaus.org/browse/MINVOKER-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286757#comment-286757 ] Robert Scholte commented on MINVOKER-122: - What you can do is specifying for which versions the test is by using [selector-conditions|http://maven.apache.org/plugins/maven-invoker-plugin/examples/selector-conditions.html]. But exposing this kind of information sounds reasonable to me. > Import information into groovy scripts of the running Maven environment > > > Key: MINVOKER-122 > URL: https://jira.codehaus.org/browse/MINVOKER-122 > Project: Maven 2.x Invoker Plugin > Issue Type: New Feature >Affects Versions: 1.5 >Reporter: Karl Heinz Marbaise >Priority: Minor > > During the execution of a postbuild.groovy script i'm checking the contents > of the build.log output (output of plugins etc.). The problem is that based > on the differences between MVN 2.2.1 and MVN 3.0.? the output looks > different. But inside a verify.groovy i don't know under which version of > Maven the integration-tests has been run...so it's not simple to make a > difference here...It might be a good idea to get this information inside the > groovy script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
