Re: Tentative release planning for 3.1.x
On Tue, Nov 13, 2012 at 10:02 AM, Jesse Glick jgl...@cloudbees.com wrote: On 11/12/2012 02:00 PM, Dennis Lundberg wrote: I had a quick look at the Windows ITs and the problem seems to be that Maven/Jenkins is unable to delete files. This looks like a Windows path length issue, because the path it complain about is 264 chars long. JENKINS-15418 [1] was fixed in 1.489, FYI. [1] https://issues.jenkins-ci.org/**browse/JENKINS-15418https://issues.jenkins-ci.org/browse/JENKINS-15418 However, JENKINS-15367 [1] is still not fixed, I think the reason Jenkins is still 1.480 at Apache. (There is a pull request [2] to fix it, just needs someone with enough karma to apply it) [1] https://issues.jenkins-ci.org/browse/JENKINS-15367 [2] https://github.com/jenkinsci/jenkins/pull/609 -- Larry
Re: Surefire (with JUnit and TestNG) with the Release plugin and failures/errors in JUnit tests
Created: http://jira.codehaus.org/browse/SUREFIRE-926 As mentioned in the bug, I'm trying to create integration tests to exhibit this behavior, but having a few problems. Also, is there an easy way to run just one, or two integration tests by hand? I tried -Dit.test=MyNewTest but it didn't run anything... Thanks -- Larry On Thu, Nov 8, 2012 at 12:11 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: This seems to be a bug; would you mind filing an issue http://jira.codehaus.org/browse/SUREFIRE ? Kristian 2012/11/8 Larry Shatzer, Jr. lar...@gmail.com: I'm using a fairly recent feature of Surefire where you can specify multiple providers ( http://maven.apache.org/plugins/maven-surefire-plugin/examples/providers.html ) I'm using both TestNG and Junit. Here is the secion of the pom in question: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.12.4/version dependencies dependency groupIdorg.apache.maven.surefire/groupId artifactIdsurefire-testng/artifactId version2.12.4/version /dependency dependency groupIdorg.apache.maven.surefire/groupId artifactIdsurefire-junit4/artifactId version2.12.4/version /dependency /dependencies /plugin When I go to run release:prepare where I have a JUnit test either error or fail, it will continue like everything is fine, and allow the release with test failures or errors! Here is the output from running release:prepare http://pastebin.com/Z94egP3E When I then have a TestNG failure, I get what I expect (a failure): http://pastebin.com/yJufszdN I'm not sure if this is a bug with the Release plugin, Surefire, or can be helped with any extra configuration of either the Release plugin or Surefire... Thanks! -- Larry - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Surefire (with JUnit and TestNG) with the Release plugin and failures/errors in JUnit tests
It was named ending in IT, but the only way I got it to run was to run all of them with a mvn install. I wanted to just run one by hand. -- Larry On Thu, Nov 8, 2012 at 2:57 PM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: Test name must probably end with IT Kristian Den 8. nov. 2012 kl. 22:51 skrev Larry Shatzer, Jr. lar...@gmail.com: Created: http://jira.codehaus.org/browse/SUREFIRE-926 As mentioned in the bug, I'm trying to create integration tests to exhibit this behavior, but having a few problems. Also, is there an easy way to run just one, or two integration tests by hand? I tried -Dit.test=MyNewTest but it didn't run anything... Thanks -- Larry On Thu, Nov 8, 2012 at 12:11 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: This seems to be a bug; would you mind filing an issue http://jira.codehaus.org/browse/SUREFIRE ? Kristian 2012/11/8 Larry Shatzer, Jr. lar...@gmail.com: I'm using a fairly recent feature of Surefire where you can specify multiple providers ( http://maven.apache.org/plugins/maven-surefire-plugin/examples/providers.html ) I'm using both TestNG and Junit. Here is the secion of the pom in question: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.12.4/version dependencies dependency groupIdorg.apache.maven.surefire/groupId artifactIdsurefire-testng/artifactId version2.12.4/version /dependency dependency groupIdorg.apache.maven.surefire/groupId artifactIdsurefire-junit4/artifactId version2.12.4/version /dependency /dependencies /plugin When I go to run release:prepare where I have a JUnit test either error or fail, it will continue like everything is fine, and allow the release with test failures or errors! Here is the output from running release:prepare http://pastebin.com/Z94egP3E When I then have a TestNG failure, I get what I expect (a failure): http://pastebin.com/yJufszdN I'm not sure if this is a bug with the Release plugin, Surefire, or can be helped with any extra configuration of either the Release plugin or Surefire... Thanks! -- Larry - 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
Surefire (with JUnit and TestNG) with the Release plugin and failures/errors in JUnit tests
I'm using a fairly recent feature of Surefire where you can specify multiple providers ( http://maven.apache.org/plugins/maven-surefire-plugin/examples/providers.html ) I'm using both TestNG and Junit. Here is the secion of the pom in question: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.12.4/version dependencies dependency groupIdorg.apache.maven.surefire/groupId artifactIdsurefire-testng/artifactId version2.12.4/version /dependency dependency groupIdorg.apache.maven.surefire/groupId artifactIdsurefire-junit4/artifactId version2.12.4/version /dependency /dependencies /plugin When I go to run release:prepare where I have a JUnit test either error or fail, it will continue like everything is fine, and allow the release with test failures or errors! Here is the output from running release:prepare http://pastebin.com/Z94egP3E When I then have a TestNG failure, I get what I expect (a failure): http://pastebin.com/yJufszdN I'm not sure if this is a bug with the Release plugin, Surefire, or can be helped with any extra configuration of either the Release plugin or Surefire... Thanks! -- Larry
Re: Maven 2/3 and Cobetura plugin with both TestNG and JUnit tests (with Surefire plugin configuration)
On Mon, Aug 1, 2011 at 9:56 AM, Larry Shatzer, Jr. lar...@gmail.com wrote: I want to run with both JUnit and TestNG. By removing JUnit (and the tests that JUnit run), it ran just fine, as do the inverse, just JUnit and no TestNG. It is the combination of both of them. To help, instead of having gists, I created a github project: https://github.com/larrys/CoverageBug which you can fetch and run locally and see exactly what I'm talking about and be able to possibly tweak or debug any issues that I lack the knowledge to do. I removed cobertura out of the picture and ran emma instead, and produced similar results. --- T E S T S --- Running com.company.JUnitTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec Running com.company.TestNGTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 If I just run the test lifecycle, it will execute the tests. Somehow a plugin that calls the test lifecycle in Maven 3 when both TestNG and JUnit are configured to run have issues. I also tried the latest surefire plugin snapshot build (built locally), and it has no effect. So I started going through various versions of Surefire. 2.7.1, 2.7, 2.6, 2.5, 2.4.3, 2.4.2, and 2.4.1 had similar output as below (ran test phase 3 times, but still did not execute tests!): --- T E S T S --- Running com.company.JUnitTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec Running com.company.TestNGTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-surefire-plugin:2.7.1:test (test-junit) @ coveragebug --- [INFO] Surefire report directory: C:\development\coverage-bug\coveragebug\target\surefire-reports --- T E S T S --- Running com.company.JUnitTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec Running com.company.TestNGTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-surefire-plugin:2.7.1:test (test-testng) @ coveragebug --- [INFO] Surefire report directory: C:\development\coverage-bug\coveragebug\target\surefire-reports --- T E S T S --- Running com.company.JUnitTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running com.company.TestNGTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 When I get to 2.3.1: --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-surefire-plugin:2.3.1:test (test-junit) @ coveragebug --- [INFO] Surefire report directory: C:\development\coverage-bug\coveragebug\target\surefire-reports --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-surefire-plugin:2.3.1:test (test-testng) @ coveragebug --- [INFO] Surefire report directory: C:\development\coverage-bug\coveragebug\target\surefire-reports --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 It does it three times, but does not actually show the test classes it is supposed to try to be running. 2.3 has issues with TestNG: --- T E S T S --- org.apache.maven.surefire.booter.SurefireExecutionException: org.testng.xml.XmlSuite.setParallel(Z)V; nested exception is java .lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:123) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
Re: Maven 2/3 and Cobetura plugin with both TestNG and JUnit tests (with Surefire plugin configuration)
One last update. If I remove the execution sections that tell
Surefire to run both TestNG and Junit, and put dependencies on the
Surefire Plugin like so:
dependencies
dependency
groupIdorg.apache.maven.surefire/groupId
artifactIdsurefire-junit4/artifactId
version${surefire.version}/version
/dependency
dependency
groupIdorg.apache.maven.surefire/groupId
artifactIdsurefire-testng/artifactId
version${surefire.version}/version
/dependency
/dependencies
I get the results I expect.
---
T E S T S
---
Running com.company.JUnitTest
JUnit
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.037 sec
Flushing results...
Flushing results done
Cobertura: Loaded information on 1 classes.
Cobertura: Saved information on 1 classes.
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
---
T E S T S
---
Running TestSuite
TestNG
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.311 sec
Flushing results...
Flushing results done
Cobertura: Loaded information on 1 classes.
Cobertura: Saved information on 1 classes.
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 2/3 and Cobetura plugin with both TestNG and JUnit tests (with Surefire plugin configuration)
On Thu, Jul 28, 2011 at 6:04 AM, Martin Gainty mgai...@hotmail.com wrote:
Larry-
try loading both dependencies in your local repository and running offline
with mvn -o (at least your dependencies will be found)
did you check cobertura for errors?
mvn -e -X cobertura:cobertura -Dquiet=true
I did not see any obvious errors.
take junit out of the mix and run testng as solo Test dependency then check
output folders
${project.reporting.outputDirectory}/cobertura.
if these tests fail you may have found a bug in which cause you need to file
a JIRA at
http://jira.codehaus.org/browse/MCOBERTURA
I want to run with both JUnit and TestNG. By removing JUnit (and the
tests that JUnit run), it ran just fine, as do the inverse, just JUnit
and no TestNG. It is the combination of both of them.
To help, instead of having gists, I created a github project:
https://github.com/larrys/CoverageBug which you can fetch and run
locally and see exactly what I'm talking about and be able to possibly
tweak or debug any issues that I lack the knowledge to do.
Thanks
-- Larry
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Set specific plugin versions for a project - issue in plugin-registry.xml/maven-metada-local.xml
On Mon, Jul 25, 2011 at 9:30 AM, Kasun Gajasinghe kasu...@gmail.com wrote: On Mon, Jul 25, 2011 at 5:34 PM, Damian Bradicich dbradic...@sonatype.com wrote: err...pluginManagement section even ;) Damian On Mon, Jul 25, 2011 at 8:02 AM, Damian Bradicich dbradic...@sonatype.comwrote: Why not define the pluginDependency section in a parent pom, then each of your projects uses this as a parent, and pulls in all the plugin dep versions defined in it (or overrides in project pom if necessary). Seems that would be simplest solution Since these projects are unrelated, they can't be glued together via a parent pom. I don't see why not. Consider the following example: http://img.skitch.com/20110727-b3j3j8fk2rg4s2h9exm225skyd.png You just need to have a hierarchy of parent poms. Sure, if you update the top Corporate Super-Pom, you will then need to update the other parent poms that depend on that pom, but this way you can share only the most common stuff, such as plugin versions and generic configurations in the corporate super pom, and then in each of the other parent poms, you get more specific. -- Larry - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven 2/3 and Cobetura plugin with both TestNG and JUnit tests (with Surefire plugin configuration)
I did send this to the users list, but got no response in over a week. I know dev lists are not a magical escalation path, but this might be a better venue for this email. I have an example project at https://gist.github.com/1090223 This project has both a JUnit test and a TestNG test. Following some instructions online to get surefire be able to run both I added lines 19-45 in the pom. This works fine when running mvn test, except it runs the TestNG tests twice. I can fix that by commenting out lines 34-43. Now when I run mvn cobertura:cobertura, this is where things get weird. In Maven 2.2.1, it runs both TestNG and JUnit just fine, and produces the correct coverage. Now in Maven 3.0.3 it just runs the JUnit tests. (With lines 34-43 still commented out). When I bring those back, this is the output: --- T E S T S --- Running com.company.JUnitTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec Running com.company.TestNGTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 So it appears to try to run both tests, but fails to actually run any tests, and gets 0% coverage. It appears there is something odd between Maven 2.2.1 and Maven 3.0.3 when the cobertura plugin runs, and its reading of the Surefire plugin configuration. Ideally I would only use JUnit or TestNG, and this would not be a problem. However, we are using TestNG exclusively, and wanted to introduce a tool that currently only is executed as a JUnit test (Spock). I wanted to avoid changing all our tests from TestNG to JUnit unless absolutely necessary. It appears to be a regression from Maven 2.2.1 to Maven 3.0.3, unless it was a bug in Maven 2 that was fixed. -- Larry - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Excecuting maven commands in crontab
Remember, that cron jobs execute in a limited environment. You should check your log for any clues. Also, this is more of a maven users question, not about the development of maven itself. -- Larry On Thu, Aug 12, 2010 at 9:49 AM, anilreddy76 anilredd...@gmail.com wrote: I've one shellscript excute.sh which has the maven commands like this #!/bin/bash mvn clean package mvn exec:java -Dexec.mainClass=com.eportfolio.dart.business.EPenCreateICFCDFFile and I'm calling the above script in crontab for every 1 min like this,but it's not executing. */1 * * * * /hosting/pem_rd/DART/DART_ePortfolio_Server/execute.sh /tmp/dart/icfcdf.log once I just run excute.sh from command line without cron it is fine. Could any body please advise where I'm going wrong? Thanks, Kumar -- View this message in context: http://maven.40175.n5.nabble.com/Excecuting-maven-commands-in-crontab-tp2473371p2473371.html Sent from the Maven Developers mailing list archive at Nabble.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: [VOTE] Release Maven Shade Plugin 1.2.2
I attached a patch (with a test too!) for MSHADE-52, and would love that to get included, or at the very least, looked at. On Sun, Nov 22, 2009 at 5:43 AM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, We solved 7 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540version=15525 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11540status=1 Staging repo: https://repository.apache.org/content/repositories/maven-017/ Staging site (sync pending): http://maven.apache.org/plugins/maven-shade-plugin-1.2.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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
