Skip to content
This repository has been archived by the owner on Jul 9, 2022. It is now read-only.

Fail to initialize EclipseModelBuilder in gradle 2.14.1 if "Use Custom Tooling Model" is checked. #105

Open
aya-eiya opened this issue Jul 26, 2016 · 4 comments

Comments

@aya-eiya
Copy link

Failed to fetch 'EclipseProject' model due to EclipseModelBuilder constructor argument number change.

spring-projects/eclipse-integration-gradle - version 3.8.0
StsEclipseProjectModelBuilder

gradle/gradle version 2.14.1
EclipseModelBuilder

error message:

org.gradle.plugins.ide.internal.tooling.EclipseModelBuilder.<init>(Lorg/gradle/plugins/ide/internal/tooling/GradleProjectBuilder;)V
Could not fetch model of type 'EclipseProject' using Gradle distribution 'https://services.gradle.org/distributions/gradle-2.14.1-bin.zip'.
@kdvolder
Copy link
Contributor

Couldn't reproduce. I created a basic gradle project, added gradle wrapper for version 2.14.1 and imported it. It worked fine for me.

You will need to provide more details. Best would be a sample project and exact details on what options you select in the import wizard.

At first glance, everything is working right. So I'll close ticket for now. Add more details and we can reopen it.

@aya-eiya
Copy link
Author

aya-eiya commented Jul 27, 2016

I found this occurs only in case the option "Use Custom Tooling Model" is checked.

@aya-eiya aya-eiya changed the title Fail to initialize EclipseModelBuilder in gradle 2.14.1 Fail to initialize EclipseModelBuilder in gradle 2.14.1 if "Use Custom Tooling Model" is checked. Jul 27, 2016
@kdvolder
Copy link
Contributor

Thanks, I will reopen it. But it is unlikely we will fix it. The custom tooling always was a rather experimental feature and has proven to be a bit too big of a maintenance burden. Perhaps its a small fix, and maybe someone will step forward with a pull-request.

@kdvolder kdvolder reopened this Jul 27, 2016
@kdvolder
Copy link
Contributor

BTW: some of the problems that the custom tooling model was intended to solve are handled better by BuildShip which eventually will replace STS gradle tooling. So perhaps using BuildShip is an option for you. If not please consider raising the issue via Eclipse bugzilla so that BuildShip developers might try to address it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants