DealingWithUMPLE_VERSION

Timothy Lethbridge edited this page Jun 14, 2016 · 2 revisions
Clone this wiki locally

Dealing with @UMPLE_VERSION@

Each generated umple file, has a comment header similar to:

/*PLEASE DO NOT EDIT THIS CODE*/
/*This code was generated using the UMPLE 1.15.0.963 modeling language!*/

But, you will notice that our code generator tests use a generic header as shown below:

/*PLEASE DO NOT EDIT THIS CODE*/
/*This code was generated using the UMPLE @UMPLE_VERSION@ modeling language!*/

The build process (documented in ./build/build.umple.xml) takes care of converting @UMPLE_VERSION@ to the particular version based using a setVersion. Similarly at the end of build it will resetVersion.

The specific version is based on the value in the ./build/umpleversion.txt file.

Now, things can go awry for several reasons.

  • Eclipse might have cached the explicit version and all of your tests are failing (Refresh the project in that case).

  • Or, you might manually stop the build after the "setVersion" but before the "resetVersion" (or it stopped by itself - i.e. a bug in the build process itself). To resolve this issue read on.

Let suppose that the application's @UMPLE_VERSION@ is out of sync and currently set at 1.2.345.

  ant -f build.umple.xml -Dmyenv=local -Dumple.version=1.2.345 template.resetVersion

Adding in these words to help find this page:

  • Fixing Umple version (umple.version)
  • Resetting Umple version
  • How to reset Umple version
  • Umple tests failing because of version number
  • @UMPLE_VERSION@ is broken