Fornax MWE Workflow Maven Plugin 3.5.1 published on Maven Central

The Fornax Workflow plugin is a Maven Plugin that executes MWE/MWE2 workflows within Maven. It has been there for quite some years now, and whoever needed to integrate MWE/MWE2 workflows in a headless build was likely using it. The Fornax Platform has been an address where components around openArchitectureWare, Xpand and Xtext have been developed. While all other subprojects don’t play any role anymore, the Workflow plugin is still in frequent use.

Over the years we had to change the underlying infrastructure some times. The plugin was hosted on the project’s own repository server, and projects using the plugin had to configure an additional plugin repository either in their POMs or settings.xml. This was undesired, but at the end not really a blocker. However, with a recent change of the repository manager, users experienced problems accessing the Fornax repository Currently, this URL is redirected to a server hosted at itemis, and users might get problems with the HTTPS connection.

It always bothered me that we had to host this plugin on a separate repository, and since it is a widely used component, it is logical that it should be available from the Central repository. But it was never a blocker for me. Now finally I got the driver to change this.

Long story short, the plugin is now published at Maven Central as version 3.5.1. I highly recommend to upgrade to this version and remove the Fornax Maven repository from your configuration. The coordinates did not change, they are still org.fornax.toolsupport:fornax-oaw-m2-plugin. I would like to change this sometime in the future (e.g. the name parts “oaw” and “m2” are not up-to-date anymore), maybe with moving development to another project hosting platform.

Version 3.5.1 does not differ much from 3.4.0, which is the version likely used by the world today. The main work was on refactoring the POM and its parent in order to meet the requirements for deployment on Maven Central. Further, I worked on automation of the release process with the maven-release-plugin.

There is one additional feature in 3.5.x: The new property useTestScope can be used to skip dependencies from the test scope for computation of the Java classpath used to execute a workflow in forked mode. On Windows systems the classpath sometimes reaches the limit of allowed command line length, especially since the local Maven repository is below the user’s home directory by default, which has already a rather long path prefix. By default, the plugin will exclude now these test scope dependencies unless the user configures the property explicitly. In 3.5.0 there was a small logical bug with this feature which made the plugin unusable, so please do not use that version. The version 3.5.1 can be used without problems for all using 3.4.0 so far.

5 thoughts on “Fornax MWE Workflow Maven Plugin 3.5.1 published on Maven Central

  1. Dear Karsten, I appriciate very much that there is new version of the Fornax plugin. I have been using version 3.4.0 for quite a while to generate Java code from an UML model. Recently I had problems to run my workflow on an UML file that I had opened and saved with a newer version of Papyrus, such that the referenced UML version in the header of the XMI file changed from 3.0.0 to 5.0.0. I guess I need to upgrade my maven dependency org.eclipse.uml2:uml also from 3.0.0 to 5.0.0. But when I try, I end up in a mess searching for dependent Eclipse plugins in Maven repositories around the world. Have you ever generate code from a UML model (version 5.0.0) using the Fornax Maven plugin? Do you have a hint where is a good place to find the required Maven dependencies in a well organized repository? Thanks a lot in advance for your kind answer.

  2. Since I just hit the classpath limits in windows. How and where can I set the useTestScope property. The value needs to be false right?

    • To answer my question:



      Unfortunately my CP is still too long.

      • org.fornax.toolsupport


  3. Put it into the <configuration> area of the plugin. It is false already by default. You should analyze the project dependencies (might be too much), and move the local repository to a short path (e.g. C:\.m2\repository)

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s