flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject AW: [FALCONJX] Jdk 1.6 incompatability in debugger module
Date Wed, 27 Apr 2016 13:22:44 GMT
No, this is if you execute the maven build.
It's the animal-sniffer-plugin (http://www.mojohaus.org/animal-sniffer/animal-sniffer-maven-plugin/)
that's complaining.
Not only should we not use it cause it's internal, it also doesn't seem to be available in

[INFO] --- animal-sniffer-maven-plugin:1.15:check (check-jdk-1.6) @ debugger ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java16:1.1
[ERROR] /Users/christoferdutz/Projects/Apache/Flex/flex-falcon/debugger/src/main/java/flex/tools/debugger/cli/DebugCLI.java:488:
Undefined reference: java.util.Locale com.sun.org.apache.xml.internal.utils.LocaleUtility.langToLocale(String)
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------

So it claims the call "java.util.Locale com.sun.org.apache.xml.internal.utils.LocaleUtility.langToLocale(String)"
doesn't exist in the signature of Java 1.6


Von: Alex Harui <aharui@adobe.com>
Gesendet: Mittwoch, 27. April 2016 15:08:08
An: dev@flex.apache.org
Betreff: Re: [FALCONJX] Jdk 1.6 incompatability in debugger module

For me, it is a warning:

/debugger/cli/DebugCLI.java:487: warning: LocaleUtility is internal
proprietary API and may be removed in a future release

Maybe there is a way to turn your error into a warning?  Or a replacement
for LocaleUtility?


On 4/27/16, 5:43 AM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:

>I just implemented the Maven build for the debugger module and
>encountered a problem.
>As I configured the animal-sniffer-plugin to check the output for
>compatibility with JDK 1.6, the plugin started complaining that it's not
>possible to use DebugCLI on a 1.6 VM. The line it's complaining about is
>Seems to be incompatible to 1.6. How do we proceed here? As it's getting
>impossible to get my hands on a 1.6 VM on my Mac I would like to update
>to 1.7 as base-line Java Version, what do you think? If we can't get the
>environment, how should we support it? Or we refactor this line so it's
>compatible with 1.6.
>I'm commenting that line out for now ... we should however solve the
>problem somehow.

View raw message