RE: [flexcoders] Re: Flex and Maven2 managed project
I am not using Mavin but I do use CruiseControl.Net which I have currently managing 21 Flex, Flash and .NET applications. Some of the applications have both Flex and .NET projects as part of the solution. My use of CruiseControl is purely for build/version management and since we use more .NET than Java it was a good fit for us. We have successfully got flexUnit to work with CC.Net as well which really puts all the work of writing unit tests to good use! It was a bit of work to get going and there are still a few ruff edges but all in all it really has made our build, publish and version management way easier! In a nutshell that is what we are using for our multiple project environment. Lance From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Shailesh Mangal Sent: Monday, January 08, 2007 5:02 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Flex and Maven2 managed project I dont have huge exp with Maven either. I just liked some of the features that it brings to the table e.g. Modular, inheritance, more then build (report, testing etc) out of the box (of course u can build all these in ant as well). Specially when I would need multiple projects for client (Flex modules, action script libraries), server (FDS, XFire, Hibernate etc) would like know what people are using in mulitple project env. -sxm --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Nick Sophinos" <[EMAIL PROTECTED]> wrote: > > I despise Maven. > > I know that this is a bit provocative, but my experience with those who > utterly abuse it to the point where the project is *anything but manageble* > has led me to this conclusion. I am always open to change, though. > > Thoughts, anyone? > > > - Nick > > On 1/8/07, Shailesh Mangal <[EMAIL PROTECTED]> wrote: > > > > 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 <mailto:flexcoders%40yahoogroups.com> , Oliver > > Lietz 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. > > > > > > > > > >
[flexcoders] Re: Flex and Maven2 managed project
I dont have huge exp with Maven either. I just liked some of the features that it brings to the table e.g. Modular, inheritance, more then build (report, testing etc) out of the box (of course u can build all these in ant as well). Specially when I would need multiple projects for client (Flex modules, action script libraries), server (FDS, XFire, Hibernate etc) would like know what people are using in mulitple project env. -sxm --- In flexcoders@yahoogroups.com, "Nick Sophinos" <[EMAIL PROTECTED]> wrote: > > I despise Maven. > > I know that this is a bit provocative, but my experience with those who > utterly abuse it to the point where the project is *anything but manageble* > has led me to this conclusion. I am always open to change, though. > > Thoughts, anyone? > > > - Nick > > On 1/8/07, Shailesh Mangal <[EMAIL PROTECTED]> wrote: > > > > 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 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. > > > > > > > > > >
Re: [flexcoders] Re: Flex and Maven2 managed project
I despise Maven. I know that this is a bit provocative, but my experience with those who utterly abuse it to the point where the project is *anything but manageble* has led me to this conclusion. I am always open to change, though. Thoughts, anyone? - Nick On 1/8/07, Shailesh Mangal <[EMAIL PROTECTED]> wrote: 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. >
[flexcoders] Re: Flex and Maven2 managed project
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. >