Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Papyrus/Oxygen Work Description/NewFeature/SyncModelCode"

 
Line 4: Line 4:
  
 
Links:
 
Links:
 +
* Umbrella issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=510256
 
* Planning for new feature: https://wiki.eclipse.org/Papyrus_Software_Designer/Model_Code_Synchronization
 
* Planning for new feature: https://wiki.eclipse.org/Papyrus_Software_Designer/Model_Code_Synchronization
 
* Existing batch approach: https://wiki.eclipse.org/Java_reverse_engineering and https://wiki.eclipse.org/Java_Code_Generation
 
* Existing batch approach: https://wiki.eclipse.org/Java_reverse_engineering and https://wiki.eclipse.org/Java_Code_Generation
 
* EVM-JDT core in VIATRA: https://git.eclipse.org/c/viatra/org.eclipse.viatra.git/tree/integration/plugins/org.eclipse.viatra.integration.evm.jdt
 
* EVM-JDT core in VIATRA: https://git.eclipse.org/c/viatra/org.eclipse.viatra.git/tree/integration/plugins/org.eclipse.viatra.integration.evm.jdt
 
* Prototype implementation to be migrated and updated: https://github.com/viatra/viatra-evm-jdt/
 
* Prototype implementation to be migrated and updated: https://github.com/viatra/viatra-evm-jdt/

Latest revision as of 08:01, 11 January 2017

Real-time incremental (change-based) synchronization between UML and code

This page describes the work on performance real-time incremental (change-based) synchronization between UML and code, in Papyrus Oxygen, in collaboration with IncQuery Labs, using EVM-JDT.

Links:

Back to the top