Skip to main content



      Home
Home » Modeling » Epsilon » Using JDT driver in workflow(Reverse engineering and architecture modernisation using DevOps)
Using JDT driver in workflow [message #1853985] Tue, 26 July 2022 19:52 Go to next message
Eclipse UserFriend
Hello!
We are quite excited about the EMC JDT driver and would like to know if it is possible to use it:

  1. within the Epsilon workflow component in a headless system. This would allow us to perform all sorts of interesting metrics and customer-specific analysis, including enforcing customers design rules.
  2. to write Java information to the API. This would allow us to perform automated aggressive refactoring on customer code.

In case the workflow use is possible, we would also like to know how we would need to activate the JDT model in the headless environment. It would seem that we would need to

  1. start a headless workspace
  2. trigger its Eclipse builders
  3. perform the queries or manipulations
  4. commit the results
  5. release (unwind) any resources: workflow, project, workspace

Is that correct?
Re: Using JDT driver in workflow [message #1853990 is a reply to message #1853985] Tue, 26 July 2022 23:45 Go to previous message
Eclipse UserFriend
Hi Jörn,

In principle #1 should be feasible as the driver doesn't have any UI dependencies and JDT can be run in headless mode [1, 2]. #2 is not possible as the driver doesn't provide any writing capabilities I'm afraid.

Best,
Dimitris

[1] https://jmini.github.io/blog/2020/2020-01-17_jdt-without-eclipse.html
[2] https://github.com/jmini/jdt-experiments/tree/master/programcreek-examples/programcreek-osgi
Previous Topic:Models with multipe files and only file reference - preferred approach EVL
Next Topic:emfatic: nested double-quotes in annotations?
Goto Forum:
  


Current Time: Fri Jul 04 10:31:05 EDT 2025

Powered by FUDForum. Page generated in 0.34187 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top