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

Changes in 3.2.0

BJ Hargrave edited this page May 17, 2016 · 9 revisions

Bndtools 3.2.0

For Bnd 3.2.0 changes, see https://github.com/bndtools/bnd/wiki/Changes-in-3.2.0.

New Workspace Wizard

The process for creating and configuring a new Bndtools Workspace has been improved, and now makes use of the new-style templating system that was introduced in version 3.1. This means that templates can now be delivered via repositories rather than executable code that had to be installed as plugins into your Eclipse IDE.

Additionally, templates can be fetched directly from a remote Git or GitHub repository. The list of available repositories can be edited via the Eclipse Preferences window.

Whereas the old wizard was only able to output content into the cnf folder, the new templates can output anywhere into the project. This enables them to deliver files that may be needed by a build system (e.g. build.gradle).

Initialisation Steps

The New Workspace wizard can be manually invoked by the user from the File -> New menu. When starting a fresh workspace, you are recommended to run this wizard first.

If you do create a bnd project before creating the workspace, a build error will occur. However, you can use Quick Fixes to initiate the New Workspace wizard directly from that build error. To select the Quick Fix, do one of the following:

  • Find the error in the Eclipse Problems view, right-click and select Quick Fix (or Ctrl-1/Cmd-1).

OR

  • Open the bnd.bnd file for the project. The Build page will display the error at the top. Click the error message and select the fix from the popup.

Other Notable Changes

  • Baseline version errors are now reported on package-info.java, and the Quick Fix to bump the version can be applied directly from the Java editor for package-info.java.
  • Templates can now use the Mustache templating engine. Set the attribute engine=mustache in your template capability to select this engine. To get started, generate a new template project using the "Project Template Project (Mustache)". (NB: to use StringTemplate set engine=stringtemplate... or just leave this attribute undefined, since StringTemplate remains the default).
  • The option to create projects with the "Maven Layout" (i.e. sources under src/main/java/ and src/test/java/ rather than src/ and test/) has been removed. With the template system it is now much simpler to create templates that support any desired layout.

Backwards compatibility

  • None.

Known Issues

  • None at this time.