[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_13950 ]
Thorsten Pohl commented on AAAA-23: ----------------------------------- I think that a combination of automatic dependency discovery and generated dependency description would serve us best on this issue. If we can discover the needed jar's for a dependency in a directory of the user's choice, we would be able to run both in a maven repository environment and in a custom "repository" env. I think, the dependency-list Matthias suggested should contain the following information: The dependency's name and version. Then the runner can try to auto-discover the jars from a given base-directory. The ResourceResolver from Android should be able to do this job. But I think (as mentioned below) the dependency configuration should be customizable by the user so that additional libs can be incorporated and the paths of "undetectable" jars can be added. About the handling of a runner: I think it would be Eclipse-like, if the launch-configuration has the final control over which libraries are in the classpath for each individual run. This way the user can use different plugins with each configuration. I am thinking about something like the "classpath"-tab in the ant-launch-configuration of eclipse. On the other hand an initial configuration should be provided, and maybe even customized using eclipse's preferences. Do you have any additional ideas? > 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
