I would agree with Elliotte here. If someone creates a patch for Maven 2.2.x,
he or she should just branch from the old tag and have all ITs available at
that point of time.
Keeping tests and mark them as to be skipped for newer versions is strange.
After reading Tibor’s comment:
* Tibor just
I’m still working on fixing an issue for aggregated javadoc with jmps and
java11
I hope to get this fix for the weekend but if not go ahead and release
I can release again once I get the fix
On Tue, 17 Dec 2019 at 5:18 pm, Hervé BOUTEMY wrote:
> I would like to release Apache parent POM this WE
+1 please go ahead
Enrico
Il giorno mar 17 dic 2019 alle ore 08:18 Hervé BOUTEMY <
herve.bout...@free.fr> ha scritto:
> I would like to release Apache parent POM this WE (then Maven parent
> POMs),
> with plugin versions that support Reproducible Builds
>
> The last plugin to upgrade is
Hi,
Some points:
In my experience upgrading Maven has never been a problem (thanks to the
great attention we pay to backward compatibility)
Maven versioning scheme is very unusual and I suppose that people really
don't care about it or even they can't understand. Maven version is useful
only to
I forgot to mention:
notice that thanks to maven-release-plugin 3.0.0-M1, the
project.build.outputTimestamp property was automatically updated 2 times during
the release:
- [1] during the release preparation phase
- [2] when preparing next development iteration
We have now the expected
