Le dimanche 13 janvier 2019, 21:18:28 CET Robert Scholte a écrit :
> On Sun, 13 Jan 2019 21:03:20 +0100, Hervé BOUTEMY
>
> wrote:
> > Le dimanche 13 janvier 2019, 20:22:15 CET Robert Scholte a écrit :
> >> On Sun, 13 Jan 2019 18:48:29 +0100, Hervé BOUTEMY
> >>
> >>
> >> wrote:
> >> > Le dimanch
On Sun, 13 Jan 2019 21:03:20 +0100, Hervé BOUTEMY
wrote:
Le dimanche 13 janvier 2019, 20:22:15 CET Robert Scholte a écrit :
On Sun, 13 Jan 2019 18:48:29 +0100, Hervé BOUTEMY
wrote:
> Le dimanche 13 janvier 2019, 11:37:43 CET Robert Scholte a écrit :
>> This is indeed a good approach.
>>
Le dimanche 13 janvier 2019, 20:22:15 CET Robert Scholte a écrit :
> On Sun, 13 Jan 2019 18:48:29 +0100, Hervé BOUTEMY
>
> wrote:
> > Le dimanche 13 janvier 2019, 11:37:43 CET Robert Scholte a écrit :
> >> This is indeed a good approach.
> >> The first group doesn't care about this warning, the s
Le dimanche 13 janvier 2019, 20:21:07 CET Tibor Digana a écrit :
> Herve, and only those two plugins would appear in the Warning?
yes, we can do that if we want: you'll see that soon in MNG-6562 branch that I
will push
> Reading StephenC email, this reminds me to think of an algorithm which
> dow
I would say: we need to externalize this configuration.
It should be possible to create a jar-file with a minimum pom, but Maven
should know which plugin belongs to which packaging. So we always need to
have this mapping, and it would make it easier for custom packaging types
to register th
On Sun, 13 Jan 2019 18:48:29 +0100, Hervé BOUTEMY
wrote:
Le dimanche 13 janvier 2019, 11:37:43 CET Robert Scholte a écrit :
This is indeed a good approach.
The first group doesn't care about this warning, the second one should.
Hervé, can you confirm that in case of *only* specifying the la
Herve, and only those two plugins would appear in the Warning?
Reading StephenC email, this reminds me to think of an algorithm which
downloads the latest version for these two plugins from Maven Central. Here
the question is; Do we need to use default bindings in lifecycle plugin
online builds?
O
Le dimanche 13 janvier 2019, 11:37:43 CET Robert Scholte a écrit :
> This is indeed a good approach.
> The first group doesn't care about this warning, the second one should.
>
> Hervé, can you confirm that in case of *only* specifying the latest
> maven-jar-plugin or maven-war-plugin or other pac
thank you for the improved message: yes, we'll need help to define the right
message since it will be seen by many many users who are quite new to Maven...
To help on plugins upgrade, there is versions:display-plugin-updates
https://www.mojohaus.org/versions-maven-plugin/display-plugin-updates-mo
Il dom 13 gen 2019, 12:53 Stephen Connolly
ha scritto:
> I think where we want to go is warnings and no version injected. Thus if
> you ignore the warnings you get latest version always *and* we don’t have
> to update the versions ever. ;-)
>
> Add a CLI option to fail if versions unspecified.
>
I think where we want to go is warnings and no version injected. Thus if
you ignore the warnings you get latest version always *and* we don’t have
to update the versions ever. ;-)
Add a CLI option to fail if versions unspecified.
Start publishing base parent poms defining a profile of plugin vers
This is my view on it in the following order:
- Improve warning regarding default lifecycle bindings
- update plugin versions
- support failOnWarning[1] . This one hasn't been mentioned yet, but it
seems like some are still concerned about warnings not being read despite
the colors. Now Maven
Robert, your email still was not totally concrete.
I understand it like this; the warnings proposed by Herve been introduced
in the nearest version 3.6.x, and an update of default bindings in 3.7.0.
Do we understand it in the same roadmap?
In my experiences, developers do not read warnings because
This is indeed a good approach.
The first group doesn't care about this warning, the second one should.
Hervé, can you confirm that in case of *only* specifying the latest
maven-jar-plugin or maven-war-plugin or other packaging plugin, you won't
get these warnings.
It really matters where the
14 matches
Mail list logo
