Am 01/12/17 um 01:32 schrieb Stephen Connolly:
> Well now after several repeats still no sign of the failure when running
> with -llr
Would be great if it has become reproducible by that. I wonder why it
succeeded several times without that change. What so ever. All it needs
is to stop failing eve
No that is not quite what I am saying...
I'll respond in detail later
On Thu 12 Jan 2017 at 20:32, Christian Schulte wrote:
> Am 12.01.2017 um 12:09 schrieb Robert Scholte:
>
> > On Thu, 12 Jan 2017 09:00:16 +0100, Hervé BOUTEMY >
>
> > wrote:
>
> >
>
> >> Do we agree on the initial explanation
Am 12.01.2017 um 12:09 schrieb Robert Scholte:
> On Thu, 12 Jan 2017 09:00:16 +0100, Hervé BOUTEMY
> wrote:
>
>> Do we agree on the initial explanation about the plugin runtime
>> resolution hack?
>
> The first thing Maven does is create a BuildPlan. This means that the
> plugins being par
Hello Everyone
This email is to tell you about ASF participation at FOSDEM. The event
will be held in Brussels on 4^th & 5^th February 2017 and we are hoping
that many people from our ASF projects will be there.
https://fosdem.org/2017/
Attending FOSDEM is completely free and the ASF will ag
That's in JIRA of course, poms need to be updated.
On Thu, 12 Jan 2017 12:47:48 +0100, Robert Scholte
wrote:
to change the version to 3.5.1 in the pom
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additio
It's always hard to predict the next version. I would expect it to be 3.6,
until we received a bug report[1], which made me decide to change the
version to 3.5.1 in the pom with the idea to do a release soon.
This also brings me to another point: could somebody second MNG-6109[2]
for M3.5.0,
On Thu, 12 Jan 2017 09:00:16 +0100, Hervé BOUTEMY
wrote:
Do we agree on the initial explanation about the plugin runtime
resolution hack?
The first thing Maven does is create a BuildPlan. This means that the
plugins being part of this run are initiated. This is also the reason why
a ma
I'm not ok with the "maven baseline" approach: IMHO, there is no such thing
during plugin dependencies resolution.
AFAIK, plugin dependencies resolution happens "normally" (or more precisely
with the current hack for test or provided scoped dependencies), then when
plugin "classpath" creation h
