That’s what I have been using to find out what was wrong with my distribution …
now if someone would explain what’s missing, I could have a look at it (Being a
Jetbrains Fanboy I guess I have to make my favorite IDE play nice with FlexJS
;-) )
Chris
Am 16.01.17, 17:40 schrieb "Alex Harui" <aha...@adobe.com>:
AIUI, the source for IntelliJ Flex support is here [1]?
I believe we have been invited to fix it.
-Alex
[1] https://github.com/JetBrains/intellij-plugins/tree/master/flex
On 1/16/17, 7:51 AM, "Josh Tynjala" <joshtynj...@gmail.com> wrote:
>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.ht
>ml
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
