[ http://jira.andromda.org/browse/AAAA-23?page=comments#action_13911 ]
Matthias Bohlen commented on AAAA-23:
-------------------------------------
Yes, this should be possible. Look at the contents of the
maven/2/andromdapp/**/ClasspathWriter.java file in the source tree of AndroMDA
3. This is a class which generates an Eclipse .classpath file from a Maven
build project with nested pom.xml files. It collects all the dependencies and
writes them into the .classpath file. The ClasspathWriter class is part of the
andromdapp plugin and is run when you type "mvn andromdapp:eclipse" on the
command line. This short form of invocation works only if you have the
following three lines in your $HOME/.m2/settings.xml file:
<pluginGroups>
<pluginGroup>org.andromda.maven.plugins</pluginGroup>
</pluginGroups>
You could copy the code from ClasspathWriter.java and create a new Maven2
plugin (Mojo) which writes an XML dependency file that you can use when booting
the Launcher.
The only thing is that the user will also have to invoke this Mojo from his own
build to make sure that his own cartridges and will be part of the list of
dependencies, too. The advantage is that even transitive dependencies from
other frameworks will be detected.
She must finally tell the Eclipse launcher plugin somehow where to find the
dependency file. Should the Eclipse runner have a preference page for this or
is there a better, more 'automatic' way (example: keep the dependency file
always at the same place in the user's Eclipse project)?
> 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
