That's what you need to do with any FlexJS SDK. Not just the Maven version. IntelliJ IDEA would need to fix this. Not us. It's the same with the Feathers SDK too.
I spent many hours trying to find a workaround, but I think there's no working around the assumptions that Jetbrains made about Flex SDKs. I think I determined that they only bother checking for manifests in the SWCs in frameworks/libs if you explicitly add it, even though frameworks/libs is already on the library path by default. - Josh On Jan 16, 2017 7:31 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote: Chris, I will test it later today, but question is even more extensive. What actually should be done in order to have components being recognizable ? Currently If I do not add SDK as an Library additionally I don't have intelli sence support etc. Piotr ----- Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex- development.2333347.n4.nabble.com/FlexJS-Fixed-a-bug-in-the- distribution-generation-IntelliJ-now-accepts-distribution-tp58352p58355.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
