+1
On Tue, Nov 21, 2017 at 12:05 AM, Hervé BOUTEMY
wrote:
> +1
>
> no logging in properties( cliRequest ), then no issue found when calling
> before initializing logging
>
> Regards,
>
> Hervé
>
> Le samedi 18 novembre 2017, 16:31:44 CET Robert Scholte a écrit :
> > Hi,
> >
> > MNG-6220[1] was i
+1
no logging in properties( cliRequest ), then no issue found when calling
before initializing logging
Regards,
Hervé
Le samedi 18 novembre 2017, 16:31:44 CET Robert Scholte a écrit :
> Hi,
>
> MNG-6220[1] was incomplete, which will be fixed with MNG-6296[2].
>
> Commit:
> https://git1-us-w
ping?
or give a -1 and tell me what else you expect.
On Sat, 18 Nov 2017 16:31:44 +0100, Robert Scholte
wrote:
Hi,
MNG-6220[1] was incomplete, which will be fixed with MNG-6296[2].
Commit:
https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commit;h=b2afafe5
CI:
https://build
Hi Petar,
would be great if you could pick this up.
There's enough work I want to finish first, maven-release-plugin is not
one of them right now.
thanks,
Robert
On Mon, 20 Nov 2017 18:38:56 +0100, Petar Tahchiev
wrote:
Hi Robert,
any updates on the release-aggregator? Is there anythi
Hi Robert,
any updates on the release-aggregator? Is there anything I can do to help?
2017-06-27 22:43 GMT+03:00 Robert Scholte :
> Hi Petar,
>
> This is a clear sign that ${project} should not be used to resolve this.
> Instead the pom should be analyzed again and if there's a system property
>
Github user dipak-pawar commented on the issue:
https://github.com/apache/maven-surefire/pull/169
Sure, we will be happy to move it forward. Please keep this PR open and let
us know by commenting here when it will make sense to resume the effort. I
really hope we can make it upstream.
