Hi Tibor:
So Java version is a concern.
By API version do you mean Maven API version? I believe this is controlled
with the tag inside the plugin's pom file?
An even simpler solution is to publish a "plugin compatibility matrix" page
in the web site as some companies do. Check for example Sonarqu
>> However, it seems that the only use case for upgrading the default
plugin versions is compatibility with some specific Java version?
Gabriel, Java version is not the only one reason.
There is API version as well and bug fixing.
These plugins are especially important because they are bound to th
I think I'm joining late to this thread. +1 to showing a warning message.
However, it seems that the only use case for upgrading the default plugin
versions is compatibility with some specific Java version?
How about developing a plugin that "recommends" specific plugin versions
based on the sour
Introducing a new parent might help for some, but not for everybody.
If you already have a parent specified, you can't use this.
And Maven doesn't support mixins (yet).
We need to document how plugins are controlled.
These are probably all variants I can think of
- pom.xml
- via packaging-plugin
I've removed the invokerPublisher() calls in our Jenkins scripts, this
seems to be the cause of the hanging Java processes.
Within a couple of hours I expect all Windows nodes to be restarted by
INFRA and then we should be good again.
thanks,
Robert
On Sat, 12 Jan 2019 09:23:20 +0100, Tibor
Looks good to me.
+1
On Mon, 14 Jan 2019 16:27:43 +0100, Hervé BOUTEMY
wrote:
Hi,
I worked with Mickael on his PR and we came to MNG-6533-2 branch:
https://github.com/apache/maven/tree/MNG-6533-2
for MNG-6533 https://issues.apache.org/jira/browse/MNG-6533
Seconders to merge to master?
Hi,
I worked with Mickael on his PR and we came to MNG-6533-2 branch:
https://github.com/apache/maven/tree/MNG-6533-2
for MNG-6533 https://issues.apache.org/jira/browse/MNG-6533
Seconders to merge to master?
Regards,
Hervé
PR also created :)
https://github.com/apache/maven/pull/233
Le lundi 14 janvier 2019, 12:06:40 CET Hervé BOUTEMY a écrit :
> MNG-6562 Jira issue [1] and Git branch [2] created: please review and
> comment
>
> I'll start to work on the new parent POM that locks down versions of plugins
> from defa
MNG-6562 Jira issue [1] and Git branch [2] created: please review and comment
I'll start to work on the new parent POM that locks down versions of plugins
from default lifecycle bindings: see MPOM-215 [3]
I'll do it in a personal GitHub git repo first while we choose the final name:
maven-defaul
