Buildship leads to a clean build on every startup

issue-resolved

(Stefan Oehme) #1

The Gradle Dependency Container is currently removed and re-added when starting Eclipse. The removal triggers the autobuild, which starts recompiling. Of course since all dependencies are missing now, all files will be broken. Then when the classpath is re-added, everything is recompiled again. On our code base this means opening the workspace takes an extra 10 minutes. This is preventing us from finally moving to Buildship.

Buildship should cache the last known state of the dependency container and update it in the background without removing it completely.


(Etienne Studer) #2

Hi Stefan.
Yes, this is already on our list of things to optimize. We want to tackle this soon.
Etienne


(Donát Csikós) #3

This issue has been fixed in Buildship and will be released next week. If you want to evaluate you can install the latest milestone build from the following update site: http://download.eclipse.org/buildship/updates/e45/milestones/1.0/1.0.10.v20160309-1150-m
We appreciate any feedback.