Good. Let me explain anyway. The warnings from the initial archetype cmd can be ignored (I will add a note of that in the tutorial). Before version 1.3.0 we used to declare the fornax maven repository in settings.xml. Now we don't and instead it is defined in the pom.xml, which is generated by the archetype.
Yes, removing the local maven repository can often be a solution to maven problems. mvn -U clean install is also a good alternative in some cases. /Patrik kflo wrote: > > FWIW, I appear to have gotten past this. I found another suggestion in an > old thread that I tried and it got me past the mvn eclipse:eclipse step. > > Solution: Nuke the fornax repository locally and tried mvn eclipse:eclipse > again. It downloaded everything properly and created the eclipse project. > I imported into eclipse and all is well. > > Moving onto to the code gen steps. > > -- View this message in context: http://www.nabble.com/Hello-World-Tutorial-tp17364308s17564p17364351.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
