I went through, ran mvn dependency:tree, and made sure there were no references made to any 3.5 swc files.
Yet flexmojos put them in the compile path anyway. This looks like a bug flexmojos. On Oct 4, 11:03 am, Marvin Froeder <[email protected]> wrote: > My best guess is that you (or whoever did that) forgot to exclude something > or maybe a typo error, maven doesn't validate that. > > Anyway, if you feel comfortable doing that, ok, whatever, but is a really > error-prone approach. > > On Tue, Oct 4, 2011 at 2:27 PM, Javier Delgadillo > <[email protected]>wrote: > > > > > > > > > I was using exclusion in my pom.xml (look at my previous message in > > the thread). flexmojos immediately would fail immediately complaining > > of conflicting sdk's if I didn't. Some of the 3.5 references were > > removed from the compile command but not all. > > > as3commons-lang was only one of a handful of dependencies that dragged > > in 3.5. I gave them all new pom's that had no dependencies which > > mimics the developer's FlashBuilder setup and everything works fine > > now. > > > On Oct 3, 11:25 am, Marvin Froeder <[email protected]> wrote: > > > Hrmmm, why didn't you use exclusions to drag 3.5.0 out? Replacing pom.xml > > > will come after you in the future. > > > > VELO -- 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/
