Google has destroyed the meaning of the term "beta"... they are the exception to the rule.
We will not be using Beta code in a production environment: a company with several hundred million dollars in revenue each year just doesn't work like that. Additionally, it creates a lot of extra work upgrading to a new version of maven that has limited backward compatibility. It's not prejudice – just business common sense. Very disappointing that you don't understand this. We have an interim solution to our problem, and will most likely write our own mojo to do what we require – or wait until maven 3.x is released. Matt On Jun 8, 2:47 pm, Marvin Froeder <[email protected]> wrote: > Yes, I'm no longer changing 3.x code... just applying users patches.... > > Commons folks, let's stop the prejudice with betas.... chrome and gmail > where betas for life times and nobody refused to use either. > > From what I have being seeing on flexmojos build m3 is way more stable then > any 2.x..... give if a shot and you will likely be surprised. > > VELO > > On Tue, Jun 8, 2010 at 10:10 AM, Alexandre A <[email protected]>wrote: > > > > > Thanks a lot VELO. > > Very quick response to the problem. > > > We are currently using Flex Mojo 3.6.1 with maven 2.2 > > Do we need to upgrade the Flex Mojo 4 with Maven 3 to start using this > > feature? If it is the case, then as Maven 3 is still in beta version, > > we can not use it with our 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 http://flexmojos.sonatype.org/
