Problem importing litiengine as Gradle project

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-14 21:59:48
User: CalvinMT [] (age: 1451 days 🔥; posts: 114)}
Hi!
I'd love to be of more help and try out some features and ideas I've got for the LITIengine and the utiLITI (that I'll gladly share with you all, no worries ;) ), but as the title say, I'm having trouble importing the project as a Gradle project without messing up some files that I surely don't want to commit and push onto GitHub.
I've tried countless ways to solve the problem, which all comes to an error (see below) in the "Import Gradle Preview" using the "Buildship Gradle Integration 3.0" under Eclipse.
I've searched and tested for weeks and only found a command line. Something like: gradle eclipse. That command, as said above, changes some of the files to point to some user directories which I shouldn't commit.
Here's the beginning part of the error message I get:
org.gradle.tooling.GradleConnectionException: Could not create an instance of Tooling API implementation using the specified Gradle distribution 'https://services.gradle.org/distributions/gradle-5.3.1-bin.zip'. at org.gradle.tooling.internal.consumer.loader.DefaultToolingImplementationLoader.create(DefaultToolingImplementationLoader.java:95) at org.gradle.tooling.internal.consumer.loader.CachingToolingImplementationLoader.create(CachingToolingImplementationLoader.java:44) at org.gradle.tooling.internal.consumer.loader.SynchronizedToolingImplementationLoader.create(SynchronizedToolingImplementationLoader.java:43) at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.onStartAction(LazyConsumerActionExecutor.java:101) at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:83) at org.gradle.tooling.internal.consumer.connection.CancellableConsumerActionExecutor.run(CancellableConsumerActionExecutor.java:45) at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:58) at org.gradle.tooling.internal.consumer.connection.RethrowingErrorsConsumerActionExecutor.run(RethrowingErrorsConsumerActionExecutor.java:38) at org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:55) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) at java.lang.Thread.run(Thread.java:745) at org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46) at org.gradle.tooling.internal.consumer.DefaultModelBuilder.get(DefaultModelBuilder.java:50) at org.gradle.tooling.internal.consumer.DefaultProjectConnection.getModel(DefaultProjectConnection.java:41) at org.eclipse.buildship.core.internal.util.gradle.CompatProjectConnection.getModel(CompatProjectConnection.java:50) at org.eclipse.buildship.core.internal.util.gradle.IdeAttachedProjectConnection.configureOperation(IdeAttachedProjectConnection.java:64) at org.eclipse.buildship.core.internal.util.gradle.IdeAttachedProjectConnection.model(IdeAttachedProjectConnection.java:55) at org.eclipse.buildship.core.internal.util.gradle.IdeAttachedProjectConnection.getModel(IdeAttachedProjectConnection.java:82) at org.eclipse.buildship.core.internal.workspace.DefaultModelProvider.queryModel(DefaultModelProvider.java:140) at org.eclipse.buildship.core.internal.workspace.DefaultModelProvider.lambda$null$0(DefaultModelProvider.java:50) at org.eclipse.buildship.core.internal.workspace.DefaultModelProvider$$Lambda$481/528411614.apply(Unknown Source) at org.eclipse.buildship.core.internal.DefaultGradleBuild$GradleConnectionOperation.runInToolingApi(DefaultGradleBuild.java:326) at org.eclipse.buildship.core.internal.operation.DefaultToolingApiOperationManager$WorkspaceRunnableAdapter.run(DefaultToolingApiOperationManager.java:57) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322) at org.eclipse.buildship.core.internal.operation.DefaultToolingApiOperationManager.run(DefaultToolingApiOperationManager.java:38) at org.eclipse.buildship.core.internal.DefaultGradleBuild.withConnection(DefaultGradleBuild.java:119) at org.eclipse.buildship.core.internal.workspace.DefaultModelProvider.lambda$fetchModel$1(DefaultModelProvider.java:49) at org.eclipse.buildship.core.internal.workspace.DefaultModelProvider$$Lambda$480/445231130.call(Unknown Source) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:5065) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3716) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2424) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2298) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2211) at com.google.common.cache.LocalCache.get(LocalCache.java:4154) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:5060) at org.eclipse.buildship.core.internal.workspace.DefaultModelProvider.getFromCache(DefaultModelProvider.java:107) at org.eclipse.buildship.core.internal.workspace.DefaultModelProvider.executeOperation(DefaultModelProvider.java:99) at org.eclipse.buildship.core.internal.workspace.DefaultModelProvider.fetchModel(DefaultModelProvider.java:48) at org.eclipse.buildship.ui.internal.wizard.project.ProjectPreviewWizardPage.fetchBuildEnvironment(ProjectPreviewWizardPage.java:453) at org.eclipse.buildship.ui.internal.wizard.project.ProjectPreviewWizardPage.access$600(ProjectPreviewWizardPage.java:80) at org.eclipse.buildship.ui.internal.wizard.project.ProjectPreviewWizardPage$UpdatePreviewOperation.runInToolingApi(ProjectPreviewWizardPage.java:478) at org.eclipse.buildship.core.internal.operation.ToolingApiOperations$1.runInToolingApi(ToolingApiOperations.java:59) at org.eclipse.buildship.core.internal.operation.DefaultToolingApiOperationManager$WorkspaceRunnableAdapter.run(DefaultToolingApiOperationManager.java:57) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322) at org.eclipse.buildship.core.internal.operation.DefaultToolingApiOperationManager.run(DefaultToolingApiOperationManager.java:38) at org.eclipse.buildship.core.internal.operation.DefaultToolingApiOperationManager.run(DefaultToolingApiOperationManager.java:32) at org.eclipse.buildship.ui.internal.wizard.project.ProjectPreviewWizardPage$4.run(ProjectPreviewWizardPage.java:313) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) Caused by: java.lang.ExceptionInInitializerError
Now, I know I can finish the import even with this error, but I won't be able to use Gamepad inputs because Jinput wouldn't be in the libraries. And if I add it myself, I won't be able to push any commits before removing the library.
So, here are my specs:

• - Windows 10
• - Eclipse 2019-03 (4.11.0)
• - Buildship Gradle Integration 3.0 (eclipse plugin)
• - JavaSE 1.8 (jdk1.8.0_05)
  If more information is needed, please do not hesitate to ask.
  Hope someone can help. :)

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-18 16:07:45
User: CalvinMT [] (age: 1451 days 🔥; posts: 114)}
So, I continued investigating and also tried the command *.\gradlew.bat build* instead of using the Gradle Integration 3.0, which comes up with this error message:
`~~[CODE]~~17:46:48.373 [main] INFO o.g.i.n.services.NativeServices - Initialized native services in: C:\Users\me.gradle\native
FAILURE: Build failed with an exception.

• What went wrong:
  ch.qos.logback.classic.Logger cannot be cast to org.gradle.api.logging.Logger
• Try:
  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
  [/CODE]`
  It looks like there's a slight cast problem, though I looked up the "Logging.java" file in the Gradle project on GitHub and it seems intentional.
  Would someone know what to do from there, now that I know what's causing the issue?

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-19 11:33:43
User: steffen [Admin 👑, Mod 🔧] (age: 1568 days 🔥; posts: 100)}
CalvinMT I'll try to investigate this in the upcoming days.

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-20 19:16:57
User: CalvinMT [] (age: 1451 days 🔥; posts: 114)}
steffen
I downloaded the latest JDK, updated the environment variables and it builded fine. Though I still cannot import the project into eclipse because of the same error.
Would there be a workaround?
Forgot to say that I also changed Eclipse's installed JREs under ~~*~~Window->Preferences->Java->Installed JREs*.
I'm guessing it's something to do with the fact that the project is run under Java 8, which triggers Eclipse into using a compiler compliance.

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-21 18:59:50
User: pma8444 [] (age: 1335 days 🔥; posts: 16)}
Under the "Import Options", what's the latest version you can choose under the "Specific Gradle version"?
I tried to import it with 5.4.1 and it worked (also Eclipse 2019-03 and Buildship 3.0 - it even worked with an old Spring Tool Suite and Buildship 2.0).
Otherwise a workaround would be to switch to IntelliJ :D

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-21 19:17:22
User: CalvinMT [] (age: 1451 days 🔥; posts: 114)}
pma8444
I also have 5.4.1 Gradle version as being the latest selectable.
So I overrided the default setup with that version, but I still get the same error.
As for IntelliJ, I can't really put any money into it for the moment.
Thanks though. :)

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-21 21:54:02
User: CalvinMT [] (age: 1451 days 🔥; posts: 114)}
@steffen pma8444
It's done! :D
I went in the folder where I installed Eclipse (i.e.: C:\Program Files\java-2019-03\eclipse) and opened the [b]~~*~~eclipse.ini*[/b] file. In it, I replaced this line:
~~[code]~~C:\Program Files\Java\jdk1.8.0_05\jre\bin [/code]
to this line:
~~[code]~~C:\Program Files\Java\jdk-12.0.1\bin [/code]
I then right-clicked on the two project (litiengine & utiliti), clicked on [b]~~*~~properties*[/b] and went down into [b]~~*~~Java Build Path*[/b].
In there, I went to [b]~~*~~libraries*[/b], clicked on [b]~~*~~JavaSE-12*[/b] and clicked [b]~~*~~Edit...*[/b] on the right.
In the pop-up window, I chose [b]~~*~~Execution environment: JavaSE-1.8*[/b].
Clicked finish. Apply and close. And waited for the build to finish. :D
Some lines in files stored in the *.setting* folder were changed (aswell as in *.classpath* files), but I'll do my best not to commit them (if you want more details, don't hesitate to ask).
Thanks again for your help!

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-22 08:50:52
User: CalvinMT [] (age: 1451 days 🔥; posts: 114)}
@steffen
I just realized.
Shouldn't the *.classpath* files and the *.settings* folders be stated in the *.gitignore* anyway?

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-22 17:22:28
User: steffen [Admin 👑, Mod 🔧] (age: 1568 days 🔥; posts: 100)}
@CalvinMT glad you found a solution yourself! Unfortunately, I'm having a busy week so far and weren't able to check this yet...
> Shouldn't the .classpath files and the .settings folders be stated in the .gitignore anyway?
Yes and no... Eclipse likes to change things up there and in order to keep a clean working directory we usually just revert the changes on these files and it still should build just fine otherwise we sometimes had divergent results when using the engine from source.

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-05-22 17:36:41
User: pma8444 [] (age: 1335 days 🔥; posts: 16)}
> CalvinMT As for IntelliJ, I can't really put any money into it for the moment.
The community edition is free.
Having used both IDEs for a couple of years now, it feels to me like you'll have to deal with more problems like this one when using Eclipse - but to each its own :)