Improve Eclipse WTP support in Gradle 3, HowTo?

Help/Discuss
,
21

Buildship should only call cleanEclipseWtp, nothing else.

22

But now itā€™s not deleting .settings folder any more. Interesting not?

23

Well, does it delete .settings when you re-add your custom task?

24

Yes:

  • adding it back
  • removing the projects from eclipse
  • running from command line: gradlew.bat cleanEclipse cleanEclipseCustom
  • try to import the project into Eclipse using Existing Gradle Project
  • Result:
    error.jpg732Ɨ48 7.64 KB
25

Well of course itā€™s gone if you explicitly call your clean task. Why do you do that?

26

I donā€™t know how this can be misunderstood.
If I clean a project completely and start a fresh export I expect, that it creates alle Eclipse Workspace files. Is this expectation false?
So After Step 4 in my previous posting it should have new .settings folder but it has not.

27

Next Test:

I renamed the task to something differentā€¦ .settings folder still get removed during import.

allprojects {
	apply plugin: 'eclipse'

	group = 'de.pentos'
	version = '1.0.2'

	task cEC {
		delete '.settings'
		delete 'bin'
		delete 'build'
	}
}

Then I removed it completely

allprojects {
	apply plugin: 'eclipse'

	group = 'de.pentos'
	version = '1.0.2'

}

Now the import works fine

28

Your snippet is calling Project.delete at configuration time. You forgot to specify the type of the task:

task customClean(type:Delete) {
	delete '.settings'
        delete 'bin'
	delete 'build'
}
29

:hushed: Ups, my mistake.
So there is no error with deleting .settings, but the project still has the wrong facet with BuildShip 2