Am 2018-05-07 um 23:27 schrieb Robert Scholte:
On Mon, 07 May 2018 23:14:18 +0200, Michael Osipov
wrote:
Am 2018-05-07 um 22:40 schrieb Robert Scholte:
That's indeed better.
Maybe a comment that when Maven requires Java9 it could be reverted
to "Java Home"?
Maybe, but still remains not te
Am 2018-05-07 um 22:40 schrieb Robert Scholte:
That's indeed better.
Maybe a comment that when Maven requires Java9 it could be reverted to
"Java Home"?
Maybe, but still remains not technically Java, but the bundled JRE as
Oracle documents and can be confused with JAVA_HOME.
What about this
That's indeed better.
Maybe a comment that when Maven requires Java9 it could be reverted to
"Java Home"?
Robert
On Mon, 07 May 2018 22:30:51 +0200, Michael Osipov
wrote:
Am 2018-05-07 um 21:46 schrieb Robert Scholte:
I understand the fix, but it'll be no issue anymore with Java 9+
I
Am 2018-05-07 um 21:46 schrieb Robert Scholte:
I understand the fix, but it'll be no issue anymore with Java 9+
I have my doubts about "used"? "JRE used" could also refer to a version.
This is actually the JRE *location*, but that's quite long
"JRE Home"?
Or just do a Java check and only adjust
I understand the fix, but it'll be no issue anymore with Java 9+
I have my doubts about "used"? "JRE used" could also refer to a version.
This is actually the JRE *location*, but that's quite long
"JRE Home"?
Or just do a Java check and only adjust it for Java 8 and before.
In the end it really i
+1
On Sat 5 May 2018 at 23:11, Michael Osipov wrote:
> Hi folks,
>
> who seconds MNG-5756 for 3.5.4? Several folks complain that "mvn -v"
> does not correspond to the reality, therefore two PRs have been created.
> I have just changed the output to "JRE used:" instead of "Java home:".
>
> Michae
Hi folks,
who seconds MNG-5756 for 3.5.4? Several folks complain that "mvn -v"
does not correspond to the reality, therefore two PRs have been created.
I have just changed the output to "JRE used:" instead of "Java home:".
Michael
--
