I am planning to use Maven for my new flex project. Wondering if someone can share their experience of using maven folder structure, POM file, todo and not todo items, limitations etc
-sxm --- In flexcoders@yahoogroups.com, Oliver Lietz <[EMAIL PROTECTED]> wrote: > > Am Montag, 18. Dezember 2006 08:19 schrieb Aldo Bucchi: > > Yeah Maven!, > > > > I'm a little surprised on the apparent low interest in the flex-maven > > front. > > I'm not surprised ;). Most people will start with a shiny frontend which sells > the application. Project (build/change/livecycle) management is not as sexy > as eye candy for most of them. > > > I am also flirting with the idea of building a plugin, but not > > yet... not yet... tomorrow perhaps > > :), same here > > > I would really like to hear about Adobe's plans with respect to Maven. > > It would be a very good way to make things easier for new developers ( > > by leveraging something that's already built for you ) and to make > > things more attractive to veterans. > > Really, maven is one of those little toys I really really love. > > > > My wishlist on this one ( thinking java here ): > > > > * mavenized standardization of folder structures for flex applications > > ( all flavors: standalone, fds, etc ) > > ** src/main/flex, src/test/flex? > > Did that already for my projects without integrating testing. Works fine - > same layout (SVN+MVN) for Flex and Java projects. > > > * maven plugins: > > ** flexunit ( or asunit ) > > ** mxmlc > > ** asdoc > > *** including complex features (eg. auto compile and deploy examples) > > * definitions and workflow for continuous integration deployoment ( > > cruise control and continuum hopefully ) > > > > and then some extra would-be-nice-to-have plugins: > > * auto generate fds stubs/skeletons ( vos, assemblers, dataproviders, > > dataservices, etc ) for hibernate, JDO, other ORMs > > * springified fds > > ...? > > Nice, indeed. I hope someone at Adobe is already working on Mavenization of > Flex. > > O. >
