Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 207.46.163.235 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Subject: Re: AW: Flexmojos using Falcon
Thread-Topic: AW: Flexmojos using Falcon
Thread-Index: AQHPrNYjlZuqjTDjX0S/r48mwWGUTg==
Date: Thu, 31 Jul 2014 15:43:14 +0000
Message-ID: <CFFFB171.28BF8%aharui@adobe.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.4.2.140509
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4E8D77F8CD48A14AA0B30AD5F9564F70@namprd02.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

It appears that Flash Builder loads the flex-oem-compiler.jar from the SDK
lib folder.

Is it really impractical to abstract what classes Flexmojos uses?
Falcon's flex-oem-compiler.jar is quite a hack, blending old MXMLC classes
and wiring them to Falcon classes.  But that's because I can't change
FlashBuilder.

-Alex

On 7/31/14 7:27 AM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:

>Ok ... so I have followed this path all day now and I sort of feel like
>walking into a dark and spooky forrest the longer I go ;-)
>
>Simply switching the compiler artifact will probably not do the trick.
>Even if for FlashBuilder falcon seems to be a drop-in-replacement, for
>Flexmojos it's not. A lot of internal clases have been used by Velo in
>the inner workings of Flexmojos. For example in order to trigger a
>compile he calls the static "mxmlc" method inside the flex2.tools.Mxmlc
>class. So how does flashbuilder do this? Does it check the MANIFEST.MF
>file in a jar called compc.jar and mxmlc.jar to know which classes it
>should use? Having a look at the flex-compiler-oem jar sort of seems that
>it's quite tightly coupled to the old packages and Classes.
>
>So how does the FlashBuilder do it? I would like to do it the same way
>for Flexmojos.
>
>Chris
>
>-----Urspr=FCngliche Nachricht-----
>Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
>Gesendet: Mittwoch, 30. Juli 2014 21:33
>An: 'dev@flex.apache.org'
>Betreff: Flexmojos using Falcon
>
>Hi,
>
>so my changes to the falcon build script were actually quite simple. Now
>I have an artifact
>"org.apache.flex.compiler:falcon-compiler:0.0.2-SNAPSHOT in my local repo
>which pulls in all dependencies of the compiler using maven (Yes ... it's
>only one jar we seem to have to provide).
>
>Now I'm doing my first steps with Flexmojos using Falcon and I noticed
>something that I have to change:
>Till now Flexmojos always referenced a default compiler version. So if
>you didn't provide an explicit version, it used the one Flexmojos was
>built against. Now starting with falcon we have different compiler
>artifacts and here the simple "version overriding" of maven no longer
>works. So I was thinking about setting that dependency to "provided", so
>the user has to provide a compiler artifact. The downside is that you
>have to provide something you didn't have to earlier. The good thing is
>that this way you can choose your compiler artifact. Eventually I might
>even be able to bring back together the Adobe and Apache versions of flex
>so Flexmojos could build both worlds (but that would be a goodie, that
>I'll experiment on as soon as Falcon is working).
>
>So keep your fingers crossed that we will be able to build flex
>applications with falcon using flexmojos. If we get the build script
>running on the Apache jenkins we could even get "4.14.0-SNAPSHOT" sdks
>out the door automatically, which would make bleeding-edge experimenting
>a lot easier :)
>
>Chris