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
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
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!
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
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
+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:
>
