[ANN] Apache Maven Surefire Plugin 3.0.0-M3 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Surefire Plugin, version 3.0.0-M3. The release contains 6 bug fixes. Again we received contributions from the community in form of bug reports and bug fixes. Thank you and keep them coming! http://maven.apache.org/plugins/maven-surefire-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-surefire-plugin 3.0.0-M3 or for failsafe: org.apache.maven.plugins maven-failsafe-plugin 3.0.0-M3 or for surefire-report: org.apache.maven.plugins maven-surefire-report-plugin 3.0.0-M3 You can download the appropriate sources etc. from the download page: https://maven.apache.org/surefire/download.cgi Release Notes - Maven Surefire - Version 3.0.0-M3 Bug [SUREFIRE-1613] - maven-surefire-report-plugin fails on JDK 11 [SUREFIRE-1614] - JUnit Runner that writes to System.out corrupts Surefire's STDOUT when using JUnit's Vintage Engine [SUREFIRE-1616] - Smart stacktrace in test summary should not print JUnit5 assertion exception type Improvement [SUREFIRE-1608] - dump error paths with the same root cause in Boot Manifest-JAR only once without stacktrace Task [SUREFIRE-1609] - Use ShadeFire 3.0.0-M2 in the internal tests [SUREFIRE-1611] - Deprecate skipTests in Failsafe Plugin Enjoy, -The Apache Maven team
[RESULT] [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M3
Hi, The vote has passed with the following result: +1 : Christian Stein, Enrico Olivelli, Eric Lilja, Olivier Lamy, Karl Heinz Marbaise, Tibor Digana PMC quorum: reached I will promote the artifacts to the central repo. I will add the release to the next board report. Cheers Tibor
Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M3
Hi, The vote has passed with the following result: +1 : Christian Stein, Enrico Olivelli, Eric Lilja, Olivier Lamy, Karl Heinz Marbaise, Tibor Digana PMC quorum: reached I will promote the artifacts to the central repo. I will add the release to the next board report. Cheers Tibor On Thu, Dec 20, 2018 at 10:47 AM Tibor Digana wrote: > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342872 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1479 > > https://repository.apache.org/content/repositories/maven-1479/org/apache/maven/surefire/surefire/3.0.0-M3/surefire-3.0.0-M3-source-release.zip > > Source release checksum(s): > surefire-3.0.0-M3-source-release.zip sha1: > 4d1187b9c1f1922d13ac25d4538f30225ea8e27a > surefire-3.0.0-M3-source-release.zip sha512: > c13d24c10ec59278113f862702538770fccf1f816a7803dc7adaaa9f90ab0a76bad0d83526cd4ce80d3891e9364f4079020b70478dede0e330f98f8f79afae54 > > Staging site: > http://maven.apache.org/surefire-archives/surefire-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Cheers > Tibor > >
Re: On Maven 4.0.0 and beyond
On Sun 23 Dec 2018 at 11:32, Michael Osipov wrote: > Am 2018-12-23 um 11:14 schrieb Stephen Connolly: > > Over the break I *may* get some time to work on the tooling improvements > > that Robert, Hervé and I identified for the jump to 4.0.0 (namely a > better > > way to ensure api binary compatibility for the APIs that core exposes to > > plugins) > > > > If I do get a chance to work on this, it’ll be in a branch until we think > > it’s “good enough”. > > > > The idea is to enable large scale lambdafication and other Java 8 > > improvements in core without breaking plugins. > > I'd rather see a big bug/PR sweep than lambafication which does not give > a huge benefit for the users. What else I'd like to see is edge cases > covered Christian Schulte started to work on. We can break things this > time and clean them up. We need to get people actually involved in the code. Lambdafication and other modernisation refactoring enable people to get their hands dirty without committing too much. Asking potential new blood to look at the harder things will not get us new blood. Actual committers should be looking at the other changes... though I don’t believe we can change the pom until 5.0.0 which is why the scope of 4.0.0 is likely: * modernise the codebase * Java 8 baseline * perhaps relocate aether to org.apache.maven * other behaviour changes that do not affect the pom * nicer failure message when presented with a newer modelVersion * native consumer pom support... perhaps also PDT publishing > > Michael > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
Re: On Maven 4.0.0 and beyond
Am 2018-12-23 um 11:14 schrieb Stephen Connolly: Over the break I *may* get some time to work on the tooling improvements that Robert, Hervé and I identified for the jump to 4.0.0 (namely a better way to ensure api binary compatibility for the APIs that core exposes to plugins) If I do get a chance to work on this, it’ll be in a branch until we think it’s “good enough”. The idea is to enable large scale lambdafication and other Java 8 improvements in core without breaking plugins. I'd rather see a big bug/PR sweep than lambafication which does not give a huge benefit for the users. What else I'd like to see is edge cases covered Christian Schulte started to work on. We can break things this time and clean them up. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
On Maven 4.0.0 and beyond
Over the break I *may* get some time to work on the tooling improvements that Robert, Hervé and I identified for the jump to 4.0.0 (namely a better way to ensure api binary compatibility for the APIs that core exposes to plugins) If I do get a chance to work on this, it’ll be in a branch until we think it’s “good enough”. The idea is to enable large scale lambdafication and other Java 8 improvements in core without breaking plugins. If we have good reliable tooling, then we hope to be able to encourage contributions (as you don’t need a CLA for an “obvious” ~10-15 line patch - intent to submit is sufficient) and get the code base more energised. -Stephen P.S. the existing api checker tools do not meet our needs as they check too much, we only want those classes exposed to plugins and extensions. I think animal sniffer might be closest to what we need - as it allows defining the signature scope - but it needs a different execution mode to do what we need: check that the signature is still valid for a specific classpath. P.P.S. I also might need to think about Java modules... eg would it make sense to use modules for Maven 5.0 as an alternative to classworlds? -- Sent from my phone
Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M3
+1 On Thu, Dec 20, 2018 at 10:47 AM Tibor Digana wrote: > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342872 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1479 > > https://repository.apache.org/content/repositories/maven-1479/org/apache/maven/surefire/surefire/3.0.0-M3/surefire-3.0.0-M3-source-release.zip > > Source release checksum(s): > surefire-3.0.0-M3-source-release.zip sha1: > 4d1187b9c1f1922d13ac25d4538f30225ea8e27a > surefire-3.0.0-M3-source-release.zip sha512: > c13d24c10ec59278113f862702538770fccf1f816a7803dc7adaaa9f90ab0a76bad0d83526cd4ce80d3891e9364f4079020b70478dede0e330f98f8f79afae54 > > Staging site: > http://maven.apache.org/surefire-archives/surefire-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Cheers > Tibor > >
