flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [FALCON/JX] guava dependencies in compiler AND closure
Date Fri, 01 Nov 2013 14:41:26 GMT
Makes sense to upgrade Guava.  That's out of my comfort zone and it
appears you got around the problem, so is there a set of steps we can
record here or in the wiki for the next person to hit it?


On 11/1/13 5:32 AM, "Erik de Bruin" <erik@ixsoftware.nl> wrote:

>While trying to get my local development setup in order, I kept
>getting errors when trying to run FalconJx on the examples. The
>FalconJx tests run fine, so it's not the compiler perse... Some (ha!)
>digging later, I stumbled on the following: both Falcon and the
>Closure Compiler (CC) are dependent on the Guava library.
>Now the problem: Falcon uses Guava r08. The latest CC seems to use a
>much more recent version (the latest is 15). This causes problems when
>doing a full build on a FalconJx project, which invokes the CC to
>build the release JS. It turns out that more recent versions of Guava
>deprecated several members of the MapMaker class, as well as hide some
>others. This prevents Falcon from being compiled using a recent
>version of Guava.
>I don't think it is a good idea to keep relying on an old (2011)
>version of Guava, thereby also locking us also to an old version of
>the CC. The best way to fix this is to follow the documentation here
>[1][2] and move Falcon to the most recent version of Guava. This does
>require some refactoring - use CacheBuilder instead of MapMaker,
>apparently - that is beyond my capability to reliably execute.
>Any one of the compiler insiders brave or foolish enough to take this
>one? Pretty please?!?
>Ix Multimedia Software
>Jan Luykenstraat 27
>3521 VB Utrecht
>T. 06-51952295
>I. www.ixsoftware.nl

View raw message