|
Project
|
IntelliJ IDEA
|
|
Priority
|
Normal |
|
Type
|
Bug |
|
Fix versions
|
No Fix versions |
|
State
|
Duplicate |
|
Assignee
|
Alexander Doroshko |
|
Subsystem
|
Flash/Flex |
|
Affected versions
|
No Affected versions |
|
Fixed in build
|
No Fixed in build
|
<log4j:configuration> <category name="com.intellij.lang.javascript.flex.debug"> <priority value="DEBUG"/> </category> ...- launch IDEA, set only one breakpoint (that will become (x)), launch Flex debug process. Make sure that breakpoint became (x)
After that log.xml will contain the reason of unresolved breakpoint. Please attach it to the issue.Attempting to resolve breakpoint 2, expression "ModulesManager.as:23":
There is no executable code on the specified line.
It seems that for some reason source of this class does not match runtime code.
794 C:\dev\projects\mmp-core-4-8-0\modules\mmp-core\mobile-crm\net.velti.crm.flex\src\main\flex\flex\ModulesManager.as, ModulesManager.as
it points to the file where my source located
Yes, everything seems to go correct except unexpected response of Flex Debugger (fdb tool) that "There is no executable code on the specified line".
Do breakpoints work for neighbor classes?
and breakpoint does not work in any place except main module(flex application)
Is it possible to create some minimal project in which the issue is reproduced? I suppose it's a project with 2 modules: Flex application and Flex module with 1 class in each module.
<flex.debug>true</flex.debug>
i use maven for that
i'm using intellij idea for debug and edit (build with maven only)
Yes, it can.
IDEA 8.1.3 takes fdb.exe from that SDK.
As I see you have Flex SDK 3.0.0. Probably fdb tool of that old version has some bugs.
Please try to configure Flex SDK 3.3.0 for all facets
hvae you tested it with player 10... because it worked with 9 but with 10 i still can not debug....
And did you try to change facet SDK to version 3.3.0.4852? In IDEA debug console you should see:
Can it happen that it is of version 9?
<groupId>org.sonatype.flexmojos</groupId>
<artifactId>flexmojos-maven-plugin</artifactId>
<configuration>
<quick>true</quick>
<contextRoot>dashboard-module</contextRoot>
<sourceFile>CommunitiesDashboard.mxml</sourceFile>
<debug>${flex.debug}</debug>
<verifyDigests>${flex.verify.digests}</verifyDigests>
<compiledLocales>
<locale>en_US</locale>
<locale>fr_FR</locale>
<!– locale>ru_RU</locale–>
</compiledLocales>
</configuration>
Can you please try latest EAP from http://www.jetbrains.net/confluence/display/IDEADEV/Maia+EAP
and attach logs acquired in the same way as written in the first comment to this issue (i.e. clean old logs, use 1 breakpoint that becomes (x)).
Error during dispatching of java.awt.event.InvocationEvent[INVOCATION_DEFAULT,runnable=com.intellij.openapi.roots.ui.configuration.projectRoot.daemon.ProjectStructureDaemonAnalyzer$2@7c448e,notifier=null,catchExceptions=false,when=1258996450416] on sun.awt.windows.WToolkit@1457184: com.intellij.ui.treeStructure.NullNode cannot be cast to com.intellij.openapi.roots.ui.configuration.artifacts.nodes.PackagingElementNode
As for sdk resolving problems: I'm afraid you need to open each Flex facet settings dialog and make sure that there's no 'exclaimer' mark in Flex SDK combobox.
By the way in IDEA 9 you may skip all manual configuration (including Flex SDK) when working with Flexmojos projects. You may import the whole project as described here: http://blogs.jetbrains.com/idea/2009/09/flexmojos-inmaia/
The most reliable way is that described at the end of that blog post, i.e. with <configurationReport> tag and successful 'mvn compile' before importing.
If the code remains red then please open Dependencies tab of module mcrm-main-flex. There should be a lot of libraries called Maven: ...'. Among them should be 'Maven: com.adobe.flex.framework:framework:swc:3.3.0.4852'. Press Edit button for this library and make sure that framework-3.3.0.4852.swc file is added as Classes and it is black (Sources and Docs entries are probably red - it doesn't matter). Presence of this file is enough for <mx:Application/> component resolving.
Another way to check that mx.core.Aplication class is loaded - press Ctrl+N and type 'Application'.
Error:Error: Cannot access compiler output path.
C:\Documents and Settings\mil\.m2\repository\com\adobe\flex\framework\applicationupdater\3.3.0.4852\applicationupdater-3.3.0.4852.swc
Error:Error:Can not calculate name of output bundle, rename jar or use -properties
user description is welcome in any case.
I still had no luck reproducing it myself though tried a lot of times. Sample project is still very much welcome because I'd like to workaround this Adobe's bug in IDEA.