|
[
Permalink
| « Hide
]
Pedro Paulo Almeida added a comment - 23/Apr/12 06:56 PM
Oh, Sorry: the correct second image (the list with the installed SDKs) is http://yfrog.com/h7lk4jp
Investigating here, I found that, with Flex4.6.0 SDK I can compile but I cant debug.
The error is: java.lang.NullPointerException at com.powerflasher.fdt.core.launch.debug.DebugSessionManager.getDebuggerFor(DebugSessionManager.java:50) at com.powerflasher.fdt.core.launch.debug.DebugSessionManager.launchSessionFor(DebugSessionManager.java:97) at com.powerflasher.fdt.core.launch.debug.DebugSessionManager.launchSessionAndKillOld(DebugSessionManager.java:137) at com.powerflasher.fdt.core.internal.launch.debug.concrete.DebuggerStarter.run(DebuggerStarter.java:47) at com.powerflasher.fdt.core.launch.AbstractTargetStarter.runListenerStarters(AbstractTargetStarter.java:61) at com.powerflasher.fdt.core.launch.swf.SwfStarter.run(SwfStarter.java:58) at com.powerflasher.fdt.core.internal.launch.compile.concrete.CompilerProcess$1.run(CompilerProcess.java:226) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) The SessionData: Project Type (right click on Main.as -> FlashProject -> Set Project Type): The problem is: as far as I know, the Flex4.6.0 should be compatible with a empty Main.as on a AS3 project type [SOLVED]
I finally get it. Two steps: 1) Modificate the flex-sdk-description.xml inside FlexSDK 4.60 2) Rename some SWCs inside Flex SDK: It looks like everything is ok now. I will check all and back here if neccessay. Thank you all. I'm a bit confused, what was the finial solution / problem? Is it still happening. This workaround seems odd.
Hi, Alan.
I cant precise what was the problem. Initially looks like FDT couldnt "keep" or understand that a FlexSDK was already set in the sdk panel. Because everytime I started FDT it was complaining "theres no SDK in FDT". To stop that I did the changes on "flex-sdk-description.xml" trick. It fix the "no sdk in FDT" problem. But FDT still having problems with the SDK, but a different one: it was looking for some SWCs that didnt exists inside FlexSDK. So i did the "fix 2", renaming the "flex.swc" and "utilities.swc" to "core.swc" and "authoringsupport.swc". After that, everything looks fine now. My suggestion: make a fix inside FDT to look first for "flex.swc" and "utilities.swc". If FDT can't find it, look for "core.swc" and "authoringsupport.swc". Because I need to "delete" flex and utilities swcs and add, manually, core and utilities swcs in the classpath. As you can see in this video: http://screencast.com/t/T5arpdbkMoPH Thank you. Hey Pedro,
Looks like you're using FDT 4. The other issues is probably a misconnection between the project type and the SDK. The 'AS 3' project type is not set to look for those particular SWCs. There might, if I remember correctly, be a 'AS3 4.5' project type.You'll need to use that with Flex 4.5 & FDT 4.5. Check out FDT 5 and the soon to be released FDT 5.5. FDT 5.5. is particularly good because we really optimized the Project Types and SDKs options. Keep an eye out. It will be released next week! I'm going to close this. b/c this has been fixed in later versions: especially FDT 5.5
@Pedro, check out FDT 5.5. and see how things are there.
Alan K (Deprecated) made changes - 26/Apr/12 07:28 PM
FDT Team made changes - 22/Jun/12 06:32 PM
FDT Team made changes - 22/Jun/12 07:01 PM
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||