Change Request #3104

Java 9 compliance - SafetyCases

Added by Alexander Diewald about 3 years ago. Updated over 2 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
0.50 h


Java 9 introduces a module system (Project Jigsaw) that contains a "Module" class.

The SafetyCases plugin defines a "Module" EClass in the meta-model such an error occurs in the generated code. The generator does not automatically resolve the include since it cannot know which "module" class to use.

Hence, a renaming of the EClass would solve the problem and it would also resolve a naming conflict with where also a "Module" EClass is defined. A migrator will be needed but it should be simple.

Ofc, this should be only done after the current release.


#1 Updated by Alexander Diewald almost 3 years ago

  • Assignee changed from Carmen Carlan to Alexander Diewald
  • % Done changed from 0 to 90

Just did this as Sudeep just fixed it for

I'd just need a (simple) old model to see if the migrator works fine (ModuleRef). As far as I understood the model, "Module" is actually abstract and needs no migration. If so we could also define it as such in the model. Should I do so?
As indicated above, I only had to write a migrator for ModuleRef.

BTW, we got no more compilation errors with Java 9 now (under the assumption that "Module" is abstract) :)

#2 Updated by Alexander Diewald over 2 years ago

  • Status changed from New to Feedback
  • Assignee changed from Alexander Diewald to Carmen Carlan
  • % Done changed from 90 to 100

Resolved in r23128.

Tested for an artificially generated safetycases that contains all relevant classes.

#3 Updated by Carmen Carlan over 2 years ago

  • Status changed from Feedback to Resolved
  • Assignee changed from Carmen Carlan to Anonymous

#4 Updated by Anonymous over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF