Skip to content

Latest commit

 

History

History
67 lines (43 loc) · 3.41 KB

installation.md

File metadata and controls

67 lines (43 loc) · 3.41 KB
title
Installation & Getting Started with Bndtools 7.0.0

There are different flavors you can install Bndtools.

Users: If you just want to use Bndtools for your own projects

Developers: If you want to contribute to bndtools

<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/Ry6XNGm7C-k" frameborder="1" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

To get then started with the bndtools Workspace model, you can follow some videos that can get you started.

Marketplace

The recommended way to install Bndtools via the Eclipse Marketplace.

Drag to your running Eclipse* workspace. *Requires Eclipse Marketplace Client

Update Site

  • From the Help menu select Install New Software...
  • When the dialog opens, click the Add... button near the top-right.
  • In the Name field enter Bndtools. In the Location field enter one of the the following P2 Repository URLs
Type URL alt. URL
Latest stable release https://bndtools.org/bndtools.p2.repo/7.0.0/ via jfrog
Latest release candidate https://bndtools.jfrog.io/bndtools/update-rc
Latest build snapshot https://bndtools.jfrog.io/bndtools/update-snapshot
  • Press Next and then Finish, acknowledging the licenses

Getting Started

To get started with Bnd/Bndtools we recommend:

Release Notes

For more complete information on the changes in the Bndtools release, see https://github.com/bndtools/bnd/wiki#release-notes.

Known Issues

  • Bndtools is built to run on Eclipse 2020-06 or later. So Bndtools 7.0.0 may not run on older versions of Eclipse.

  • This release is based on Java 17. This tends to be not noticed for developmet but there are a number of runtime bundles in the distribution that now also have become Java 17 code. This could generate the error during a bndrun launch or with bnd/OSGi testing when the Execution Environment is set to < 17. The easy fix is to set this to 17. If this is impossible, the previous launchers than run on 1.8 can then be used (if they are available in the repositories). Add

-runpath \
    biz.aQute.launcher;version="[6.4.0,7)", \
    biz.aQute.tester.junit-platform;version="[6.4.0,7)"