Hello,
Only lurking those days, but chiming in quickly here :-).
2017-09-10 20:54 GMT+02:00 Robert Scholte :
> On Sun, 10 Sep 2017 20:21:11 +0200, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> On Sun 10 Sep 2017 at 19:04, Tibor Digana
Robert,
>>And if we're focusing on the latter, shouldn't the twitter question be
Good remark! I am not against such question on Twitter but I would be
interested in one more in comparison to Gradle.
*What the Maven should improve to make Maven more attractive against
Gradle?*
Because I don't
On Sun, 10 Sep 2017 20:21:11 +0200, Stephen Connolly
wrote:
On Sun 10 Sep 2017 at 19:04, Tibor Digana wrote:
Hi All,
Are we facing new API regarding networking and security useful in Java
8?
When I first saw these options I
Stephen,
I was pragmatic and did not want to push users to use Maven only
because JDK 7 is weak.
First the interest should go from inside, this means API and then users.
I agree with Michael whether we should better focus on Maven 4 and POM
structure.
For instance today everybody could notice
Am 2017-09-10 um 19:07 schrieb Stephen Connolly:
Hervé and I discussed on irc earlier today.
My suggestion - I was going to write up tomorrow - is that we drop 7 for
3.6.x
We should focus 3.6.x on making the codebase Java 8 (lambdas, replace
FileStream with the non-file handle leak
On Sun 10 Sep 2017 at 19:04, Tibor Digana wrote:
> Hi All,
>
> Are we facing new API regarding networking and security useful in Java 8?
>
> When I first saw these options I asked myself what benefit would have the
> User and Jenkins from Java 8.
> And second question was
Hi All,
Are we facing new API regarding networking and security useful in Java 8?
When I first saw these options I asked myself what benefit would have the
User and Jenkins from Java 8.
And second question was whether we would be so flexible to rewrite the code
and use Lambda fully anywhere in
Hervé and I discussed on irc earlier today.
My suggestion - I was going to write up tomorrow - is that we drop 7 for
3.6.x
We should focus 3.6.x on making the codebase Java 8 (lambdas, replace
FileStream with the non-file handle leak version, adopt Path, etc) with
a view to encourage
But on twitter thus probably far from being a good representation of our
users ...
Le dim. 10 sept. 2017 à 18:45, Gary Gregory a
écrit :
> On Sep 10, 2017 10:33, "Robert Scholte" wrote:
>
> So what would be the conclusion?
>
> 35% want to keep
On Sep 10, 2017 10:33, "Robert Scholte" wrote:
So what would be the conclusion?
35% want to keep Java7 as JRE for Maven for a shorter or longer period?
IMHO that's a lot
but less than the 65% who do not, an overwhelming majority.
Gary
Robert
On Sun, 10 Sep 2017
So what would be the conclusion?
35% want to keep Java7 as JRE for Maven for a shorter or longer period?
IMHO that's a lot
Robert
On Sun, 10 Sep 2017 11:55:20 +0200, Stephen Connolly
wrote:
So poll results:
493 votes cast
25% want Java 7,8&9 for Maven
So poll results:
493 votes cast
25% want Java 7,8&9 for Maven 3.6.x
65% want Java 8&9 for Maven 3.6.x
10% want Java 8&9 for Maven 3.6.x and 6 months of backporting to 3.5.x
On Sat 9 Sep 2017 at 11:50, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
12 matches
Mail list logo