It's java's reflection ... same as with JUnit on newer JDKs the order of the tests are random, on older they are always in the same order. As the arguments are output based on reflection running on some of the config-interfaces, the order does vary. In the new Flexmojos versions this is still the case, but I switched the way the args are output to a format that is invulnerable against ordering problems
Chris -----Ursprüngliche Nachricht----- Von: laserjet [mailto:[email protected]] Gesendet: Freitag, 13. November 2015 08:04 An: [email protected] Betreff: Re: FlexMojos: Ambiguous argument list to mxmlc Yes, it's probably a good idea to do the update, but it would still be interresting to understand why the argument list is generated in random order on some systems, but not on others. Best Regards /Claes Mario Souza wrote > So... I already updated the company's projects from FlexMojos 4 > directly to > 7 .. somethings has been changed (of course), also I've updated the > Flex SDK from 4.5 to 4.14.1 .. but once you fix the build, you never > need touch on that again. So, I strongly recommend you upgrade for FM > 7.x ... take 2 or 3 days on that. :) > > Regards. > > @mariojunior > > > On 13 November 2015 at 10:55, Christofer Dutz < > christofer.dutz@ > > > wrote: > >> I too have encountered this issue and have fixed this in the >> Flexmojos >> 7.0.1 >> I will definitely not back-port this fix, especially not way back to 5.x. >> So I would suggest to update. >> >> Chris >> >> ________________________________________ >> Von: laserjet < > claes.frisk@ > > >> Gesendet: Donnerstag, 12. November 2015 15:02 >> An: > [email protected] >> Betreff: FlexMojos: Ambiguous argument list to mxmlc >> >> I'm using FlexMojos 5.2 for various reasons and can't easily upgrade. >> I have recently run into problems getting errors like: >> [ERROR] command line:[-1,-1] ambiguous argument list; unable to >> determine where 'compiler.namespaces.namespace' parameters end, and >> default 'file-specs' parameters begin. Use '--' to terminate the >> parameter list, or perhaps use the >> '-compiler.namespaces.namespace=val[,val]+' syntax instead. >> >> It seems that FlexMojos generates the argument list in a somewhat >> random order and when the nampespace list ends up last, it will fail. >> >> Something similar has been reported in >> https://flexmojos.atlassian.net/browse/FLEXMOJOS-886. >> >> The thing is it only happens in certain environments and I haven't >> been able to find why. On some environments the argument list is >> always in the same order. Does anyone have experience with this or >> know what environments are sensitive to this problem? >> >> /Claes Frisk >> Quickspin AB >> >> >> >> -- >> View this message in context: >> http://apache-flex-users.2333346.n4.nabble.com/FlexMojos-Ambiguous-ar >> gument-list-to-mxmlc-tp11476.html Sent from the Apache Flex Users >> mailing list archive at Nabble.com. >> -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/FlexMojos-Ambiguous-argument-list-to-mxmlc-tp11476p11480.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
