[CANCELLED] Re: [VOTE] Release Maven Dependency Tree 2.0 + Maven Project Info Reports Plugin 2.5 + Maven Dependency Plugin 2.5
grrr :( I'll need to work on it tonight I asked for tests a week ago just to avoid such late reports :/ Please continue to report problems on what is now a RC so the next vote won't show such problems Regards, Hervé Le mardi 31 juillet 2012 10:02:42 Joseph Walton a écrit : > I've filed MDEP-361 and MDEP-362 against the new dependency:tree > implementation. It'd be nice to see them resolved before a final release. > > On 31/07/12 07:34, Christian Schulte wrote: > > -1 (unbinding) > > > > The dependency plugin still contains 'System.out.println' statements. > > > > Am 07/30/12 22:50, schrieb Hervé BOUTEMY: > >> Hi, > >> > >> We solved 2 + 7 + 6 issues: > >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleNam > >> e=Html&version=14540 > >> > >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142&styleNam > >> e=Html&version=17369 > >> > >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleNam > >> e=Html&version=18077 > >> > >> > >> There are still "a couple" of issues left in JIRA: > >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&; > >> status=1 > >> > >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11142&; > >> status=1 > >> > >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11214&; > >> status=1 > >> > >> > >> Staging repo: > >> https://repository.apache.org/content/repositories/maven-098/ > >> https://repository.apache.org/content/repositories/maven-098/org/apache/m > >> aven/shared/maven- > >> > >> dependency-tree/2.0/maven-dependency-tree-2.0-source-release.zip > >> https://repository.apache.org/content/repositories/maven-098/org/apache/m > >> aven/plugins/maven- > >> > >> project-info-reports-plugin/2.5/maven-project-info-reports-plugin-2.5-sou > >> rce- > >> > >> release.zip > >> https://repository.apache.org/content/repositories/maven-098/org/apache/m > >> aven/plugins/maven- > >> > >> dependency-plugin/2.5/maven-dependency-plugin-2.5-source-release.zip > >> > >> Staging sites: > >> http://maven.apache.org/shared/maven-dependency-tree-2.0/ > >> http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.5/ > >> http://maven.apache.org/plugins/maven-dependency-plugin-2.5/ > >> > >> 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 > > > > - > > 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
Re: [VOTE] Release Maven Dependency Tree 2.0 + Maven Project Info Reports Plugin 2.5 + Maven Dependency Plugin 2.5
please open a Jira issue with traces of the problem Regards, Hervé Le lundi 30 juillet 2012 23:34:29 Christian Schulte a écrit : > -1 (unbinding) > > The dependency plugin still contains 'System.out.println' statements. > > Am 07/30/12 22:50, schrieb Hervé BOUTEMY: > > Hi, > > > > We solved 2 + 7 + 6 issues: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName > > =Html&version=14540 > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142&styleNam > > e=Html&version=17369 > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleNam > > e=Html&version=18077 > > > > There are still "a couple" of issues left in JIRA: > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&s > > tatus=1 > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11142&; > > status=1 > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11214&; > > status=1 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-098/ > > https://repository.apache.org/content/repositories/maven-098/org/apache/ma > > ven/shared/maven- > > dependency-tree/2.0/maven-dependency-tree-2.0-source-release.zip > > https://repository.apache.org/content/repositories/maven-098/org/apache/ma > > ven/plugins/maven- > > project-info-reports-plugin/2.5/maven-project-info-reports-plugin-2.5-sou > > rce- release.zip > > https://repository.apache.org/content/repositories/maven-098/org/apache/ma > > ven/plugins/maven- > > dependency-plugin/2.5/maven-dependency-plugin-2.5-source-release.zip > > > > Staging sites: > > http://maven.apache.org/shared/maven-dependency-tree-2.0/ > > http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.5/ > > http://maven.apache.org/plugins/maven-dependency-plugin-2.5/ > > > > 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 > > - > 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 Dependency Tree 2.0 + Maven Project Info Reports Plugin 2.5 + Maven Dependency Plugin 2.5
I've filed MDEP-361 and MDEP-362 against the new dependency:tree implementation. It'd be nice to see them resolved before a final release. On 31/07/12 07:34, Christian Schulte wrote: -1 (unbinding) The dependency plugin still contains 'System.out.println' statements. Am 07/30/12 22:50, schrieb Hervé BOUTEMY: Hi, We solved 2 + 7 + 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14540 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142&styleName=Html&version=17369 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleName=Html&version=18077 There are still "a couple" of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11142&status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11214&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-098/ https://repository.apache.org/content/repositories/maven-098/org/apache/maven/shared/maven- dependency-tree/2.0/maven-dependency-tree-2.0-source-release.zip https://repository.apache.org/content/repositories/maven-098/org/apache/maven/plugins/maven- project-info-reports-plugin/2.5/maven-project-info-reports-plugin-2.5-source- release.zip https://repository.apache.org/content/repositories/maven-098/org/apache/maven/plugins/maven- dependency-plugin/2.5/maven-dependency-plugin-2.5-source-release.zip Staging sites: http://maven.apache.org/shared/maven-dependency-tree-2.0/ http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.5/ http://maven.apache.org/plugins/maven-dependency-plugin-2.5/ 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 - 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 Dependency Tree 2.0 + Maven Project Info Reports Plugin 2.5 + Maven Dependency Plugin 2.5
-1 (unbinding) The dependency plugin still contains 'System.out.println' statements. Am 07/30/12 22:50, schrieb Hervé BOUTEMY: Hi, We solved 2 + 7 + 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14540 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142&styleName=Html&version=17369 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleName=Html&version=18077 There are still "a couple" of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11142&status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11214&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-098/ https://repository.apache.org/content/repositories/maven-098/org/apache/maven/shared/maven- dependency-tree/2.0/maven-dependency-tree-2.0-source-release.zip https://repository.apache.org/content/repositories/maven-098/org/apache/maven/plugins/maven- project-info-reports-plugin/2.5/maven-project-info-reports-plugin-2.5-source- release.zip https://repository.apache.org/content/repositories/maven-098/org/apache/maven/plugins/maven- dependency-plugin/2.5/maven-dependency-plugin-2.5-source-release.zip Staging sites: http://maven.apache.org/shared/maven-dependency-tree-2.0/ http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.5/ http://maven.apache.org/plugins/maven-dependency-plugin-2.5/ 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire Plugin version 2.12.1
+1 Hervé Le dimanche 29 juillet 2012 22:45:34 Kristian Rosenvold a écrit : > Hi, > > This is a bugfix release. > > We solved a few issues: > > Bug > > [SUREFIRE-659] - Maven PDF plugin:showSuccess=false creates empty > table causing error > [SUREFIRE-825] - NPE in JUnit4TestChecker if > org.junit.runner.RunWith class can't be loaded by testClassloader > [SUREFIRE-827] - Surefire 2.12 cannot run a single test, > regression from 2.11 > [SUREFIRE-828] - testng test need a excludedGroups element to not fail > [SUREFIRE-832] - JUnit categories only work when junit47 provider > is explicitly set > [SUREFIRE-836] - regression with surefire 2.12 plugin and > SecurityManager [SUREFIRE-844] - "test" parameter no longer working with > JUnit in 2.12 (worked in 2.9 - 2.11) > [SUREFIRE-847] - surefire cannot run single testng test > [SUREFIRE-858] - Running a single unit test in Windows > [SUREFIRE-865] - surefire 2.12 with parallel=methods does not > execute junit 4.7+ tests in parallel > [SUREFIRE-869] - Parallel test execution on class level runs not > all tests but some twice > [SUREFIRE-871] - Output of forked tests with non-zero exit code not > retained [SUREFIRE-877] - Surefire doesn't support "mixed" TestNG 6.5.x > config parameter > [SUREFIRE-879] - maven-surefire-report-plugin fails some times > with ConcurrentModificationException when running parallel TestNG > [SUREFIRE-880] - ObjectFactory no longer works with TestNG 6.5.2 > [SUREFIRE-883] - Cannot run tests in parallel > > Improvement > > [SUREFIRE-745] - -Dtest supports multiple test classes but not > multiple test methods > [SUREFIRE-876] - surefire-junit47 does not work in an OSGi > classloader environment > [SUREFIRE-881] - use plugins annotations > [SUREFIRE-889] - JUnit | supprot inheritance of test's categories/groups > > We unresolved 1 issue; which had to be reverted because it was the > root cause of several of the above issues: > > https://jira.codehaus.org/browse/SUREFIRE-800 > > > There are still lots of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jq > lQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+D > ESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-096/ > > Staging site: (Sync pending) > http://maven.apache.org/surefire/staging/ (Links to sub-sites work > when transfered to production) > http://maven.apache.org/plugins/maven-failsafe-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-reports-plugin-2.12.1/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > > [ ] +1 > [ ] +0 > [ ] -1 > > And here's my +1 > > > Kristian > > - > 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
[VOTE] Release Maven Stylus Skin version 1.5
Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430&styleName=Html&version=18379 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11430&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-099/ https://repository.apache.org/content/repositories/maven-099/org/apache/maven/skins/maven- stylus-skin/1.5/maven-stylus-skin-1.5-source-release.zip Staging site: http://maven.apache.org/skins/maven-stylus-skin-1.5/ 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
[VOTE] Release Maven Dependency Tree 2.0 + Maven Project Info Reports Plugin 2.5 + Maven Dependency Plugin 2.5
Hi, We solved 2 + 7 + 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14540 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142&styleName=Html&version=17369 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleName=Html&version=18077 There are still "a couple" of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11142&status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11214&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-098/ https://repository.apache.org/content/repositories/maven-098/org/apache/maven/shared/maven- dependency-tree/2.0/maven-dependency-tree-2.0-source-release.zip https://repository.apache.org/content/repositories/maven-098/org/apache/maven/plugins/maven- project-info-reports-plugin/2.5/maven-project-info-reports-plugin-2.5-source- release.zip https://repository.apache.org/content/repositories/maven-098/org/apache/maven/plugins/maven- dependency-plugin/2.5/maven-dependency-plugin-2.5-source-release.zip Staging sites: http://maven.apache.org/shared/maven-dependency-tree-2.0/ http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.5/ http://maven.apache.org/plugins/maven-dependency-plugin-2.5/ 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: How to set up an IT repo ?
See the versions-maven-plugin for examples of use On 30 July 2012 21:16, Stephen Connolly wrote: > mrm-maven-plugin @ mojo > > > On 30 July 2012 21:12, Kristian Rosenvold wrote: > >> Surefire currently has a bunch of test projects at >> >> >> https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources >> >> It uses the maven-invoker-plugin to create a local repository (module >> surefire-setup-integration-tests), but unfortunately all the IT's have >> to run on-line because they resolve tons of different versions of >> junits, testng and similar - which the invoker plugin does not seem to >> handle too well. >> >> I have tested that running on a pre-resolved local repo (hence >> offline) doubles the speed of the IT run. Ideally I'd like to have >> some code that loads all the poms in the test sub-projects, resolves >> all the artifacts and installs them to the test repository. Anyone >> know if this exists, or there's some code I can start from/modify ? >> >> Kristian >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> >
Re: How to set up an IT repo ?
mrm-maven-plugin @ mojo On 30 July 2012 21:12, Kristian Rosenvold wrote: > Surefire currently has a bunch of test projects at > > > https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources > > It uses the maven-invoker-plugin to create a local repository (module > surefire-setup-integration-tests), but unfortunately all the IT's have > to run on-line because they resolve tons of different versions of > junits, testng and similar - which the invoker plugin does not seem to > handle too well. > > I have tested that running on a pre-resolved local repo (hence > offline) doubles the speed of the IT run. Ideally I'd like to have > some code that loads all the poms in the test sub-projects, resolves > all the artifacts and installs them to the test repository. Anyone > know if this exists, or there's some code I can start from/modify ? > > Kristian > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
How to set up an IT repo ?
Surefire currently has a bunch of test projects at https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources It uses the maven-invoker-plugin to create a local repository (module surefire-setup-integration-tests), but unfortunately all the IT's have to run on-line because they resolve tons of different versions of junits, testng and similar - which the invoker plugin does not seem to handle too well. I have tested that running on a pre-resolved local repo (hence offline) doubles the speed of the IT run. Ideally I'd like to have some code that loads all the poms in the test sub-projects, resolves all the artifacts and installs them to the test repository. Anyone know if this exists, or there's some code I can start from/modify ? Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire Plugin version 2.12.1
There is an integration test (TestMultipleMethodsIT) that runs the project located at SVN in https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources/junit48-multiple-methods https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources/junit44-multiple-methods This test passed using this command: mvn -Dtest=junit4.BasicTest#testSuccessOne+testFailOne,junit4.TestThree#testSuccessTwo -Dsurefire.version=2.12.1 test Is this a documentation problem or is there some other issue ? Please try to reproduce in terms of the existing IT projects if you can. As for TestNG, I do not believe this is supported (neither JUnit3). I will update the official feature matrix (http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/plugins/maven-surefire-plugin/featurematrix.html) and mark this as not supported for TestNG/JUnit3. I will redeploy the site sometime tomorrow. Since we traditionally do not cancel votes due to documentation changes, I'm not cancelling this vote until there's a clear proof of a bug. If necessary I'll extend the vote period so we're sure. Kristian mvn -Dsurefire.version=2.12.1 -Dtest=test.mavenproject2.AppNGTest#testMain,test.mavenproject2.AppNGTest#testMain2 test 2012/7/30 Milos Kleint : > -1 > > surefire 1.12.1 + testng 6.5.2 or 6.7: > "mvn > -Dtest=test.mavenproject2.AppNGTest#testMain,test.mavenproject2.AppNGTest#testMain2 > test" > doesn't work (no tests run), even though running just 1 test method > will succeed. > > surefire 1.12.1 + junit 4.10: > "mvn > -Dtest=test.mavenproject1.AppTest#testMain2,test.mavenproject1.AppTest#testMain > test" > doesn't work either, will run just one test, ignore the other. > If I have 2 test classes each with 2 failing tests and attempt to > execute all of them, then only one per class file is executed. > > the variants with 1 test method being executed work fine. > > variant with multiple test classes (not methods) does work in both > testng and junit4. > > Milos > > On Sun, Jul 29, 2012 at 10:45 PM, Kristian Rosenvold > wrote: >> Hi, >> >> This is a bugfix release. >> >> We solved a few issues: >> >> Bug >> >> [SUREFIRE-659] - Maven PDF plugin:showSuccess=false creates empty >> table causing error >> [SUREFIRE-825] - NPE in JUnit4TestChecker if >> org.junit.runner.RunWith class can't be loaded by testClassloader >> [SUREFIRE-827] - Surefire 2.12 cannot run a single test, >> regression from 2.11 >> [SUREFIRE-828] - testng test need a excludedGroups element to not fail >> [SUREFIRE-832] - JUnit categories only work when junit47 provider >> is explicitly set >> [SUREFIRE-836] - regression with surefire 2.12 plugin and SecurityManager >> [SUREFIRE-844] - "test" parameter no longer working with JUnit in >> 2.12 (worked in 2.9 - 2.11) >> [SUREFIRE-847] - surefire cannot run single testng test >> [SUREFIRE-858] - Running a single unit test in Windows >> [SUREFIRE-865] - surefire 2.12 with parallel=methods does not >> execute junit 4.7+ tests in parallel >> [SUREFIRE-869] - Parallel test execution on class level runs not >> all tests but some twice >> [SUREFIRE-871] - Output of forked tests with non-zero exit code not >> retained >> [SUREFIRE-877] - Surefire doesn't support "mixed" TestNG 6.5.x >> config parameter >> [SUREFIRE-879] - maven-surefire-report-plugin fails some times >> with ConcurrentModificationException when running parallel TestNG >> [SUREFIRE-880] - ObjectFactory no longer works with TestNG 6.5.2 >> [SUREFIRE-883] - Cannot run tests in parallel >> >> Improvement >> >> [SUREFIRE-745] - -Dtest supports multiple test classes but not >> multiple test methods >> [SUREFIRE-876] - surefire-junit47 does not work in an OSGi >> classloader environment >> [SUREFIRE-881] - use plugins annotations >> [SUREFIRE-889] - JUnit | supprot inheritance of test's categories/groups >> >> We unresolved 1 issue; which had to be reverted because it was the >> root cause of several of the above issues: >> >> https://jira.codehaus.org/browse/SUREFIRE-800 >> >> >> There are still lots of issues left in JIRA: >> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-096/ >> >> Staging site: (Sync pending) >> http://maven.apache.org/surefire/staging/ (Links to sub-sites work >> when transfered to production) >> http://maven.apache.org/plugins/maven-failsafe-plugin-2.12.1/ >> http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/ >> http://maven.apache.org/plugins/maven-surefire-reports-plugin-2.12.1/ >> >> Guide to testing staged releases: >> http://maven.apache.org/guides/development/guide-testing-releases.html >> >> Vote open for 72 hours. >> >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> And here's my +1 >> >> >>
Re: [VOTE] Apache Maven Indexer 4.1.3
I didn't investigate on that. My main concern is the lucene 3.6.x compatibilty (for performance reason). 2012/7/30 Milos Kleint : > any chance of getting https://jira.codehaus.org/browse/MINDEXER-52 > done or scheduled? this is both causing problems for clients and is a > resource hog as each repository will consume one thread. > > apart from that I'll try testing with netbeans later this week. > > Milos > > On Mon, Jul 30, 2012 at 7:04 PM, Olivier Lamy wrote: >> Hi, >> I'd like to release Maven Indexer 4.1.3. >> We fixed 7 issues: >> https://jira.codehaus.org/browse/MINDEXER/fixforversion/17843 >> >> Staging repository: >> https://repository.apache.org/content/repositories/maven-097/ >> Staging site: http://maven.apache.org/maven-indexer-4.1.3/ (wait sync) >> >> Vote open for 72H. >> >> [+1] >> [0] >> [-1] >> >> Thanks, >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> - >> 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 > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire Plugin version 2.12.1
-1 surefire 1.12.1 + testng 6.5.2 or 6.7: "mvn -Dtest=test.mavenproject2.AppNGTest#testMain,test.mavenproject2.AppNGTest#testMain2 test" doesn't work (no tests run), even though running just 1 test method will succeed. surefire 1.12.1 + junit 4.10: "mvn -Dtest=test.mavenproject1.AppTest#testMain2,test.mavenproject1.AppTest#testMain test" doesn't work either, will run just one test, ignore the other. If I have 2 test classes each with 2 failing tests and attempt to execute all of them, then only one per class file is executed. the variants with 1 test method being executed work fine. variant with multiple test classes (not methods) does work in both testng and junit4. Milos On Sun, Jul 29, 2012 at 10:45 PM, Kristian Rosenvold wrote: > Hi, > > This is a bugfix release. > > We solved a few issues: > > Bug > > [SUREFIRE-659] - Maven PDF plugin:showSuccess=false creates empty > table causing error > [SUREFIRE-825] - NPE in JUnit4TestChecker if > org.junit.runner.RunWith class can't be loaded by testClassloader > [SUREFIRE-827] - Surefire 2.12 cannot run a single test, > regression from 2.11 > [SUREFIRE-828] - testng test need a excludedGroups element to not fail > [SUREFIRE-832] - JUnit categories only work when junit47 provider > is explicitly set > [SUREFIRE-836] - regression with surefire 2.12 plugin and SecurityManager > [SUREFIRE-844] - "test" parameter no longer working with JUnit in > 2.12 (worked in 2.9 - 2.11) > [SUREFIRE-847] - surefire cannot run single testng test > [SUREFIRE-858] - Running a single unit test in Windows > [SUREFIRE-865] - surefire 2.12 with parallel=methods does not > execute junit 4.7+ tests in parallel > [SUREFIRE-869] - Parallel test execution on class level runs not > all tests but some twice > [SUREFIRE-871] - Output of forked tests with non-zero exit code not > retained > [SUREFIRE-877] - Surefire doesn't support "mixed" TestNG 6.5.x > config parameter > [SUREFIRE-879] - maven-surefire-report-plugin fails some times > with ConcurrentModificationException when running parallel TestNG > [SUREFIRE-880] - ObjectFactory no longer works with TestNG 6.5.2 > [SUREFIRE-883] - Cannot run tests in parallel > > Improvement > > [SUREFIRE-745] - -Dtest supports multiple test classes but not > multiple test methods > [SUREFIRE-876] - surefire-junit47 does not work in an OSGi > classloader environment > [SUREFIRE-881] - use plugins annotations > [SUREFIRE-889] - JUnit | supprot inheritance of test's categories/groups > > We unresolved 1 issue; which had to be reverted because it was the > root cause of several of the above issues: > > https://jira.codehaus.org/browse/SUREFIRE-800 > > > There are still lots of issues left in JIRA: > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-096/ > > Staging site: (Sync pending) > http://maven.apache.org/surefire/staging/ (Links to sub-sites work > when transfered to production) > http://maven.apache.org/plugins/maven-failsafe-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-reports-plugin-2.12.1/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > > [ ] +1 > [ ] +0 > [ ] -1 > > And here's my +1 > > > Kristian > > - > 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] Apache Maven Indexer 4.1.3
any chance of getting https://jira.codehaus.org/browse/MINDEXER-52 done or scheduled? this is both causing problems for clients and is a resource hog as each repository will consume one thread. apart from that I'll try testing with netbeans later this week. Milos On Mon, Jul 30, 2012 at 7:04 PM, Olivier Lamy wrote: > Hi, > I'd like to release Maven Indexer 4.1.3. > We fixed 7 issues: > https://jira.codehaus.org/browse/MINDEXER/fixforversion/17843 > > Staging repository: > https://repository.apache.org/content/repositories/maven-097/ > Staging site: http://maven.apache.org/maven-indexer-4.1.3/ (wait sync) > > Vote open for 72H. > > [+1] > [0] > [-1] > > Thanks, > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > - > 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
[VOTE] Apache Maven Indexer 4.1.3
Hi, I'd like to release Maven Indexer 4.1.3. We fixed 7 issues: https://jira.codehaus.org/browse/MINDEXER/fixforversion/17843 Staging repository: https://repository.apache.org/content/repositories/maven-097/ Staging site: http://maven.apache.org/maven-indexer-4.1.3/ (wait sync) Vote open for 72H. [+1] [0] [-1] Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Updating dependencies on Maven 2.x to Maven 3.x in plugins?
On Jul 30, 2012, at 10:10 AM, Stephen Connolly wrote: > The only reason to do this from my PoV is if the plugin requires features > only available in Maven 3. > > There are still a significant number of users who use Maven 2.2.1, yeah I > would love to get them to jump up to 3.0.4, but I acknowledge that is > something that may be beyond their control. Forcing plugin dependencies up > without a valid driving requirement is just forcing unnecessary pain on the > end users. > > IMHO features should drive the upgrading of dependencies, nothing else. > +1 There is little value in updating plugins to use Maven 3.x components for the sake of it. The reason we spent so much time making sure that 3.x runs older components was to ensure no one has to do this. > -Stephen > > On 30 July 2012 12:44, Stanislav Ochotnicky wrote: > >> Hi everyone, >> >> I am wondering what is general feeling about updating maven plugins from >> depending on Maven 2.x artifacts to their Maven 3.x counterparts. >> >> I am aware not all m2 artifacts have equivalents in m3 (i.e. >> maven-project, maven-artifact-manager and few others). Things have moved >> around somewhat (i.e. few classes from maven-artifact moved to -core or >> -compat). >> >> However, if someone provided patches, with builds and unit tests working >> and all that jazz, would there be willingness to work on making this >> transition happen? Or is the time not right just yet? >> >> Note that we've been running maven-3.0.4 and ~60 maven plugins without >> maven-core,maven-artifact and quite few other 2.x artifacts, for about a >> year and everything works as far as we are concerned (limited use case >> of Fedora Linux apply of course) >> >> For the record full list of maven 2.x artifacts we still keep is: >> * maven-artifact-manager >> * maven-error-diagnostics >> * maven-model >> * maven-monitor >> * maven-plugin-descriptor >> * maven-plugin-registry >> * maven-profile >> * maven-project >> * maven-toolchain >> >> -- >> Stanislav Ochotnicky >> Software Engineer - Base Operating Systems Brno >> >> PGP: 7B087241 >> Red Hat Inc. http://cz.redhat.com >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> Thanks, Jason -- Jason van Zyl Founder & CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We all have problems. How we deal with them is a measure of our worth. -- Unknown
Re: Updating dependencies on Maven 2.x to Maven 3.x in plugins?
The only reason to do this from my PoV is if the plugin requires features only available in Maven 3. There are still a significant number of users who use Maven 2.2.1, yeah I would love to get them to jump up to 3.0.4, but I acknowledge that is something that may be beyond their control. Forcing plugin dependencies up without a valid driving requirement is just forcing unnecessary pain on the end users. IMHO features should drive the upgrading of dependencies, nothing else. -Stephen On 30 July 2012 12:44, Stanislav Ochotnicky wrote: > Hi everyone, > > I am wondering what is general feeling about updating maven plugins from > depending on Maven 2.x artifacts to their Maven 3.x counterparts. > > I am aware not all m2 artifacts have equivalents in m3 (i.e. > maven-project, maven-artifact-manager and few others). Things have moved > around somewhat (i.e. few classes from maven-artifact moved to -core or > -compat). > > However, if someone provided patches, with builds and unit tests working > and all that jazz, would there be willingness to work on making this > transition happen? Or is the time not right just yet? > > Note that we've been running maven-3.0.4 and ~60 maven plugins without > maven-core,maven-artifact and quite few other 2.x artifacts, for about a > year and everything works as far as we are concerned (limited use case > of Fedora Linux apply of course) > > For the record full list of maven 2.x artifacts we still keep is: > * maven-artifact-manager > * maven-error-diagnostics > * maven-model > * maven-monitor > * maven-plugin-descriptor > * maven-plugin-registry > * maven-profile > * maven-project > * maven-toolchain > > -- > Stanislav Ochotnicky > Software Engineer - Base Operating Systems Brno > > PGP: 7B087241 > Red Hat Inc. http://cz.redhat.com > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Updating dependencies on Maven 2.x to Maven 3.x in plugins?
I work with a lot of older (sometimes out of service software [customers pay a fortune but are prepared to live with it]) so I'm generally a fan of the lowest common denominator. What do you hope to achieve by the? Are there any specific outstanding issues that need this change to solve? -Chris On 30/07/2012, at 9:44 PM, Stanislav Ochotnicky wrote: > Hi everyone, > > I am wondering what is general feeling about updating maven plugins from > depending on Maven 2.x artifacts to their Maven 3.x counterparts. > > I am aware not all m2 artifacts have equivalents in m3 (i.e. > maven-project, maven-artifact-manager and few others). Things have moved > around somewhat (i.e. few classes from maven-artifact moved to -core or > -compat). > > However, if someone provided patches, with builds and unit tests working > and all that jazz, would there be willingness to work on making this > transition happen? Or is the time not right just yet? > > Note that we've been running maven-3.0.4 and ~60 maven plugins without > maven-core,maven-artifact and quite few other 2.x artifacts, for about a > year and everything works as far as we are concerned (limited use case > of Fedora Linux apply of course) > > For the record full list of maven 2.x artifacts we still keep is: > * maven-artifact-manager > * maven-error-diagnostics > * maven-model > * maven-monitor > * maven-plugin-descriptor > * maven-plugin-registry > * maven-profile > * maven-project > * maven-toolchain > > -- > Stanislav Ochotnicky > Software Engineer - Base Operating Systems Brno > > PGP: 7B087241 > Red Hat Inc. http://cz.redhat.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 Surefire Plugin version 2.12.1
+1 LieGrue, strub - Original Message - > From: Kristian Rosenvold > To: Maven Developers List > Cc: > Sent: Sunday, July 29, 2012 10:45 PM > Subject: [VOTE] Release Maven Surefire Plugin version 2.12.1 > > Hi, > > This is a bugfix release. > > We solved a few issues: > > Bug > > [SUREFIRE-659] - Maven PDF plugin:showSuccess=false creates empty > table causing error > [SUREFIRE-825] - NPE in JUnit4TestChecker if > org.junit.runner.RunWith class can't be loaded by testClassloader > [SUREFIRE-827] - Surefire 2.12 cannot run a single test, > regression from 2.11 > [SUREFIRE-828] - testng test need a excludedGroups element to not fail > [SUREFIRE-832] - JUnit categories only work when junit47 provider > is explicitly set > [SUREFIRE-836] - regression with surefire 2.12 plugin and SecurityManager > [SUREFIRE-844] - "test" parameter no longer working with JUnit in > 2.12 (worked in 2.9 - 2.11) > [SUREFIRE-847] - surefire cannot run single testng test > [SUREFIRE-858] - Running a single unit test in Windows > [SUREFIRE-865] - surefire 2.12 with parallel=methods does not > execute junit 4.7+ tests in parallel > [SUREFIRE-869] - Parallel test execution on class level runs not > all tests but some twice > [SUREFIRE-871] - Output of forked tests with non-zero exit code not > retained > [SUREFIRE-877] - Surefire doesn't support "mixed" TestNG 6.5.x > config parameter > [SUREFIRE-879] - maven-surefire-report-plugin fails some times > with ConcurrentModificationException when running parallel TestNG > [SUREFIRE-880] - ObjectFactory no longer works with TestNG 6.5.2 > [SUREFIRE-883] - Cannot run tests in parallel > > Improvement > > [SUREFIRE-745] - -Dtest supports multiple test classes but not > multiple test methods > [SUREFIRE-876] - surefire-junit47 does not work in an OSGi > classloader environment > [SUREFIRE-881] - use plugins annotations > [SUREFIRE-889] - JUnit | supprot inheritance of test's categories/groups > > We unresolved 1 issue; which had to be reverted because it was the > root cause of several of the above issues: > > https://jira.codehaus.org/browse/SUREFIRE-800 > > > There are still lots of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-096/ > > Staging site: (Sync pending) > http://maven.apache.org/surefire/staging/ (Links to sub-sites work > when transfered to production) > http://maven.apache.org/plugins/maven-failsafe-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-reports-plugin-2.12.1/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > > [ ] +1 > [ ] +0 > [ ] -1 > > And here's my +1 > > > Kristian > > - > 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 Surefire Plugin version 2.12.1
+1 2012/7/29 Kristian Rosenvold : > Hi, > > This is a bugfix release. > > We solved a few issues: > > Bug > > [SUREFIRE-659] - Maven PDF plugin:showSuccess=false creates empty > table causing error > [SUREFIRE-825] - NPE in JUnit4TestChecker if > org.junit.runner.RunWith class can't be loaded by testClassloader > [SUREFIRE-827] - Surefire 2.12 cannot run a single test, > regression from 2.11 > [SUREFIRE-828] - testng test need a excludedGroups element to not fail > [SUREFIRE-832] - JUnit categories only work when junit47 provider > is explicitly set > [SUREFIRE-836] - regression with surefire 2.12 plugin and SecurityManager > [SUREFIRE-844] - "test" parameter no longer working with JUnit in > 2.12 (worked in 2.9 - 2.11) > [SUREFIRE-847] - surefire cannot run single testng test > [SUREFIRE-858] - Running a single unit test in Windows > [SUREFIRE-865] - surefire 2.12 with parallel=methods does not > execute junit 4.7+ tests in parallel > [SUREFIRE-869] - Parallel test execution on class level runs not > all tests but some twice > [SUREFIRE-871] - Output of forked tests with non-zero exit code not > retained > [SUREFIRE-877] - Surefire doesn't support "mixed" TestNG 6.5.x > config parameter > [SUREFIRE-879] - maven-surefire-report-plugin fails some times > with ConcurrentModificationException when running parallel TestNG > [SUREFIRE-880] - ObjectFactory no longer works with TestNG 6.5.2 > [SUREFIRE-883] - Cannot run tests in parallel > > Improvement > > [SUREFIRE-745] - -Dtest supports multiple test classes but not > multiple test methods > [SUREFIRE-876] - surefire-junit47 does not work in an OSGi > classloader environment > [SUREFIRE-881] - use plugins annotations > [SUREFIRE-889] - JUnit | supprot inheritance of test's categories/groups > > We unresolved 1 issue; which had to be reverted because it was the > root cause of several of the above issues: > > https://jira.codehaus.org/browse/SUREFIRE-800 > > > There are still lots of issues left in JIRA: > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-096/ > > Staging site: (Sync pending) > http://maven.apache.org/surefire/staging/ (Links to sub-sites work > when transfered to production) > http://maven.apache.org/plugins/maven-failsafe-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-reports-plugin-2.12.1/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > > [ ] +1 > [ ] +0 > [ ] -1 > > And here's my +1 > > > Kristian > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MDEP-339 and MPIR-237
tested dependency:tree. Works fine. Nice job ! 2012/7/24 Hervé BOUTEMY : > I think I finally fixed MDEP-339 and MPIR-237: these plugins should now be > fully > Maven 2 and Maven 3 compatible. > > AFAIK, m-project-info-reports-p is the last plugin that was causing trouble to > publish standard site with Maven 3. > > maven-dependency-tree has been reworked to an thin layer on Maven 2 and Maven > 3 dependency resolution code, and should easily be extensible in the future to > any change like Eclipse Aether or any other implementation. > > > I intend to release these 3 artifacts in about a week: please test and report > if you find anything not as expected. > > Regards, > > Hervé > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Re : Release of poms parent
2012/7/30 herve.bout...@free.fr : > I wanted to release mpir first (M3 compatible) as it currently depends on parent snapshot, it's probably a chicken and egg release issue :-). BTW no problem to wait mpir first. > > Envoyé depuis mon mobile > > - Reply message - > De : "Olivier Lamy" > Pour : "Maven Developers List" > Objet : Release of poms parent > Date : lun., juil. 30, 2012 09:32 > > > Hi, > In order to release plugins, I'd like to release parent poms (asf, > maven and plugins). > > No objections ? > > Thanks, > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Updating dependencies on Maven 2.x to Maven 3.x in plugins?
Hi everyone, I am wondering what is general feeling about updating maven plugins from depending on Maven 2.x artifacts to their Maven 3.x counterparts. I am aware not all m2 artifacts have equivalents in m3 (i.e. maven-project, maven-artifact-manager and few others). Things have moved around somewhat (i.e. few classes from maven-artifact moved to -core or -compat). However, if someone provided patches, with builds and unit tests working and all that jazz, would there be willingness to work on making this transition happen? Or is the time not right just yet? Note that we've been running maven-3.0.4 and ~60 maven plugins without maven-core,maven-artifact and quite few other 2.x artifacts, for about a year and everything works as far as we are concerned (limited use case of Fedora Linux apply of course) For the record full list of maven 2.x artifacts we still keep is: * maven-artifact-manager * maven-error-diagnostics * maven-model * maven-monitor * maven-plugin-descriptor * maven-plugin-registry * maven-profile * maven-project * maven-toolchain -- Stanislav Ochotnicky Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc. http://cz.redhat.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire Plugin version 2.12.1
+1 On Sun, Jul 29, 2012 at 10:45 PM, Kristian Rosenvold < kristian.rosenv...@gmail.com> wrote: > Hi, > > This is a bugfix release. > > We solved a few issues: > > Bug > > [SUREFIRE-659] - Maven PDF plugin:showSuccess=false creates empty > table causing error > [SUREFIRE-825] - NPE in JUnit4TestChecker if > org.junit.runner.RunWith class can't be loaded by testClassloader > [SUREFIRE-827] - Surefire 2.12 cannot run a single test, > regression from 2.11 > [SUREFIRE-828] - testng test need a excludedGroups element to not fail > [SUREFIRE-832] - JUnit categories only work when junit47 provider > is explicitly set > [SUREFIRE-836] - regression with surefire 2.12 plugin and > SecurityManager > [SUREFIRE-844] - "test" parameter no longer working with JUnit in > 2.12 (worked in 2.9 - 2.11) > [SUREFIRE-847] - surefire cannot run single testng test > [SUREFIRE-858] - Running a single unit test in Windows > [SUREFIRE-865] - surefire 2.12 with parallel=methods does not > execute junit 4.7+ tests in parallel > [SUREFIRE-869] - Parallel test execution on class level runs not > all tests but some twice > [SUREFIRE-871] - Output of forked tests with non-zero exit code not > retained > [SUREFIRE-877] - Surefire doesn't support "mixed" TestNG 6.5.x > config parameter > [SUREFIRE-879] - maven-surefire-report-plugin fails some times > with ConcurrentModificationException when running parallel TestNG > [SUREFIRE-880] - ObjectFactory no longer works with TestNG 6.5.2 > [SUREFIRE-883] - Cannot run tests in parallel > > Improvement > > [SUREFIRE-745] - -Dtest supports multiple test classes but not > multiple test methods > [SUREFIRE-876] - surefire-junit47 does not work in an OSGi > classloader environment > [SUREFIRE-881] - use plugins annotations > [SUREFIRE-889] - JUnit | supprot inheritance of test's > categories/groups > > We unresolved 1 issue; which had to be reverted because it was the > root cause of several of the above issues: > > https://jira.codehaus.org/browse/SUREFIRE-800 > > > There are still lots of issues left in JIRA: > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-096/ > > Staging site: (Sync pending) > http://maven.apache.org/surefire/staging/ (Links to sub-sites work > when transfered to production) > http://maven.apache.org/plugins/maven-failsafe-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/ > http://maven.apache.org/plugins/maven-surefire-reports-plugin-2.12.1/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > > [ ] +1 > [ ] +0 > [ ] -1 > > And here's my +1 > > > Kristian > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Release of poms parent
Hi, In order to release plugins, I'd like to release parent poms (asf, maven and plugins). No objections ? Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
