Re: [Andromda-user] getting started documentation is more like getting stuck documentation

[Brian Hill]

-- How do you suggest we organize them? All of the following should be in a single getting started document rather than having the first-time user go from Getting Started --> Plugin --> Download The single getting started document would contain: ==== AndroMDA is distributed as a Maven Plug-in.  The dependencies for AndroMDA (e.g. XDoclet) will automatically be retrieved when you use Maven to get AndroMDA. First you need to install Maven.  [Send person to off to get Maven just like you already do]. Once Maven is installed, create a project.properties file in any directory containing a single line [creating a project.properties file containing this line was not an obvious thing to guess] maven.repo.remote=http://www.ibiblio.org/maven,http://team.andromda.org/maven In that same directory execute $MAVEN_HOME/bin/maven plugin:download -DgroupId=andromda -DartifactId=maven-andromdapp-plugin -Dversion=3.0M3-SNAPSHOT Then insert the exact same directions on how to generate an application as you already have. Then send the user off to the samples, and that takes care of the single getting started document. ==== I am still stumped as to why $MAVEN_HOME/bin/maven andromdapp:generate Resulted in Goal "andromdapp:generate" does not exist in this project. and then it worked after re-installation.  Anyway, it works now. --Brian ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user