Flex: Strange error about unknown dependency

Hi,

from time to time, I run into a strange error where the compiler complains about a dependency that is not found. When this error occurs, the error is shown in the Make log panel and the Flex compiler config file is opened. However, the error does not seem to be correct since the path to the dependency in the error is actually wrong.

For example, when I build my project, I get the following error:

Error: unable to open 'C:/Documentsand Settings/cherrema/.m2/repository/org/springextensions/actionscript/spring-actionscript-core/1.2-SNAPSHOT/spring-actionscript-core-1.2-SNAPSHOT.swc'

Notice the missing space in "Documents and Settings" where "Documentsand" are wrongly concatinated. When I look into the Flex compiler config file, the path IS correct and the dependency is also available at the location on the disk.

I have not found a solution to this error and I have no idea what is causing it. The error somehow just seems to disappear after a series of Maven cleans and IDEA restarts. No need to say that is a real pain as a lot of time is lost each time.

Does anyone have a clue about this?

regards,
Christophe

8 comments
Comment actions Permalink

You are the second who told us about this strange issue. Unfortunately we couldn't reproduce it ourselves and have no idea what can be causing this. If anybody could provide reliable steps to reproduce - that would be greatly appreciated.

0
Comment actions Permalink

Hi Alexander,

thanks for the feedback.

I looked into this a bit more and it seems to happen when there is a compilation error, but that does not get propagated properly to the IDE. In my case, I had a compile error in a statically linked class (but otherwise not referenced/used). One of the method signatures had changed when changing the interface, but the class was not updated. I figured out about this error by doing a command line Maven build.

This only seems to happen when using the built-in compiler shell. When I switched to FCSH, the error was properly shown. So there must be a bug there.

For now I'll switch to using the FCSH. I don't know what I'm missing though by not using the built-in compiler shell. Care to elaborate?

regards,
Christophe

0
Comment actions Permalink

Well, it turns out that FCSH also did not show all the errors properly, so I'm in doubt about whether or not there is an issue in the built-in compiler shell. It did however show errors the first time that were not shown by the built-in compiler shell, but maybe that was a coincidence. I'm heavily thinking now that there is an issue with FCSH that errors are not properly propagated (see previous post).

I switched to MXMLC/COMPC with 1 parallel process as a test and got the errors properly shown.

regards,
Christophe

0
Comment actions Permalink

Thank you for initial evaluation! Ideally we'd like to have all compilers reporting errors in the similar way and to have sensible error messages. Is it possible to create some sample project that generates incorrect or strange errors with any of IDEA's compiler? If you see something strange when using FCSH or MXMLC/COMPC then you can try the same compilation from command line (command is printed in Messages tool window) and compare results (or attach them here).

0
Comment actions Permalink

I ran into this issue again today.

Some more observations:

- 1. I switched back from Flex Mojos 4.0-beta7 to 3.9 (today)
- 2. the order of the dependencies in the pom seems to have an impact on this.

Concerning 2, I had a the following dependencies in the given order:
- flex-framework
- spring-actionscript
- as3-commons

This resulted in an error where the path to the spring-actionscript dependency was not correct.

I moved the SAS dependency to the bottom and then got the error again, but with an incorrect path to as3commons.

I then moved the flex-framework dependency to the bottom, which seemed to compile just fine.

regards,
Christophe

0
Comment actions Permalink

I found the core of this problem and have a potential fix, but it involves patching the Flex compiler.

Please see the details here http://bugs.adobe.com/jira/browse/ASC-4277 and vote for this issue in the hopes to see this resolved.

regards,
Christophe

0
Comment actions Permalink

Thank you for evaluation!

0
Comment actions Permalink

We have workarounded this bug at IntelliJ IDEA and Astella side.

0

Please sign in to leave a comment.