Le 10/10/2019 à 19:28, Hervé BOUTEMY a écrit :
> the only little mis-interpretation is that it is a pure build information,
> then I don't see why this property would appear in a consumer POM
Thank you for the clarification, that makes perfectly sense. And I now
see the benefit of using a
Le jeudi 10 octobre 2019 17:17:07 CEST, vous avez écrit :
> Hi Hervé,
>
> >> - We already have maven.build.timestamp [1], so I wonder whether it
> >> should be maven.build.outputTimestap, too. Although one may argue that
> >> this *output* timestamp is a property of the project being built, not
>
Hello,
I just faced a problem here using maven 3.6.1 and java11. The
compiler-plugin is assuming the classifier of a declared
annotationProcessorPath as "processor".
I've set my pom using this:
>
>
>
> maven-compiler-plugin
>
I have to try to merge the fix because it avoids a situation when the VM
hanged. It is very important for the users.
The remaining fixes may go to M5.
I will adjust Jira release notes, oki?
I have time to cut the release, no problem. The only problem was to find
some spare time for coding the
Hello,
By looking at this over the internet I don't find much informations.
Apparently the sole reliable way to configure proxy usage is trough
".m2/settings.xml" which annoys me when using CI/CD and docker behind proxies.
We do set standard environment variables for proxies in the builds that
We can release now 3.0.0-M4 and then release later with your remaining
fixes/new features.
As far I know we do not have a fix release content we can easily move the
remaining fixes to a 3.0.0-M5
I'm happy to release it myself if you don't have time.
On Thu, 10 Oct 2019 at 21:11, Tibor Digana
I understood the wish from JUnit5 fans e.g. Olivier Lamy but still we have
important fixes for the stability and it is hard to find new developers.
I was thinking about this release/3.0.0-M4 and adding one more milestone
too but there is fix on my PC that I have a problem to merge without new
