Basic build scans support
- Build scans can be activated from the workspace preferences, from the project preferences, and from the run configurations
- Executions view has toolbar action to open a published build scan
- Build scan URL is transformed to clickable link in the console output
Reworked preferences
- Added support for overridable preference hierarchy
-
New, consistent preference UI defined for
- workspace preferences
- project preferences
- run configurations
Enhancements
- Task and Executions view show headers by default
- Executions view performance increased
Compatibility with Gradle
As with all previous versions, Buildship can work with all Gradle versions supported by the Gradle Tooling API module. This release uses the 4.0 version of that module which supports Gradle 1.2+ versions and provides forward compatibility with future releases.
Compatibility with other Buildship versions
This release works seamlessly with workspaces set up by any previous Buildship 2.x versions.
Since some external projects generate Buildship configuration files, we should mention here that we've done some adjustments regarding that. We removed the duplicate key-value pairs from the projects so that now all import preferences are stored on the root project. The existing subproject configurations are ignored by Buildship 2.1.0.
API Compatibility
There were no changes in the exposed API since the previous 2.x releases.
The minimum runtime Java version for Buildship 2.1.0 is 1.7, as the Gradle Tooling API has the same requirement. Buildship supports Eclipse 4.2 (Juno) and above.
Bugfixes
Enhancements
New features