>From my tests looks like a problem with closing PrintStream in JAnsi 1.17.
Sylwester
wt., 27 lut 2018 o 19:21 użytkownik Guillaume Boué
napisał:
> (Made a mistake and only sent this to Stephen... sorry)
>
> I've found a very small regression, but definitely not a blocker for the
> release I th
+1
No problem found on my side (but light tests)
On Tue, Feb 27, 2018 at 10:31 PM, Olivier Lamy wrote:
> +1
> Thanks to take care of this release!
>
>
> On Wed, 28 Feb 2018 at 7:03 am, Guillaume Boué wrote:
>
> > +1
> >
> > Can make a JIRA for this after the release.
> >
> >
> > Le 27/02/2018 à
+1
Thanks to take care of this release!
On Wed, 28 Feb 2018 at 7:03 am, Guillaume Boué wrote:
> +1
>
> Can make a JIRA for this after the release.
>
>
> Le 27/02/2018 à 19:21, Guillaume Boué a écrit :
> > (Made a mistake and only sent this to Stephen... sorry)
> >
> > I've found a very small re
+1
Can make a JIRA for this after the release.
Le 27/02/2018 à 19:21, Guillaume Boué a écrit :
(Made a mistake and only sent this to Stephen... sorry)
I've found a very small regression, but definitely not a blocker for
the release I think. When the following is ran:
mvn org.apache.maven.p
Sent from my iPhone
Begin forwarded message:
> From: Guillaume Boué
> Date: 27 February 2018 at 18:00:29 GMT
> To: Stephen Connolly
> Subject: Re: [VOTE] Release Apache Maven 3.5.3
>
> I've found a very small regression, but definitely not a blocker for the
> release I think. When the follo
(Made a mistake and only sent this to Stephen... sorry)
I've found a very small regression, but definitely not a blocker for the
release I think. When the following is ran:
mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate
There is a spurious "[0m[0m" at the very last line
Hi all,
I believe my usage of antrun is legit to make sure user who is using mvn
install ( without clean) has a proper clean up before another plugin
execution
org.apache.maven.plugins
maven-antrun-plugin
work.around.to.clean.up.classes.befo
On 27 February 2018 at 14:46, Mirko Friedenhagen
wrote:
> +1 from my side, tested with 10 inhouse projects. Or is this vote canceled?
>
Not cancelled yet. Unclear if Dan's issue is something forking maven and
parsing the output... the task name
"work.around.to.clean.up.classes.before.jsonschema.
Hi,
tested with several projects working the last day with it...No issues..
So +1 from me.
Kind regards
Karl Heinz Marbaise
On 24/02/18 23:00, Stephen Connolly wrote:
Hi,
We solved 22 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341428&styleName=Text&projectId=1231
+1 from my side, tested with 10 inhouse projects. Or is this vote canceled?
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran wrote:
> correction
>
> found this reference
On Mon 26 Feb 2018 at 20:55, Tibor Digana wrote:
> Hi Enrico,
>
> I do not like this test because this may easily be against Java Prog. Lang.
> Spec.
> I have no idea why Kristian created like this and allowed testing non-ASCII
> characters in Java test method and Java test class.
> Here are Japa
11 matches
Mail list logo