[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_13920 ]
Peter Friese commented on AAAA-23: ---------------------------------- I'd like to point out two things: 1) The user experience must be Eclipse-like. I like Thorsten idea of having a launcher that finally apperas in the "run..." dropdown menu. Tools like the WTP chose the same approach (.WAR files have a "run on server" context menu entry), so we are in good company. 2) Dependencies should be discovered dynamically / on the fly. I really do not like the idea of having an extra description file containing a list of dependencies. Things are likely to break this way. Android will contain a bootstrapping module that makes sure Android will download all AndroMDA libraries to your favourite directory (can be either your local maven repo, your ANT lib dir or some other directory of your choice). See AND-11 for more info. Most people are using Maven in conjunction with AndroMDA, so we can be pretty sure that the local maven repo has all dependencies. Thus, the only thing we need to make sure is that we can discover all dependencies the way maven does. If we do not want to end up re-implementing major parts of maven functionality for AndroMDA / Android, the only option will be to run maven in the background. Android already contains a maven runner. (Maven is a great tool, but it imposes some very inconvenient restrictions on tool integrator. *Sigh*) > 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: Thorsten Pohl > 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 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
