On 10/03/17 00:29, Stephen Connolly wrote:
How are we doing?
Are we ready to freeze?
Can we wait until monday..
I would like to integrate MNG-6170 (which is ready) and currently
working on IT's for MNG-6057, MNG-6090, MNG-5895 which I would like to
integrate into 3.5.0-alpha-2...
So I can work on the IT's over the weekend...
(Unfortunately I can't take a look into JIRA at the moment seemed to
unavailable currently; INFRA knows already about it.)...
Kind regards
Karl Heinz Marbaise
On Sat 4 Mar 2017 at 19:40, Christian Schulte <[email protected]> wrote:
Am 03/04/17 um 18:54 schrieb Hervé BOUTEMY:
I have one question, which is recurring for every issue: what is the
impact?
I understand the logic: it should fix a bug (that is told introduced in
Maven
3.3.1), and the bug is explained by the logic behind the javadoc.
But no pointer to any code using this method, and that shows that Maven
3.3.1
does not work any more, when previous version were ok.
Then what is explained here as a bugfix could cause issues for others.
I'm -1 unless I have some details on the impact
Please see the linked issues. The reporter did a great job finding out
about when the issue got introduced. His findings are consistent with
<https://issues.apache.org/jira/browse/MNG-5775>
and his analysis also is consistent with
<https://issues.apache.org/jira/browse/MNG-5582>
What impact the changes have, I cannot tell. That's why we should take
this to JIRA.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Sent from my phone
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
