[GitHub] [maven-doxia-site] elharo merged pull request #7: we don't use subversion any more
elharo merged pull request #7: URL: https://github.com/apache/maven-doxia-site/pull/7 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-doxia-site] elharo opened a new pull request #7: we don't use subversion any more
elharo opened a new pull request #7: URL: https://github.com/apache/maven-doxia-site/pull/7 @hboutemy This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Open Pull Requests
Hi, I'm looking forward to the improvements introduced by Rob as well and therefore would like to kindly ask if there is a timeframe in which one which can expect the releases to happen or if there is anything additional needed to proceed? Best regards and thank you all for developing Maven! Tobias Am 02.06.2020 um 00:31 schrieb Robert Oxspring: > >>> Before we go to release stuff, will you need more changes maybe for >>> assembly plugin? >>> to make this faster and as we already did in past we can release all >>> together. >>> >> >> Great - good to know the process! >> >> I’d briefly forgotten this all started with the assembly plugin so will bump >> to SNAPSHOT dependencies locally and confirm whether further changes are >> necessary. >> > > I’ve had a quick test with SNAPSHOT versions of everything and all works as > expected. I don’t think there are any further changes I need. > > Thanks, > > Rob > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Suggestion: announce Maven 3.0.x is EOL
Every plugin has its freedom to choose its minimum. If for some reason Maven 3.2.x broke something that is required by the plugin, the solution is to change the requirement of the plugin, and not to fix it with a backport of Maven 3.2.x I see https://github.com/apache/maven-surefire/pull/274 [https://github.com/apache/maven-surefire/pull/274] contains references to the history page, that was a misleading action. Surefire has the option to decide Maven 3.1 will be the new minimum. Instead we should add a column to https://maven.apache.org/plugins/index.html [https://maven.apache.org/plugins/index.html] with the Maven compatibilty. As said by Olivier, in case of a blocking security issue, we might be forced to do a security release of every 3.n release. So I'd prefer to leave the history page as it is. If people want an official statement, I can write one to make clear what the difference is between EOL and minimum support. thanks, Robert On 15-6-2020 17:13:35, Elliotte Rusty Harold wrote: My concern is PRs like this one to restore Maven 3.0.5 compatibility to surefire: https://github.com/apache/maven-surefire/pull/274 I think we should have a clearly stated policy that we're no longer going to expend effort supporting Maven 3.0.x in our plugins. By contrast, we are currently planning to continue support for Maven 3.1.x+ in the various plugins. There are now multiple +1's on this PR. Can I proceed? On Sat, Jun 13, 2020 at 2:06 PM Robert Scholte wrote: > > To me these are 2 different things. > Yes, we are going to require Maven 3.1 for our plugins (and because of API > changes we need to be explicit about this), but that doesn't mean that Maven > 3.0.x itself is end of life. > > Depending on how you ask the question, to me EOLs are either about majors or > minors. > It is clear to me we won't do anything for Maven 2 anymore. > At the same time, I expect we will never do a 3.3.10 or 3.5.5. > > I don't know what people expect by a statement about EOL: nobody has a > support contract for Maven, so talking about EOL doesn't make any sense to me. > It all depends on what critical issue may appear, based on that we'll make > our decision. > To me it is either: EOL for Maven2 and/or with every new release the previous > will be marked as EOL. > > Robert > > > > > On 13-6-2020 17:26:15, Elliotte Rusty Harold wrote: > I think we've achieved consensus that Maven 3.0.x should no longer be > supported by new plugin releases and 3.1.x is our minimum. Assuming > that's true, this PR updates the history page to account for that: > > https://github.com/apache/maven-site/pull/176 > > If anyone thinks we have not achieved consensus, or should not > announce that 3.0.x is end of life, please say so. > > As always, please also comment on exact language of the PR, markup > syntax, and other pages that need to be updated. Thanks. > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Elliotte Rusty Harold elh...@ibiblio.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Suggestion: announce Maven 3.0.x is EOL
My concern is PRs like this one to restore Maven 3.0.5 compatibility to surefire: https://github.com/apache/maven-surefire/pull/274 I think we should have a clearly stated policy that we're no longer going to expend effort supporting Maven 3.0.x in our plugins. By contrast, we are currently planning to continue support for Maven 3.1.x+ in the various plugins. There are now multiple +1's on this PR. Can I proceed? On Sat, Jun 13, 2020 at 2:06 PM Robert Scholte wrote: > > To me these are 2 different things. > Yes, we are going to require Maven 3.1 for our plugins (and because of API > changes we need to be explicit about this), but that doesn't mean that Maven > 3.0.x itself is end of life. > > Depending on how you ask the question, to me EOLs are either about majors or > minors. > It is clear to me we won't do anything for Maven 2 anymore. > At the same time, I expect we will never do a 3.3.10 or 3.5.5. > > I don't know what people expect by a statement about EOL: nobody has a > support contract for Maven, so talking about EOL doesn't make any sense to me. > It all depends on what critical issue may appear, based on that we'll make > our decision. > To me it is either: EOL for Maven2 and/or with every new release the previous > will be marked as EOL. > > Robert > > > > > On 13-6-2020 17:26:15, Elliotte Rusty Harold wrote: > I think we've achieved consensus that Maven 3.0.x should no longer be > supported by new plugin releases and 3.1.x is our minimum. Assuming > that's true, this PR updates the history page to account for that: > > https://github.com/apache/maven-site/pull/176 > > If anyone thinks we have not achieved consensus, or should not > announce that 3.0.x is end of life, please say so. > > As always, please also comment on exact language of the PR, markup > syntax, and other pages that need to be updated. Thanks. > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Elliotte Rusty Harold elh...@ibiblio.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M5
+1 (non binding) - checksums ok - built locally on Fedora + JDK14, all tests passed (mvn install -Prun-its) - Tested with a few projects, even with the new TCP implementation Thank you Tibor for putting this all together Enrico Il giorno dom 14 giu 2020 alle ore 23:46 Dan Tran ha scritto: > +1 tested with our 300+ maven modules build > > Found the following new 'good' behaviors/fixes > >1. Junit 4 test class now have 'public' scope at both class and method > level. >2. Exception at test 'setup' ( ie @Before) now show up as failures, They > are ignored at M4 > > Great works > > Thanks > > > > On Sat, Jun 13, 2020 at 3:40 PM Tibor Digana > wrote: > > > Hi Herve, > > > > We can fork the discussion about this problem apart in the Slack. > > Thx for finding this. > > > > T > > > > > > On Sat, Jun 13, 2020 at 9:35 PM Hervé BOUTEMY > > wrote: > > > > > +1 > > > > > > near full reproducibility of reference artifacts with JDK 8 on Windows: > > 48 > > > artifacts are ok, just 2 still have issues: > > > - surefire-3.0.0-M5-source-release.zip: I don't know why my local build > > > added 3 dependency-reduced-pom.xml that do not exist in reference build > > > - surefire-shadefire-3.0.0-M5.jar: some strange timestamp issues for > some > > > shaded content, probably a subtle maven-shade-plugin bug > > > > > > Regards, > > > > > > Hervé > > > > > > Le samedi 13 juin 2020, 15:46:10 CEST Tibor Digana a écrit : > > > > Hi, > > > > > > > > We solved 40 issues: > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&ve > > > > rsion=12344612 > > > > > > > > There are still a couple of issues left in JIRA: > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20 > > > > status%20%3D%20Open%20ORDER%20BY%20priority%20DESC > > > > > > > > Staging repo: > > > > https://repository.apache.org/content/repositories/maven-1590/ > > > > > > > > > > https://repository.apache.org/content/repositories/maven-1590/org/apache/mav > > > > en/surefire/surefire/3.0.0-M5/surefire-3.0.0-M5-source-release.zip > > > > > > > > Source release checksum(s): > > > > surefire-3.0.0-M5-source-release.zip sha1: > > > > 687a89ceb4a1b2e5dd472deec8d3843f2a98b68f > > > > surefire-3.0.0-M5-source-release.zip sha512: > > > > > > > > > > e88ced058923b349acfe1948d4c4a7ff6f4bef08e5685f2f2ac73cfb26ad35fd6578f05309f0 > > > > 91081f01986b19bbca38a2fe6bf0fbd16980cd6f41228c529ee7 > > > > > > > > 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 > > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > >
