[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_12831 ]
Peter Friese commented on AAAA-23: ---------------------------------- Considering the fact that the Eclipse runner has some dependencies to Eclipse itself, I am not sure if this approach is feasible. I'd rather go this way: - Have Martin write the AndroMDAEngine - package the AndroMDAEngine in a JAR file (with all other engine / core stuff) - write an Eclipse plug-in which enables the user to start AndroMDA by clicking on a button or a context menu entry or whatever - import the JAR file mentioned above into the Eclipse plug-in - let the Eclipse plug-in call the AndroMDAEngine whcih resides in the JAR file > Eclipse runner > -------------- > > Key: AAAA-23 > URL: http://jira.andromda.org/browse/AAAA-23 > Project: AndroMDA 4 > Type: New Feature > Components: Eclipse integration > Reporter: Matthias Bohlen > Assignee: Peter Friese > Fix For: 4.0-M2 > > This web page > http://www.andromda.org/index.php?option=com_content&task=blogsection&id=10&Itemid=78&limit=1&limitstart=9 > shows a sequence diagram that describes how to start AndroMDA 4. The test > case in technology/workflow-test also shows how to start a sample workflow. > An Eclipse plugin should be developed that gets a URL property for the > workflow definition file and runs AndroMDAEngine as shown on the sequence > diagram. > Steps: > 0. Think about where to get that workflow description URL from. > 1. Create the Eclipse plugin in the folder integration/runners/eclipse and > put the classes into the package org.andromda.integration.eclipse. > 2. Make the Eclipse plugin call the AndroMDAEngine class which is written by > Martin in AAAA-22. > Pair with Martin because his Maven runner is very similar in nature. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.andromda.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
