In the cnf/ext directory, we can find these files:

• build.mvn
• defaults.bnd
• maven-layout.bnd
• runtime.mvn

Since the cnf/ext directory is intended for plugins, why are these files included here, as opposed to being included in the build.bnd file?

The current workspace uses the enRoute wrapper for JUnit4.

Now that JUnit5 is out, consider updating to support JUnit5.

Hey Peter,

This is really nice. I made my own custom template based on a fork of this workspace, so hopefully I can follow along with updates and also keep my customizations.

It was very easy to install the template in my Eclipse and apply it to my workspace. I also noticed that it is even possible to update the workspace easily. You can even see the diffs (at the file level) and apply which changes you want (or don't).

All this is very nice!!

However, it seems to only work for a public workspace.

Is there any plan to make this feature work for a private workspace? The reason is that it would allow a leg up getting started, even though the configurations may contain information that should not be made public.

For now I just made the information very generic in my public workspace, but then I have to manually edit it once I install the workspace, which kind of (at least partially) defeats the purpose of having a custom workspace in the first place.

In this line:

the version number is provided, which creates the default version number for all projects.

Is the intent:

1. To create a default, which will normally be overridden in the project? Or,
2. To make all of the projects in the workspace have the same version?

Hi Peter,

I cloned the workspace, but I don't see the example API and Provider projects. Am I in the wrong project?