Interesting. IJ goes down a completely different code path than FB.
Something to keep in mind for the future. Thanks for figuring it out.
-Alex
On 7/6/17, 2:15 PM, "Josh Tynjala" wrote:
>Unfortunately, there is no workaround for 0.8.0. Even if we try to use
>-js-output-type instead, it tries
Unfortunately, there is no workaround for 0.8.0. Even if we try to use
-js-output-type instead, it tries to call a constructor that simply doesn't
exist anymore. We didn't get compiler errors to tell us that this had
broken because it it used reflection to find that constructor.
- Josh
On Jul 6,
Thanks for noticing that. So does that mean a workaround for 0.8.0 is to
define in additional compiler options:
-js-output-type=FLEXJS
-Alex
On 7/6/17, 11:46 AM, "Josh Tynjala" wrote:
>Okay, I made a commit that seems to get things working in IntelliJ IDEA
>again. It looks like MxmlJSC a
Josh,
That's great news! :) I will try it out once falcon build on server. It look
like confluence need to be updated as well. Point 9 seems to be out of date
in the instruction.
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-fle
Okay, I made a commit that seems to get things working in IntelliJ IDEA
again. It looks like MxmlJSC and CompJSC in flex-compiler-oem.jar no longer
need to create the backend manually, and MXMLJSC or COMPJSC can figure out
what to do automatically based on the value of -targets now.
I was able to
By the way, I'd like to know what kind of extra problems you are seeing (in
another thread please) because that's not an issue I've encountered with
VSCode.
- Josh
On Thu, Jul 6, 2017 at 11:16 AM, Harbs wrote:
> VS Code is reporting all kinds of issues that are not problems since the
> switch t
The problem looks to be related to this line:
compiler =
COMPILER.getDeclaredConstructor(IBackend.class).newInstance(backend);
It's looking for a constructor on MXMLJSC (not to be confused with MxmlJSC)
that takes an IBackend as a parameter. There is no longer a constructor
like that in 0.8.0. If
The issue with IntelliJ IDEA on seems to be related to
flex-compiler-oem.jar, which VSCode doesn't use at all.
- Josh
On Thu, Jul 6, 2017 at 11:16 AM, Harbs wrote:
> VS Code is reporting all kinds of issues that are not problems since the
> switch to dual. Maybe that’s related as well?
>
> > On
VS Code is reporting all kinds of issues that are not problems since the switch
to dual. Maybe that’s related as well?
> On Jul 6, 2017, at 9:06 PM, Josh Tynjala wrote:
>
> I don't see why -targets wouldn't work when it works elsewhere, but I just
> tried -compiler.targets too, and that also fa
I don't see why -targets wouldn't work when it works elsewhere, but I just
tried -compiler.targets too, and that also failed.
Looking at the source code for flex2.tools.MxmlJSC, I see that it's still
checking for the -js-output-type option, and it isn't trying to find
-targets at all. Did you forg
What does IJ do with additional compiler options? Does it put them in one
of the .xml files? I can see from the original post that IJ seems to be
using:
-load-config=/Users/joshtynjala/Library/Caches/IntelliJIdea2017.1/compile-s
erver/helloidea_6d5abd99/_temp_/IntelliJ_IDEA/idea-B028A5AE-12E86E2
I tried specifying -targets=JSFlex in the additional compiler options, but
it made no difference.
- Josh
On Thu, Jul 6, 2017 at 9:09 AM, Alex Harui wrote:
> I suspect the issue is that IJ dictates all of the settings and doesn't
> use flex-config.xml, and thus no targets are being specified. I
I suspect the issue is that IJ dictates all of the settings and doesn't
use flex-config.xml, and thus no targets are being specified. Is there a
way to specify compiler.targets in additional compiler options in IJ?
There is in FB.
-Alex
On 7/6/17, 8:34 AM, "Josh Tynjala" wrote:
>While full sup
While full support for FlexJS in IntelliJ IDEA would be great, I think it's
critical that we fix this issue to at least get back to the baseline we had
in 0.7. A FlexJS project required a little bit of extra configuration with
0.7, but at least we could get the compiler to work inside IntellIJ.
Ma
As I remember Chris get to the bottom of it and resolved it. Unfortunately
after contacting with Jetbrains they refuse accept pull request with fix and
Chris dropped it. [1]
I was thinking even then that if someone could fix it and store version of
plugin somewhere with fix it would be also HUGE,
Hi,
> I was trying some time ago to do as you are doing and failed. - Not sure
> whether it was same problem. After some time I gave up.
>
> The conclusion is that I end up with pom for Maven build and setup where the
> intelisence is working.
That mirrors my experience as well. I know Chris l
Hi Josh,
I was trying some time ago to do as you are doing and failed. - Not sure
whether it was same problem. After some time I gave up.
The conclusion is that I end up with pom for Maven build and setup where the
intelisence is working.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.co
I'm trying to create a new FlexJS 0.8.0 project in IntelliJ IDEA, and I'm
getting the following output when I try to build the project:
Information:[HelloIDEA]: Starting Flex compiler:
"/Applications/IntelliJ IDEA.app/Contents/jdk/Contents/Home/jre/bin/java"
-Dapplication.home=/Users/joshtynjala/D
18 matches
Mail list logo
