Yeah profiles is a good alternative... now it's clear what you are trying to do.
Some UI testing strategies require extra libs (automation, flexunit, asmock...); I guess now we have the test-swf goal to achieve this. But anyway, I use a profile to drag all that stuff in and aim Hudson at it; a successful test build triggers a release build, which includes steps to publish to Nexus. It seems there is an argument to have (at least) 3 projects; are you sure it's wise to force them into one? Do you have this common source project simply because you need release and debug distributions? I presume the packaging project is a WAR project? On Dec 23, 3:44 pm, Logan Allred <[email protected]> wrote: > Just as another option, we used Maven profiles to do release and debug > versions, however, you can only build 1 at a time. We had multiple > Hudson jobs, 1 for release and 1 for debug (+automation). > > In the end, we stopped having multiple builds. We built debug versions > up until we were ready for a release candidate, then we branched the > code and made a release branch that only built a release build for > final testing and release. Not saying it's the right or best way, it's > just how we did it. > > You can also use the assembly plugin for packaging up your artifacts > without a separate project. > > Logan > > > > On Wed, Dec 23, 2009 at 3:49 AM, eprevot <[email protected]> wrote: > > I need it because I want to have a release and a debug versions. If I > > follow Maven rules, I'll have 4 projects : one project for the common > > sources, one for the release version, one for the debug version, and > > one to package all this. > > With this trick, I can have just one project. -- 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/
