BTW, do you have flashplayer on path? VELO On Tue, Mar 24, 2009 at 11:31 PM, Marvin Froeder <velo...@gmail.com> wrote:
> Can you run it with -X and attach the result? > VELO > > > On Tue, Mar 24, 2009 at 11:28 PM, Shanon McQuay <shanonmcq...@gmail.com>wrote: > >> Hi I'm new to both maven and flexmojos but gave the 3.1-SNAPSHOT a try >> anyway. I got the following message... >> [INFO] Starting tests >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] FATAL ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] null >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Trace >> java.lang.NullPointerException >> at >> org.sonatype.flexmojos.test.threads.AsVmLauncher.stop(AsVmLauncher.java:181) >> at >> org.sonatype.flexmojos.test.threads.ControlledThreadUtil.stop(ControlledThreadUtil.java:34) >> at org.sonatype.flexmojos.test.FlexUnitMojo.run(FlexUnitMojo.java:294) >> at >> org.sonatype.flexmojos.test.FlexUnitMojo.execute(FlexUnitMojo.java:152) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:925) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:768) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >> >> >> On 24/03/2009, at 6:42 AM, Marvin Froeder wrote: >> >> Hi Folks, >> I did some changes on the way flexmojos launch unit tests. Now I >> need volunteers to try it. So far all integration tests I have passed, but >> real people are better to find errors :D >> >> >> http://repository.sonatype.org/content/groups/public/org/sonatype/flexmojos/flexmojos-maven-plugin/3.1-SNAPSHOT/ >> >> What did change: >> - It is heavy Threaded now. So far 4 threads: one to get results, one to >> ping, one to open flash player and the main thread will monitor all other >> threads state; >> - First thread was already there, nothing new! >> - There is now a PING thread. If flash player get stuck this thread >> won't receive PONG, and will kill flash player, failing the build. That is >> the way I found to workaround this: >> http://bugs.adobe.com/jira/browse/FP-444 >> - It will open FlashPlayer (and in future ADT ) instead of launching >> application associated to SWF extension. So is necessary to have FlashPlayer >> on PATH. >> >> I know was easier to open associated application with SWF. But that made >> impossible to kill flashplayer from Java side. And that change will allow >> us to launch ADT on AIR projects (so far I didn't code that). >> >> This changes are done on my local machine for sometime, but I just check >> in today. >> >> Thanks for any problems/hits you found. >> >> >> VELO >> >> >> >> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to flex-mojos@googlegroups.com To unsubscribe from this group, send email to flex-mojos+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
