[#FDT-1463] Hero SDK is not working - Interactive Pioneers's JIRA

FDT

Hero SDK is not working

Created: 26/Oct/10 02:18 AM Updated: 22/Jun/12 07:01 PM

Component/s:

SDK Management

Affects Version/s:

FDT 4.0.1 (Build 1185)

Fix Version/s:

FDT 4.1

Security Level:

public

Time Tracking:

Not Specified

File Attachments:	1. hero_error.log (169 kB)
Environment:	Mac OS X 10.6.4 FDT4 max Stand alone

Description

« Hide

When I try to compile a flex app with the Flash 4.5 (Hero) SDK it does not compile, and I get many errors(which I don't understand), as well as the a Null Pointer Exception.
please view last night's errors here:
http://hawaiiflash.org/Hero.zip

Today I could do do a "stack trace" (see video)
the error log is here
http://hawaiiflash.org/hero_error.log

the video of me adding the SDK and compiling an empty Hero application is here:
http://www.screencast.com/t/3OF2WsEA

Thank you,
John

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

John Barrett added a comment - 26/Oct/10 02:20 AM

Sorry, here is the video link:
http://www.screencast.com/t/3OF2WsEA

[ Permalink | « Hide ]

Alan K (Deprecated) added a comment - 04/Nov/10 02:42 PM - edited

Any status on this? I see it's resolved - what was the issue? I can't get it to work as well.
I'm not using any flex framework classes - just a simple Sprite as my Main class.\

java.lang.NullPointerException
at com.powerflasher.fdt.core.internal.launch.compile.concrete.CompilerLoaderExtensionPoint.getFactoryFor(CompilerLoaderExtensionPoint.java:68)
at com.powerflasher.fdt.core.internal.launch.compile.concrete.CompilerRunnable.createCompilerFactory(CompilerRunnable.java:253)
at com.powerflasher.fdt.core.internal.launch.compile.concrete.CompilerRunnable.getContextClassLoader(CompilerRunnable.java:247)
at com.powerflasher.fdt.core.internal.launch.compile.concrete.CompilerProcess.runMainConfiguration(CompilerProcess.java:242)
at com.powerflasher.fdt.core.internal.launch.compile.concrete.CompilerProcess.runAllChildren(CompilerProcess.java:260)
at com.powerflasher.fdt.core.internal.launch.compile.concrete.CompilerProcess.access$6(CompilerProcess.java:252)
at com.powerflasher.fdt.core.internal.launch.compile.concrete.CompilerProcess$1.run(CompilerProcess.java:190)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

eclipse.buildId=I20090611-1540
java.version=1.6.0_22
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US
Framework arguments: -product --clean com.powerflasher.fdt.product.product -keyring /Users/OSX/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws cocoa -arch x86 -product -clean --clean com.powerflasher.fdt.product.product -keyring /Users/OSX/.eclipse_keyring -showlocation

[ Permalink | « Hide ]

Philipp Arnolds added a comment - 04/Nov/10 03:04 PM

This issue has allready been fixed. The fix will be included in the next service release for FDT 4. (FDT 4 SR1)

[ Permalink | « Hide ]

John Barrett added a comment - 05/Nov/10 10:39 AM

I did the update and this is fixed now, thank you!