You may try those out by using mvn command lines such as this one : mvn archetype:generate -DarchetypeVersion=<version> -DarchetypeGroupId=com.adobe.ac -DarchetypeArtifactId=<artifactId> -DarchetypeRepository=http://fna.googlecode.com/svn/trunk/fna/fna_m2_repository /
I've been working on the 1.3-SNAPSHOT versions lately Let me know if you are having issues, I also set up a mailing list for the fna project, feel free to use it for support ! Cheers ! On Wed, Feb 4, 2009 at 11:29 AM, neil thorne <[email protected]>wrote: > > Hi Francois, > > does this let you make a change to some source mxml, as, or css and > then hit reload in your browser to see changes immediately? > > If so - great! I did see this archetypes project before but I couldn't > get them to run (just my lack of understanding of using remote > archetypes :) > > Maybe I'll take another look. > > cheers, > > Neil > > On Feb 4, 10:21 am, François Le Droff <[email protected]> > wrote: > > I am not sure I understood your email right. > > but I think I achieved that kind of stuff with on the fna > archetypehttp:// > fna.googlecode.com/svn/trunk/fna/site/mvn_archetypes/blazeds-a... > > > > In generated web project I don't have any hard coded path > > and I manage to run and test the web app by running mvn > jetty:run-exploded > > > > Cheers ! > > > > On Wed, Feb 4, 2009 at 10:44 AM, neil thorne > > <[email protected]>wrote: > > > > > > > > > > > > > Hi, > > > > > A while back I read that Marcel Overdijk over at the Grail Community > > > had built a flex plugin. > > > > >http://marceloverdijk.blogspot.com/2007/08/another-sexy-flex-grails-e. > .. > > > > > This lead me to wanting to find out more about the flex webtier > > > compiler. I now use this routinely when developing flex front ends as > > > I can just hit F5 and see my code changes take effect. > > > > > I find this is much faster than using a swf based build cycle (flex > > > mojos based, or using FlexBuilder - change, build, stop, start.) > > > > > It's especially great when making styling changes (css or layouts) as > > > you feel like you're just coding html. > > > > > Anyway, my current working practice is fairly lame - I take a given > > > project that I'm working on - say > > > > > foo > > > +pom.xml > > > > > and I create a webtier project next to it - foo-webtier > > > > > parent > > > +foo > > > ++pom.xml > > > +foo-webtier > > > ++pom.xml > > > > > The webtier project is a really simple war project which just contains > > > the j2ee webtier compiler artifacts with a modified jetty plugin > > > configuration to allow me to get jetty to see changes to my foo > > > project. > > > > > The challenges I currently have are that I have to create a custom > > > webtier project each time, and that the webtier project is not generic > > > - I have hardcoded paths etc. in my flex-config.xml file and my > > > pom.xml, but I'm sure it would be easy to use something like maven > > > filters to generate these files. > > > > > I can then run mvn jetty:run in the webtier project and I now have > > > "F5" development lifecycle. > > > > > Does anyone else on this list do anything similar? > > > > > I'm happy to give you guys full details on what I currently do to turn > > > this hopefully into an official plugin. > > > > > Let me know your thoughts... > > > > > thanks, > > > > > Neil > > > > -- > > > > François Le Droffhttp://www.droff.com > > > -- François Le Droff http://www.droff.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
