Ops, forgot to say, yes, playerglobal stuff is the problem.... I know is somehow related to this 2.0.3 + 2.0-alpha-2 usage..... but not sure what is the cause of the problem. Not sure if the flex SDK dependencies have different ids between 2.0.3 and alpha2....
VELO On Fri, Mar 27, 2009 at 4:58 PM, Per Olesen <[email protected]> wrote: > > > Is all on the same project? > > Yes. > > > Maven 2.0.9 will load only one flexmojos version. This is fixed on > 2.1.0. > > I guess you mean maven will only use one in the same compilation / > execution !? > > I build my main application with 2.0-alpha2 as one mvn execution of > its own. > > Currently then, I am adding uitesting using flexmonkey as a new, > separate, integrationtest module. This is executed as a second, mvn > execution, using flex-mojos 2.0.3. I might very well upgrade to 2.0.3 > too, for the main application modules. > > But what about the logs from compilation output. Isn't it a problem, > that 2.0.3 links to playerglobal with another filename than > playerglobal.swc? And why not as an external library? > > > Anyway, I recommend you using only one version. > > We might upgrade soon. But it is little bigger issue there, as it > needs better/more thorough testing, before releasing to all our users > then. > > > > > On Fri, Mar 27, 2009 at 4:13 PM, Per Olesen <[email protected]> > wrote: > > > > > Hi, VELO > > > > > I am using both. I have a maven project with several different > > > modules. > > > Some compile with 2.0-alpha2. > > > Some compile with 2.0.3. > > > > > On Mar 27, 5:16 pm, Marvin Froeder <[email protected]> wrote: > > > > It is unclear to me, you are using flexmojos 2.0.3 or 2.0-alpha2? > > > > > > Run mvn help:effective-pom to be sure which version of flexmojos is > in > > > use. > > > > > > VELO > > > > > > On Fri, Mar 27, 2009 at 12:57 PM, Per Olesen <[email protected]> > > > wrote: > > > > > > > I have a problem running flexmonkey as it says: > > > > > > > "VerifyError: Error #1079: Native methods are not allowed in > loaded > > > > > code" > > > > > > > when loading my application from its launcher (or maybe when > loading > > > > > the tests). > > > > > > > The reason for posting this om flex-mojos group is an issue like > this > > > > >http://bugs.adobe.com/jira/browse/SDK-15073whereit seems flex-mojos > > > > > have had issues with a renamed playerglobal.swc. So I thought it > might > > > > > be the flex-mojos compilation that is causing my troubles? > > > > > > > The maven module that compiles my flexmonkey flex tests is using > flex- > > > > > mojos 2.0.3 from the flex-super-pom, which gives this compiler > output: > > > > > > > --- > > > > > -compiler.external-library-path= > > > > > -compiler.library-path > /Users/polesen/.m2/repository/com/gorillalogic/ > > > > > flexmonkey/0.8a/flexmonkey-0.8a.swc > /Users/polesen/.m2/repository/com/ > > > > > adobe/flexunit/0.9/flexunit-0.9.swc > /Users/polesen/.m2/repository/com/ > > > > > adobe/flex/framework/applicationupdater/3.2.0.3958/ > > > > > applicationupdater-3.2.0.3958.swc > /Users/polesen/.m2/repository/com/ > > > > > adobe/flex/framework/applicationupdater_ui/3.2.0.3958/ > > > > > applicationupdater_ui-3.2.0.3958.swc > /Users/polesen/.m2/repository/com/ > > > > > adobe/flex/framework/flex/3.2.0.3958/flex-3.2.0.3958.swc /Users/ > > > > > > polesen/.m2/repository/com/adobe/flex/framework/framework/3.2.0.3958/ > > > > > framework-3.2.0.3958.swc > /Users/polesen/.m2/repository/com/adobe/flex/ > > > > > framework/playerglobal/9-3.2.0.3958/playerglobal-9-3.2.0.3958.swc / > > > > > > Users/polesen/.m2/repository/com/adobe/flex/framework/rpc/3.2.0.3958/ > > > > > rpc-3.2.0.3958.swc /Users/polesen/.m2/repository/com/adobe/flex/ > > > > > framework/utilities/3.2.0.3958/utilities-3.2.0.3958.swc > > > > > --- > > > > > > > note how playerglobal is linked with a version name and not in > > > > > external library path. > > > > > > > My application which is under test, is compiling with an older > flex- > > > > > mojos version 2.0-alpha2, with a flex sdk 3.0 version. Now, the > > > > > compiler output from this is different: > > > > > > > --- > > > > > -compiler.external-library-path > /Users/polesen/sandboxes/fogp/atlight/ > > > > > trunk/thinclient/client/admin/target/libraries/external/ > > > > > playerglobal.swc > > > > > -compiler.library-path /Users/polesen/sandboxes/fogp/atlight/trunk/ > > > > > > thinclient/client/common/target/atlight-thinclient-client-common-1.19- > > > > > SNAPSHOT.swc /Users/polesen/.m2/repository/com/adobe/flex/sdk/ > > > > > framework/3.0.0.477/framework-3.0.0.477.swc /Users/polesen/.m2/ > > > > > repository/com/adobe/flex/sdk/rpc/3.0.0.477/rpc-3.0.0.477.swc > /Users/ > > > > > polesen/.m2/repository/org/puremvc/puremvc-multicore/1.0.4/puremvc- > > > > > multicore-1.0.4.swc > /Users/polesen/.m2/repository/com/adobe/flex/sdk/ > > > > > framework/3.0.0.477/framework-3.0.0.477-en_US.swc > /Users/polesen/.m2/ > > > > > > repository/com/adobe/flex/sdk/framework/3.0.0.477/framework-3.0.0.477- > > > > > ja_JP.swc /Users/polesen/.m2/repository/com/adobe/flex/sdk/rpc/ > > > > > 3.0.0.477/rpc-3.0.0.477-en_US.swc > > > > > --- > > > > > > > here, playerglobal is not named with a version in the filename and > it > > > > > is included in external library path. > > > > > > > Could this be my problem, and what should I do to fix it then? > > > --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
