[
https://issues.apache.org/jira/browse/TINKERPOP-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085736#comment-17085736
]
Marc de Lignie commented on TINKERPOP-2335:
-------------------------------------------
Can I bother you once more on this one. I still have problems with
"{{docker/build.sh -d"}} after your recent patch. Maven inside docker crashes
on the wrong JAVA_HOME. I can only get maven start building in docker if I add
"{color:#0073bf}export {color}JAVA_HOME=/usr/lib/jvm/java-8-oracle/jre" to
docker/script/build.sh. What is going on here, how can it work for you?
Before all this, the .travis.install-maven.sh, called from
docker/build/Dockerfile.template, prints to the console during a run:
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T16:41:47+00:00)
Maven home: /root/mvn-home
Java version: 1.8.0_111, vendor: Oracle Corporation
Java home: {color:#de350b}*/usr/lib/jvm/java-8-oracle/jre*{color}
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "4.15.0-96-generic", arch: "amd64", family: "unix"
So, I guess this maven install gets the wrong JAVA_HOME already.
> Drop support for older GLV runtimes
> -----------------------------------
>
> Key: TINKERPOP-2335
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2335
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet, javascript, python
> Reporter: Jorge Bay
> Priority: Major
> Fix For: 3.5.0
>
>
> As [discussed on the mailing
> list|https://lists.apache.org/thread.html/r25901cdb66b913b32b025970a6cd435eae87609e5c5af3c8a4ce630a%40%3Cdev.tinkerpop.apache.org%3E],
> we should take the opportunity of the new revision to drop support for EOL'd
> runtimes for javascript, python and .NET.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
