[jira] Subscription: open gump issues
Issue Subscription Filter: open gump issues (35 issues) Subscriber: g...@jakarta.apache.org Key Summary GUMP-160Mail message differs significantly from log and does not include the Error ! https://issues.apache.org/jira/browse/GUMP-160 GUMP-159The site needs a big review. https://issues.apache.org/jira/browse/GUMP-159 GUMP-158Manage API changes in dependencies better https://issues.apache.org/jira/browse/GUMP-158 GUMP-155Gump complains that the HiveMind build failed, when it does not https://issues.apache.org/jira/browse/GUMP-155 GUMP-153Gump Metadata: links no longer work https://issues.apache.org/jira/browse/GUMP-153 GUMP-152Made some updates on the Gump3 Presentation https://issues.apache.org/jira/browse/GUMP-152 GUMP-151path separator and depend = maven bugs https://issues.apache.org/jira/browse/GUMP-151 GUMP-150Webapplication to present the data generated by Gump3 https://issues.apache.org/jira/browse/GUMP-150 GUMP-149allow gump to bootstrap maven https://issues.apache.org/jira/browse/GUMP-149 GUMP-148Clean up entire codebase and add documentation https://issues.apache.org/jira/browse/GUMP-148 GUMP-147Complain if a project does not provide all the outputs it states https://issues.apache.org/jira/browse/GUMP-147 GUMP-145Apache HTTPD config snippet for Dynagump https://issues.apache.org/jira/browse/GUMP-145 GUMP-144Design and document sensible URL scheme for gump data https://issues.apache.org/jira/browse/GUMP-144 GUMP-143Create init script for Dynagump https://issues.apache.org/jira/browse/GUMP-143 GUMP-142Add some documentation on how to add functionality to Dynagump https://issues.apache.org/jira/browse/GUMP-142 GUMP-141Automate navigation generation for Dynagump https://issues.apache.org/jira/browse/GUMP-141 GUMP-140Gump crashes when listing https://issues.apache.org/jira/browse/GUMP-140 GUMP-134Restore Kaffe and JDK1.5 (and Test) workspaces. https://issues.apache.org/jira/browse/GUMP-134 GUMP-131Build fails with build timed out https://issues.apache.org/jira/browse/GUMP-131 GUMP-128Support federation of gump instances https://issues.apache.org/jira/browse/GUMP-128 GUMP-127Support for local plugins https://issues.apache.org/jira/browse/GUMP-127 GUMP-126Simple scheduling support using a gump run queue https://issues.apache.org/jira/browse/GUMP-126 GUMP-125Flexible way to configure gump in modern unix-like fashion https://issues.apache.org/jira/browse/GUMP-125 GUMP-116Promote using html in description/ fields https://issues.apache.org/jira/browse/GUMP-116 GUMP-115Make gump result pages link to LXR-generated content https://issues.apache.org/jira/browse/GUMP-115 GUMP-114Run LXR and/or javasrc on brutus https://issues.apache.org/jira/browse/GUMP-114 GUMP-113Set up dynagump installation and proxypass from main gump site https://issues.apache.org/jira/browse/GUMP-113 GUMP-112Document 0.5 version of the Gump Object Model https://issues.apache.org/jira/browse/GUMP-112 GUMP-89 support junitreport https://issues.apache.org/jira/browse/GUMP-89 GUMP-72 Requirement for multiple license file declarations. https://issues.apache.org/jira/browse/GUMP-72 GUMP-62 Module docs needs to point to fully qualified viewcvs https://issues.apache.org/jira/browse/GUMP-62 GUMP-40 non-committers can modify (some) descriptors https://issues.apache.org/jira/browse/GUMP-40 GUMP-36 Generate source diff report on build failure https://issues.apache.org/jira/browse/GUMP-36 GUMP-30 put installed packages under version control https://issues.apache.org/jira/browse/GUMP-30 GUMP-29 new user howto https://issues.apache.org/jira/browse/GUMP-29 You may edit this subscription at: https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=10180filterId=10780 - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: skipTests vs maven.test.skip.exec
On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig bode...@apache.org wrote: Hi, some time back we had a discussion that skipTest was the preferred property to use when we want to tell mvn not to run tests - well, it doesn't work, at least not for Cocoon 2.2.x. My theory is that those properties are interpreted by the surefire plugin rather than mvn itself. Yes, they are plugin parameters: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html And from the docs the skipTests parameter was added in version 2.4 of the surefire plugin Unlike the version of mvn we cannot influence the version of plugins used by a project, so whether skipTests works or not depends on the project. Yes and cocoon is using version 2.3 of the surefire plugin (see pluginManagement section of the pom): http://svn.apache.org/repos/asf/cocoon/trunk/parent/pom.xml skipTests was introduced to replace the more verbose maven.test.skip=true - you could use that instead though. Niall Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: skipTests vs maven.test.skip.exec
On 2010-09-06, Niall Pemberton wrote: On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig bode...@apache.org wrote: Hi, some time back we had a discussion that skipTest was the preferred property to use when we want to tell mvn not to run tests - well, it doesn't work, at least not for Cocoon 2.2.x. My theory is that those properties are interpreted by the surefire plugin rather than mvn itself. Yes, they are plugin parameters: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html Thank you for the confirmation. And from the docs the skipTests parameter was added in version 2.4 of the surefire plugin [...] and cocoon is using version 2.3 of the surefire plugin (see pluginManagement section of the pom): skipTests was introduced to replace the more verbose maven.test.skip=true - you could use that instead though. Is there a difference between maven.test.skip and maven.test.skip.exec (which we use now)? I see there is a skip property in addition to the skipTests property - the former even avoids compilation of the tests, so I gues this is the difference here as well. As much as I would have loved consistency it seems we are best off with using skipTests when possible and fall back to maven.test.skip.exec. Coming to think of it, skip and maven.test.skip may help for builds like james-jsieve which requires JUnit 3.8 to compile because they still have one of those AllTests classes invoking swingui.TestRunner we used to write in 2000. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: skipTests vs maven.test.skip.exec
On Mon, Sep 6, 2010 at 12:16 PM, Stefan Bodewig bode...@apache.org wrote: On 2010-09-06, Niall Pemberton wrote: On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig bode...@apache.org wrote: Hi, some time back we had a discussion that skipTest was the preferred property to use when we want to tell mvn not to run tests - well, it doesn't work, at least not for Cocoon 2.2.x. My theory is that those properties are interpreted by the surefire plugin rather than mvn itself. Yes, they are plugin parameters: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html Thank you for the confirmation. And from the docs the skipTests parameter was added in version 2.4 of the surefire plugin [...] and cocoon is using version 2.3 of the surefire plugin (see pluginManagement section of the pom): skipTests was introduced to replace the more verbose maven.test.skip=true - you could use that instead though. Is there a difference between maven.test.skip and maven.test.skip.exec (which we use now)? I see there is a skip property in addition to the skipTests property - the former even avoids compilation of the tests, so I gues this is the difference here as well. Yes, the skipTests and maven.test.skip.exec=true are the same - the tests get compiled, but not executed. The maven.test.skip=true doesn't compile or execute the tests. Niall As much as I would have loved consistency it seems we are best off with using skipTests when possible and fall back to maven.test.skip.exec. Coming to think of it, skip and maven.test.skip may help for builds like james-jsieve which requires JUnit 3.8 to compile because they still have one of those AllTests classes invoking swingui.TestRunner we used to write in 2000. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: skipTests vs maven.test.skip.exec
Niall Pemberton wrote: On Mon, Sep 6, 2010 at 12:16 PM, Stefan Bodewig bode...@apache.org wrote: On 2010-09-06, Niall Pemberton wrote: On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig bode...@apache.org wrote: Hi, some time back we had a discussion that skipTest was the preferred property to use when we want to tell mvn not to run tests - well, it doesn't work, at least not for Cocoon 2.2.x. My theory is that those properties are interpreted by the surefire plugin rather than mvn itself. Yes, they are plugin parameters: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html Thank you for the confirmation. And from the docs the skipTests parameter was added in version 2.4 of the surefire plugin [...] and cocoon is using version 2.3 of the surefire plugin (see pluginManagement section of the pom): skipTests was introduced to replace the more verbose maven.test.skip=true - you could use that instead though. Is there a difference between maven.test.skip and maven.test.skip.exec (which we use now)? I see there is a skip property in addition to the skipTests property - the former even avoids compilation of the tests, so I gues this is the difference here as well. Yes, the skipTests and maven.test.skip.exec=true are the same - the tests get compiled, but not executed. The maven.test.skip=true doesn't compile or execute the tests. And it will therefore not build attached tests.jars which may result depending artifacts to fail ... - Jörg - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: skipTests vs maven.test.skip.exec
On 2010-09-06, Jörg Schaible wrote: Niall Pemberton wrote: Yes, the skipTests and maven.test.skip.exec=true are the same - the tests get compiled, but not executed. The maven.test.skip=true doesn't compile or execute the tests. And it will therefore not build attached tests.jars which may result depending artifacts to fail ... Understood. In the case where the tests don't compile this doesn't make any difference for those dependening artifacts - but it will allow projects that don't require the tests jar to build. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
