> Does Java 12 have Java 1.6 target compatibility?
No. It got an error on both target and source.
> On May 15, 2019, at 6:54 PM, Alex Harui wrote:
>
> That's fine, although I think the more common pattern is to require use of
> env.properties and/or local.properties files.
>
> It occurs to me
and-target-compatibility
>
>
>
>
> From: Alex Harui
> Sent: Wednesday, May 15, 2019 6:54:13 PM
> To: dev@royale.apache.org
> Subject: Re: Problems with Java 12
>
> That's fine, although I think the more common pattern is to req
@royale.apache.org
Subject: Re: Problems with Java 12
That's fine, although I think the more common pattern is to require use of
env.properties and/or local.properties files.
It occurs to me that regarding Flash Builder, the source compatibility is less
important than the target compatibility. Does
That's fine, although I think the more common pattern is to require use of
env.properties and/or local.properties files.
It occurs to me that regarding Flash Builder, the source compatibility is less
important than the target compatibility. Does Java 12 have Java 1.6 target
compatibility?
-Al
Yeah. Looks like the problem. Thanks.
Maybe we should keep 1.6 the default, but allow a environment variable to set
it higher?
> On May 15, 2019, at 9:58 AM, Alex Harui wrote:
>
> Looks like royale-asjs/build.xml specifies 1.5. That's probably an
> accidental copy from Flex.
>
> That said,
Looks like royale-asjs/build.xml specifies 1.5. That's probably an accidental
copy from Flex.
That said, I'm not sure that flex-compiler-oem will work with Flash Builder if
the target is not 1.6. If that's true, we'll need some way to not build that
jar on Java 12.
-Alex
On 5/14/19, 11:49
Progress.
I was building using `ant all` on asjs.
When I build using `ant` on royale-compiler, I got a bunch of errors:
[javac] warning: [options] bootstrap class path not set in conjunction with
-source 6
[javac] error: Source option 6 is no longer supported. Use 7 or later.
[javac] er
I just switched to compiler-build-tools, ran "ant clean" then "ant". The
console said
"warning: [options] bootstrap class path not set in conjunction with -source
1.6"
What do you get? Maybe the main build.xml sets something but I didn't see it.
Swfutils sets 1.5. That can probably be chan
Most of the build files were set to 1.6. There was one set to 1.5 (I don’t
remember off-hand which one.
Changing all of them did not help.
I have no idea where this is being picked up from. Is it possible Maven
artifacts are coming into play?
> On May 14, 2019, at 6:29 PM, Alex Harui wrote:
>
I can't figure out why your build is trying to use 1.5. My build.xml for
compiler-build-tools is using 1.6.
-Alex
On 5/14/19, 3:46 AM, "Harbs" wrote:
I’m setting up a new Windows machine and I installed Java 12. I can’t get
Royale to compile. I keep getting this error:
annotate
I’m setting up a new Windows machine and I installed Java 12. I can’t get
Royale to compile. I keep getting this error:
annotate.class:
[javac] Compiling 1 source file to
C:\Apache\royale-compiler\compiler-build-tools\target\classes
[javac] warning: [options] bootstrap class path not set i
11 matches
Mail list logo
