Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

currently unable to build java-tron with JDK 8 #802

Closed
javatanu opened this issue May 21, 2018 · 10 comments
Closed

currently unable to build java-tron with JDK 8 #802

javatanu opened this issue May 21, 2018 · 10 comments
Labels
topic: Build compile error, jitpack

Comments

@javatanu
Copy link

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If possible, provide a recipe for reproducing the error.
    1.Installing java8 showing version
    java version "1.8.0_161"
    Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
    Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
    2.then clone java-tron from github
    3.then checkout branch master
    4.pull project from master branch
    5.try to run ./gradlew run

  2. What did you expect to see?

Building Successfully

  1. What did you see instead?
    89% build then no result found.Sometime got an error that build is failure.Try to use ./gradlew clean then ./gradlew build but build is not finishing
@bondibox
Copy link

bondibox commented May 21, 2018

If you are using Ubuntu this is a reported problem but one which no one is taking responsibility for. Yes, it stalls at Test number 72 with 26 failed tests. My guess is there are 300 libraries that gradle imports and many of them are gettting updated every few days. Sometimes the updates are incompatible with the java-tron build.

@kaankozan
Copy link

which system should I use
You are using ubuntu @bondibox

@bondibox
Copy link

bondibox commented May 21, 2018

kaankozan I'm not using anything until someone figures out what the problem is with Ubuntu. It builds fine on Mac os if you're dying to get it running.

@TurkishMagikarp
Copy link

Isnt there a way to have fixed versions of the imports that Gradle does? You can easily set that up in the Gradle properties? The ones that are known to be supported at all versions could be coded dynamically whereas the ones where the we don't know if the versions following will work could be hardcoded.

@javatanu
Copy link
Author

javatanu commented May 22, 2018 via email

@javatanu
Copy link
Author

javatanu commented May 22, 2018 via email

@javatanu
Copy link
Author

screenshot from 2018-05-22 11-49-11

@bondibox
Copy link

Isnt there a way to have fixed versions of the imports that Gradle does?

They have frozen to a very stable gradle release. I don't know how the hierarchy of these things works, but it would seem to me that gradle is alone in specifying which versions of its helpers it will retrieve. We know that gradle has to maintain the 300 helper dependencies - it seems like an enormous added burden for th Tron team to start tracking them too.

@bondibox
Copy link

Problem Solved.
#788
For the time being, using a 2 core CPU will fix it.

@kaankozan
Copy link

Close comment pls @bondibox say it #788

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: Build compile error, jitpack
Projects
None yet
Development

No branches or pull requests

6 participants
@bondibox @olenheim @TurkishMagikarp @kaankozan @javatanu and others