Re: Reproducible builds between OSes
Since it can be set in MAVEN_OPTS issue is maybe not that a big deal.
Le lun. 13 févr. 2023 à 07:22, Christoph Läubrich a
écrit :
> > On the bright side, `System.lineSeparator()` is almost never used
>
> I use that all day long in my code, and probably this will change for
> other classes as well, so relying on that people use the system property
> seems broken by design.
>
> Am 12.02.23 um 23:28 schrieb Piotr P. Karwasz:
> > Hi Elliotte,
> >
> > On Sat, 11 Feb 2023 at 14:02, Elliotte Rusty Harold
> wrote:
> >> IMHO in 2023 the problem is that anything relies on a system dependent
> >> line.separator instead of explicitly specifying which bytes are
> >> output. I've fixed some instances of that antipattern over the years.
> >> Please file bugs on any plugin you notice that still does that.
> >
> > I agree that "line.separator" should not be used anywhere.
> >
> > Unfortunately it is used whenever `BufferedWriter` or `PrintStream` is
> > used, so the simplest build that uses the "jar" plugin will already be
> > system dependent ("pom.properties" uses the line separator). On the
> > bright side, `System.lineSeparator()` is almost never used: most
> > classes use the current value of the "line.separator" property, not
> > the boot time value.
> >
> > I would be satisfied if Maven plugins started using `BufferedWriter`s
> > with a hardcoded `newLine` method, but for backward compatibility
> > Maven could:
> >
> > 1. Use a separate Maven POM property (e.g.
> > `project.build.lineSeparator`) with alphanumeric values (e.g. `CR`,
> > `LF`, `CRLF`). Plugins can issue a warning if this is not set, like in
> > the case of `sourceEncoding`:
> > https://maven.apache.org/general.html#encoding-warning
> > 2. Set the `line.separator` Java system property to the correct value
> > before any plugin runs: this will not modify `System.lineSeparator()`,
> > but will change the behavior of all `BufferedWriter`s,
> > 3. Ignore `System.lineSeparator()` in the rare plugins that were
> > adapted to use it.
> >
> > Piotr
> >
> > -
> > 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 Deploy Plugin 3.1.0
Howdy, Well, IMHO MDEPLOY-206 should be in release notes, as it carries substantial code change that needs to be explained: These both commits run under that issue: https://github.com/apache/maven-deploy-plugin/commit/59bee05f8a935f4c8ac9fcf0da47bab60c425e92 https://github.com/apache/maven-deploy-plugin/commit/2ff9a2eac94d2ca25e48af975ac47375d6fdb323 Their (combined) essence is: create one DeployRequest when deployAtEnd used. But yes, this code change has nothing to do with "parallel deploy", as it will happen in latest resolver instead So IMHO the issue IS in the right place, but carries WRONG name/description Thanks T On Sun, Feb 12, 2023 at 2:47 PM Slawomir Jaranowski wrote: > Hi, > > Agree with Olivier MDEPLOY-206 will be resolved by MRESOLVER-32 so should > not be a part of current release notes. > > > wt., 7 lut 2023 o 00:36 Olivier Lamy napisał(a): > > > +1 > > But https://issues.apache.org/jira/browse/MDEPLOY-206 should not be > > part of the release notes as it doesn't work yet so it's really > > confusing/ > > > > On Mon, 6 Feb 2023 at 22:52, Tamás Cservenák > wrote: > > > > > > Howdy, > > > > > > We fixed several issues: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317228=12352181 > > > > > > Staged repository: > > > https://repository.apache.org/content/repositories/maven-1866/ > > > > > > Source release SHA512: > > > > > > 7260610d06bff950afc07767e13a0a19ac46d68c92bd866ae18c3184089dcf50d898c01d3156907c9819805d7569203b7e6091b9b0171e255e1e6a9c8b3cdd00 > > > > > > Staged site: > > > https://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/ > > > > > > Vote open for 72h > > > > > > Thanks > > > T > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > -- > Sławomir Jaranowski >
Re: [VOTE] Release Maven Invoker Plugin version 3.5.0
+1 On Mon, 13 Feb 2023 at 05:42, Michael Osipov wrote: > > Hi, > > we solved 9 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12352645 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1872/ > https://repository.apache.org/content/repositories/maven-1872/org/apache/maven/plugins/maven-invoker-plugin/3.5.0/maven-invoker-plugin-3.5.0-source-release.zip > > Source release checksum(s): > maven-invoker-plugin-3.5.0-source-release.zip > sha512: > a32657622fd69cd1964fbec1171175658735bb49826ebd96f7e27f9e4a87bdd477547a733736235db1284b7ebab9b5977263cf83d9d27bf88843a741f6ea2b31 > > Staging site: > https://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/ > > Guide to testing staged releases: > https://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: Reproducible builds between OSes
> On the bright side, `System.lineSeparator()` is almost never used
I use that all day long in my code, and probably this will change for
other classes as well, so relying on that people use the system property
seems broken by design.
Am 12.02.23 um 23:28 schrieb Piotr P. Karwasz:
Hi Elliotte,
On Sat, 11 Feb 2023 at 14:02, Elliotte Rusty Harold wrote:
IMHO in 2023 the problem is that anything relies on a system dependent
line.separator instead of explicitly specifying which bytes are
output. I've fixed some instances of that antipattern over the years.
Please file bugs on any plugin you notice that still does that.
I agree that "line.separator" should not be used anywhere.
Unfortunately it is used whenever `BufferedWriter` or `PrintStream` is
used, so the simplest build that uses the "jar" plugin will already be
system dependent ("pom.properties" uses the line separator). On the
bright side, `System.lineSeparator()` is almost never used: most
classes use the current value of the "line.separator" property, not
the boot time value.
I would be satisfied if Maven plugins started using `BufferedWriter`s
with a hardcoded `newLine` method, but for backward compatibility
Maven could:
1. Use a separate Maven POM property (e.g.
`project.build.lineSeparator`) with alphanumeric values (e.g. `CR`,
`LF`, `CRLF`). Plugins can issue a warning if this is not set, like in
the case of `sourceEncoding`:
https://maven.apache.org/general.html#encoding-warning
2. Set the `line.separator` Java system property to the correct value
before any plugin runs: this will not modify `System.lineSeparator()`,
but will change the behavior of all `BufferedWriter`s,
3. Ignore `System.lineSeparator()` in the rare plugins that were
adapted to use it.
Piotr
-
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: Reproducible builds between OSes
On Sun, Feb 12, 2023 at 10:28 PM Piotr P. Karwasz
wrote:
> Unfortunately it is used whenever `BufferedWriter` or `PrintStream` is
> used, so the simplest build that uses the "jar" plugin will already be
> system dependent ("pom.properties" uses the line separator).
Yes, I am aware. Believe it or not, I wrote an entire book about not
using `BufferedWriter` and `PrintStream`. Not kidding. I really did.
Still in print from O'Reilly :-)
Anywhere other than System.out/System.err that is using BufferedWriter
and PrintStream needs to be fixed.
--
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: Reproducible builds between OSes
Hi Elliotte,
On Sat, 11 Feb 2023 at 14:02, Elliotte Rusty Harold wrote:
> IMHO in 2023 the problem is that anything relies on a system dependent
> line.separator instead of explicitly specifying which bytes are
> output. I've fixed some instances of that antipattern over the years.
> Please file bugs on any plugin you notice that still does that.
I agree that "line.separator" should not be used anywhere.
Unfortunately it is used whenever `BufferedWriter` or `PrintStream` is
used, so the simplest build that uses the "jar" plugin will already be
system dependent ("pom.properties" uses the line separator). On the
bright side, `System.lineSeparator()` is almost never used: most
classes use the current value of the "line.separator" property, not
the boot time value.
I would be satisfied if Maven plugins started using `BufferedWriter`s
with a hardcoded `newLine` method, but for backward compatibility
Maven could:
1. Use a separate Maven POM property (e.g.
`project.build.lineSeparator`) with alphanumeric values (e.g. `CR`,
`LF`, `CRLF`). Plugins can issue a warning if this is not set, like in
the case of `sourceEncoding`:
https://maven.apache.org/general.html#encoding-warning
2. Set the `line.separator` Java system property to the correct value
before any plugin runs: this will not modify `System.lineSeparator()`,
but will change the behavior of all `BufferedWriter`s,
3. Ignore `System.lineSeparator()` in the rare plugins that were
adapted to use it.
Piotr
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Invoker Plugin version 3.5.0
Hi, we solved 9 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12352645 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-1872/ https://repository.apache.org/content/repositories/maven-1872/org/apache/maven/plugins/maven-invoker-plugin/3.5.0/maven-invoker-plugin-3.5.0-source-release.zip Source release checksum(s): maven-invoker-plugin-3.5.0-source-release.zip sha512: a32657622fd69cd1964fbec1171175658735bb49826ebd96f7e27f9e4a87bdd477547a733736235db1284b7ebab9b5977263cf83d9d27bf88843a741f6ea2b31 Staging site: https://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/ Guide to testing staged releases: https://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 Fluido Skin version 2.0.0-M3
IMPORTANT: Requires Maven Site Plugin 4.0.0-M5 vote/staging repo! Hi, We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12352919 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluido%20Skin%22 Staging repo: https://repository.apache.org/content/repositories/maven-1871/ https://repository.apache.org/content/repositories/maven-1871/org/apache/maven/skins/maven-fluido-skin/2.0.0-M3/maven-fluido-skin-2.0.0-M3-source-release.zip Source release checksum(s): maven-fluido-skin-2.0.0-M3-source-release.zip sha512: 0c6eadcb37dcbe7a121557ca4033e2a4113ba6c2bf3367685a5949a3af829002189acd34074d4d1a417a226122cd47d19065a9915003692f1402ba908aa24136 Staging site: https://maven.apache.org/components/skins-archives/maven-fluido-skin-LATEST/ Guide to testing staged releases: https://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 Javadoc Plugin version 3.5.0
Hi, We solved 8 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12352256 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MJAVADOC/issues Staging repo: https://repository.apache.org/content/repositories/maven-1870/ https://repository.apache.org/content/repositories/maven-1870/org/apache/maven/plugins/maven-javadoc-plugin/3.5.0/maven-javadoc-plugin-3.5.0-source-release.zip Source release checksum(s): maven-javadoc-plugin-3.5.0-source-release.zip sha512: af7a5f308bdc644e130219d06eeb57ec0e08f154f4acb0131dc6a06a003737f365b1498289da2d65d747acda55583cb42b9d4c2b60312cf4033182ee739f154d Staging site: https://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ Guide to testing staged releases: https://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: GitHub release notes ...
Hi, First, with every vote for a release, there is a link for the issues fixed in Jira, but I have seen that some links to the Release Notes of Jira, and others just link to the filter of "Fix version" in Jira, to me the link should always be the Release Notes, not the filter of issues. A second point is that if Jira will be used, each Release Note has a "Copy Release Notes" that can be simply copied over. For example, the Release Notes for Maven 3.9.0 should be https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350913=12316922 (not the link for the Fix version filter), and there is nothing to "maintained" as Jira already generates the HTML in the "Copy Release Notes" section that can be used to copy/paste on the GitHub release notes, the only point is to include an additional step on the release process that every project should follow and that once the release is "done" this should be copied from Jira to GH, and that's it. Now, a third point, with some bots like dependabot, they don't create a Jira issue automatically, this might or might not be ok depending on each use case (an updated dependency could break something that should be noted in the release notes), so Jira issues fall short on tracking this kind of commits unless someone handles manually the creation of the Jira issue and that is annoying, here I don't see an easy solution since using "GH Generate release notes" or something like "Release Drafter" will differ with Jira Release Notes. In any case, since Jira is the current source of truth, the only reasonable thing to do is to simply use the "Copy Release Notes" section and include it in every release process (assuming the release process is documented somewhere). Regards, On Sun, Feb 12, 2023 at 4:15 PM Slawomir Jaranowski wrote: > > Hi, > > I know the subject is returning again ... > > When we once create GitHub release notes we should maintain it for each new > release ... > I agree the source of truth is our jira release notes. > > In other cases we have missing information about releases and users can be > confused. > > Dependabot uses GitHub releases notes for next PR and we can lose some of > the versions ... like in [1] > > For Maven 3.9.0 we also have no current release notes [2] > probably for other components ... > > [1] https://github.com/mojohaus/mojo-parent/pull/342 > [2] https://github.com/apache/maven/releases > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: GitHub release notes ...
Hi, > what about just set a link to the JIRA release notes for all GitHub release > notes. I like this minimalist approach, better than having no changes info in GitHub at all. GH release notes are very handy for update bots like renovate. Most of the time I don't see any release notes in such PRs when a Maven plugin is updated. And for some reason it is really cumbersome to find the Jira release notes yourself (e.g. you have to log in). My 2 cents. Cheers, Falko - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: GitHub release notes ...
Hi, > I agree the source of truth is our jira release notes. I'm new to maven projects here. If the quoted statement is true, what about just set a link to the JIRA release notes for all GitHub release notes. Then the task is eased and we don't maintain multiple pages with full content. ... or the issue is that the absence of release note ifself that our process can easily miss this step? Best, tison. Slawomir Jaranowski 于2023年2月12日周日 23:15写道： > Hi, > > I know the subject is returning again ... > > When we once create GitHub release notes we should maintain it for each new > release ... > I agree the source of truth is our jira release notes. > > In other cases we have missing information about releases and users can be > confused. > > Dependabot uses GitHub releases notes for next PR and we can lose some of > the versions ... like in [1] > > For Maven 3.9.0 we also have no current release notes [2] > probably for other components ... > > [1] https://github.com/mojohaus/mojo-parent/pull/342 > [2] https://github.com/apache/maven/releases > > -- > Sławomir Jaranowski >
GitHub release notes ...
Hi, I know the subject is returning again ... When we once create GitHub release notes we should maintain it for each new release ... I agree the source of truth is our jira release notes. In other cases we have missing information about releases and users can be confused. Dependabot uses GitHub releases notes for next PR and we can lose some of the versions ... like in [1] For Maven 3.9.0 we also have no current release notes [2] probably for other components ... [1] https://github.com/mojohaus/mojo-parent/pull/342 [2] https://github.com/apache/maven/releases -- Sławomir Jaranowski
Re: [VOTE] Release Maven Site Plugin version 4.0.0-M5
Am 2023-02-11 um 21:42 schrieb Michael Osipov: Hi, IMPORTANT: Requires Maven Reporting Impl 4.0.0-M4 vote/staging repo! We solved 9 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12352751 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-1869/ https://repository.apache.org/content/repositories/maven-1869/org/apache/maven/plugins/maven-site-plugin/4.0.0-M5/maven-site-plugin-4.0.0-M5-source-release.zip Source release checksum(s): maven-site-plugin-4.0.0-M5-source-release.zip sha512: 7fd11f178420756658b06ded887adf0089a20a6c44bb73f5309e99b26b144f5d3a3dab80c8aac71eb99138a052fcb92aa5721ab95e79ea0f718d09f4d23ac4a2 Staging site: https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0-M4
Am 2023-02-11 um 20:48 schrieb Michael Osipov: Hi, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352665 There are a few issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl Staging repo: https://repository.apache.org/content/repositories/maven-1868/ https://repository.apache.org/content/repositories/maven-1868/org/apache/maven/reporting/maven-reporting-impl/4.0.0-M4/maven-reporting-impl-4.0.0-M4-source-release.zip Source release checksum(s): maven-reporting-impl-4.0.0-M4-source-release.zip sha512: 32da431d8b04fc7dee338ac454c4122d39dfe6df5ba2625b657c2b82977017d2afcc3aa3ae3dbb1236e47052bd22e01b8facaa9e59d8864036bebc2034c6e67d Staging site: https://maven.apache.org/shared-archives/maven-reporting-impl-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Deploy Plugin 3.1.0
Hi, Agree with Olivier MDEPLOY-206 will be resolved by MRESOLVER-32 so should not be a part of current release notes. wt., 7 lut 2023 o 00:36 Olivier Lamy napisał(a): > +1 > But https://issues.apache.org/jira/browse/MDEPLOY-206 should not be > part of the release notes as it doesn't work yet so it's really > confusing/ > > On Mon, 6 Feb 2023 at 22:52, Tamás Cservenák wrote: > > > > Howdy, > > > > We fixed several issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317228=12352181 > > > > Staged repository: > > https://repository.apache.org/content/repositories/maven-1866/ > > > > Source release SHA512: > > > 7260610d06bff950afc07767e13a0a19ac46d68c92bd866ae18c3184089dcf50d898c01d3156907c9819805d7569203b7e6091b9b0171e255e1e6a9c8b3cdd00 > > > > Staged site: > > https://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/ > > > > Vote open for 72h > > > > Thanks > > T > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
Re: [VOTE] Apache Maven Surefire 3.0.0-M9
On Sat, 11 Feb 2023 at 20:50, Michael Osipov wrote: > > Am 2023-02-10 um 10:21 schrieb Olivier Lamy: > > Hi, > > I'd like to release Apache Maven Surefire 3.0.0-M9 > > We fixed 4 issues. > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12352730 > > > > Staging repo: https://repository.apache.org/content/repositories/maven-1867/ > > > > Staging site: https://maven.apache.org/surefire-archives/surefire-LATEST/ > > > > Source zip: > > https://repository.apache.org/content/repositories/maven-1867/org/apache/maven/surefire/surefire/3.0.0-M9/surefire-3.0.0-M9-source-release.zip > > Source directories: > > https://repository.apache.org/content/repositories/maven-1867/org/apache/maven/surefire/surefire/3.0.0-M9/ > > > > Vote open for 72H [1] > > > > > > cheers > > Olivier > > > > [1] countdown > > https://www.timeanddate.com/countdown/generic?iso=20230213T1920=47=cursive=1 > > +1 > > What about https://issues.apache.org/jira/browse/SUREFIRE-2143? > A PR is offered to fix this regression. Certainly the next train or it's never-ending restaging loop :) > > > - > 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 Surefire 3.0.0-M9
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 10.02.23 10:21, Olivier Lamy wrote: Hi, I'd like to release Apache Maven Surefire 3.0.0-M9 We fixed 4 issues. https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12352730 Staging repo: https://repository.apache.org/content/repositories/maven-1867/ Staging site: https://maven.apache.org/surefire-archives/surefire-LATEST/ Source zip: https://repository.apache.org/content/repositories/maven-1867/org/apache/maven/surefire/surefire/3.0.0-M9/surefire-3.0.0-M9-source-release.zip Source directories: https://repository.apache.org/content/repositories/maven-1867/org/apache/maven/surefire/surefire/3.0.0-M9/ Vote open for 72H [1] cheers Olivier [1] countdown https://www.timeanddate.com/countdown/generic?iso=20230213T1920=47=cursive=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
