Guide Services Links Forum
Before you start any of the tutorials you must prepare your environment so that the right tools are installed. This page helps you to achieve this. We need to run the following tools on your computer:
In general you should install the bndtools from either the Eclipse Marketplace or, if you’re a bit more adventurous, from the Milestone update. However, since this site is in beta, it is best to install the continuous build version. Once we’re out of beta, we will make sure there is always a good version in the market place. The URL for the continuous build is:
https://bndtools.ci.cloudbees.com/job/bndtools.master/lastSuccessfulBuild/artifact/build/generated/p2/
You can find the details how to install bndtools on the bndtools website:
http://bndtools.org/installation.html#update-site
Whenever you see a text like File/Open we hope you treat it as a menu path. That is, go to the menu bar, click on File, then select Open. If the menu path starts with @/ then it is from the context menu on the selected object, which has then been clearly defined in the previous sentence.
Since this part is rather sensitive to the operating system you’re using, we have split it in different sections for each of the major operating systems.
In the enRoute tutorials file paths are always indicated using the forward slash or solidus (‘/’) as is customary on *nix like systems. The reason is that bnd, since its files are portable, always uses relative addressing from the workspace and adopted the forward slash. For most developers mapping these paths to Windows should be straightforward.
The only addressing outside the workspace is to the user’s home directory, the user’s home directory is indicated by a path that starts with a tilde and a slash (‘~/’). This maps to the path indicated in Java’s user.home System property.
Make sure you have a good command line shell available. If you’re familiar with one, keep it. If command lines are uncomfortable for you, you might want to use Git for Windows which includes a bash like shell. Though virtually all work in OSGi enRoute is done through Eclipse, there are some crucial elements where the shell is just much nicer.
If you start using enRoute you will likely create a number of workspaces. There is a very handy utility plugin for Eclipse on MacOS that shows you which workspace is which icon in the task bar:
There is also multi-workspace laucher plugin from Torkild U. Resheim that incorporates Neil Bartlett’s task bar badge (above).
There is a bug in Eclipse concerning the browser support in Linux. It may be necessary to configure an external browser in the Eclipse’s Preferences for bndtools/JPM.