Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 478562

Summary: Update DOT grammar to use Xtext 2.7.3 infrastructure.
Product: [Tools] GEF Reporter: Alexander Nyßen <nyssen>
Component: GEF DOTAssignee: Alexander Nyßen <nyssen>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 0.2.0   
Target Milestone: 4.0.0 / 3.11.0 (Neon) M3   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 478617    
Bug Blocks:    

Description Alexander Nyßen CLA 2015-09-28 12:13:24 EDT
When trying to update our target to Neon M2, I noticed that the tycho integration we currently use (i.e. execute mwe workflow via antrun against Xtext version in target) does no longer seem to work with Xtext 2.9 (because it fails to retrieve the antlr generator fragment, even if its part of the target).

As the Workflow file of DOT makes use of several deprecated fragments anyway, and as we might want to retain compatibility to earlier Xtext versions (at least Luna SR2) we should migrate it to be compliant with Xtext 2.7.3 (Luna SR2 version) and make use of the Xtext/Tycho integration instead.
Comment 1 Alexander Nyßen CLA 2015-09-28 13:45:57 EDT
I pushed the following changes to origin/master:
-Updated mwe workflow to no longer use deprecated fragments
-Ensure Xtext-tycho-integration is used, enforcing a 2.7.3 generator
-Update plug-in dependencies to point to 2.7.3 minimal version

Resolving as fixed in 3.11.0 M3.
Comment 2 Alexander Nyßen CLA 2015-09-29 07:45:47 EDT
Reopen until underlying build problem is fixed (see bug #478617).
Comment 3 Alexander Nyßen CLA 2015-09-29 11:22:00 EDT
It seems some dependencies cannot be retrieved because org.codehaus.mojo is down. I thus temporarily switched back to executing the emf-workflow with antrun. However, by this we cannot control which runtime is used (the one contained in the target), thus this should be changed back.
Comment 4 Alexander Nyßen CLA 2015-10-01 12:40:17 EDT
The underlying problem indeed was a missing entry in the mwe2 workflow, which is not documented (see bug #478830).
Comment 5 Alexander Nyßen CLA 2015-10-01 14:45:40 EDT
I have updated the mwe2 workflow and pom files accordingly. The build is succeeding again. Resolving as fixed.