flex / air module build configuration dependency

Hi,

Adding another flex module's build configuration as a dependency of a flex/air module doesn't seem to have any effect on the editor's code hightlighting. (compiling/making isn't a problem though)
I.e. the editor doesn't recognize the classes included in the library project that was added as dependency. (adding the swc directly does do the trick, but is kindof a hassle since the every code change in that library needs to be compiled)
Am I missing something here? (I'm using the latest idea EAP)

Cheers,

Bert

5 comments

If you have more than one build configuration (BC) in Flash module then you can select which one should be used for highlighting of the edited file: active BC is selected in the status bar. Make sure that the BC with dependency on other BC is selected there.
Configuring dependency on swc produced by other BC should never be done of course, BC-on-BC dependency should affect highlighting. If you don't have any idea what's wrong please give some more details on the problem, e.g. screenshots of the problem and of the build configuration dependencies and specify where affected files are located.

0

Hi Alexander,

There is only one BC in each flex module and the correct BC is selected in the status bar.
Both module's BC target a desktop environment.
Both module's files are in sibling folders under the same root directory.

I've included some BC dependency screens and a screenshot of the unresolved types problem.

Cheers,

Bert



Attachment(s):
problem.PNG
bc_dependency.PNG
bc_app.PNG
0

Thanks,
as I understand, mxml file with WindowedApplication root (from screenshot) is in 'vhintra-shell' module and red classes (like MainPresentationModel) are in 'shell-bootstrap' module, right?
Configuration seems to be correct, but it's strange that one module came from maven/flexmojos import whereas the other one references standard non-flexmojos sdk. Is  'vhintra-shell' module created manually and doesn't have related pom.xml or the module configuraion was manually updated after reimport? The latter can potentially cause highighting problems - IntelliJ IDEA may continue to use maven dependencies even if you have changed Flexmojos SDK to the standard Flex SDK.

0

Hi,

The windowedapp is indeed the vhintra-shell and the missing classes are in the dependent library.
The vhintra shell does have a pom, and I was using the flexmojos related sdk before, but in that case, the code hightlighting was even worse (all flex framework classes weren't recognized)

All other modules are using the flexmojos related sdk without any issue.

Cheers,

Bert

0

Does vhintra-shell pom contain dependency on shell-bootstrap pom? I mean have you added dependency on 'shell-bootstrap' BC manually or it appeared after reimport from maven?

In any case first of all we should figure out why vhintra-shell was imported from maven incorrectly. Can you please attach a screenshot of the Dependencies tab of the vhintra-shell BC just after reimport from maven? Is it possible to attach your vhintra-shell pom and referenced parent pom(s)? We can continue problem evaluation privately: alexander dot doroshko at jetbrains.com

0

Please sign in to leave a comment.