You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Christofer Dutz <ch...@c-ware.de> on 2014/07/13 16:42:39 UTC
Mavenizing Falcon
Hi,
After my latest Mavenizer and Flexmojos changes seem to compile all of my Flex projects without problems, I wanted to get started on adding Falcon support.
Now instead of re-deploying the entire compiler, I would much more like to have the falcon-compiler depend on the normal compiler by referencing the falcon libs and adding a dependency on the normal compiler artifact and exclude the old compiler libs.
Could someone here on the list please describe me exactly which libs Falcon consists of and where I can get them from as well as which libs in the classic sdk are needed? I think being able to switch the compilers by changing a dependency in maven would make experimenting a lot easier.
Chris
AW: Mavenizing Falcon
Posted by Christofer Dutz <ch...@c-ware.de>.
Wow ... ok ... didn't know he was working on making falcon buildable by maven ... but that surely would completeley eliminate the need for me to mavenize anything at all.
Thanks for pointing that out ... Will write my feedback in a separate thread.
Chris
________________________________________
Von: omuppi1@gmail.com <om...@gmail.com> im Auftrag von OmPrakash Muppirala <bi...@gmail.com>
Gesendet: Dienstag, 15. Juli 2014 01:20
An: dev@flex.apache.org
Betreff: Re: Mavenizing Falcon
Just curious, how is this related to Jose Barragan's work on the
flex-falcon maven branch [1]?
Thanks,
Om
[1]
https://git-wip-us.apache.org/repos/asf/flex-falcon/repo?p=flex-falcon.git;a=shortlog;h=refs/heads/maven
On Mon, Jul 14, 2014 at 2:11 AM, Christofer Dutz <ch...@c-ware.de>
wrote:
> I think the problem with this is that nobody is maintaining FlashBuilder
> anymore, so if we want to switch the Compiler, we have to trick it into
> beleaving it's the old compiler.
> I bet the IntelliJ guys would take about 5 minutes to implement support
> for both compilers at the same time, but as long as we can't change the
> FlashBuilder this seems to be the best solution.
>
> Chris
>
>
>
> ________________________________________
> Von: Erik de Bruin <er...@ixsoftware.nl>
> Gesendet: Sonntag, 13. Juli 2014 19:25
> An: dev@flex.apache.org
> Betreff: Re: Mavenizing Falcon
>
> Ideally, we would have both the 'old compiler' and Falcon in the normal
> SDK. This would, I think, benefit all three projects - yours, FlexJS/VF2JS
> and the normal SDK itself (the latter because it would help start the
> transition from 'old' to 'new'.
>
> EdB
>
>
>
>
> On Sun, Jul 13, 2014 at 7:03 PM, Christofer Dutz <
> christofer.dutz@c-ware.de>
> wrote:
>
> > Just forgot to ask,
> >
> > Another question ... when using Falcon, is there any difference in the
> > Framework part? Are the swcs the same as in the normal SDK? If yes, what
> > exactly is different?
> >
> > At least this would be what I am currently expecting. I know I will have
> > to reference other things when starting to use FlexJS, but at the moment
> I
> > just want to have my application compiled using the new Compiler.
> >
> > Chris
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Alex Harui [mailto:aharui@adobe.com]
> > Gesendet: Sonntag, 13. Juli 2014 17:54
> > An: dev@flex.apache.org
> > Betreff: Re: Mavenizing Falcon
> >
> > Gordon or Darrell might know the real answer.
> >
> > If you build the Falcon repo or unpack a binary package, you should see a
> > compiler/lib folder. In it are the external dependencies require by the
> > build. Antlr, Commons-io, Commons-cli, guava, Jburg, Jflex, LZMA.
> >
> > Pretty sure Jburg is need to build, but not to run. Pretty sure
> > Commons-io and Commons-cli is need to run as well as LZMA.
> >
> > Not sure about Antr and Jflex. Might only be build tools.
> >
> > In generated/dist/sdk/lib are the jars that result from the build. They
> > are:
> > Compiler.jar
> > Falcon-asc.jar
> > Falcon-compc.jar
> > Falcon-mxmlc.jar
> > Falcon-optimizer.jar
> > Falcon-swfdump.jar
> > Flex-oem-compiler.jar
> >
> > Pretty sure you want the first 5, although really, I think falcon-asc,
> > falcon-compc, falcon-mxmlc use call compiler.jar. Not sure how the
> > optimizer works. The 5 jars can be moved into a lib folder with the
> > compiler/lib jars so they are all in one place.
> >
> > You don't need falcon-swfdump unless you want to dump SWFs, and
> > flex-oem-compiler.jar is only for FB integration.
> >
> > AFAIK, these jars do not have dependencies on the current Flex SDK. When
> > we build up an overlaid SDK we move the current SDK compiler to a
> > bin-legacy and lib-legacy folder, but that's just so folks can revert
> back
> > if Falcon isn't working. Also, the old SWFDump is much better, IMO.
> >
> > HTH
> > -Alex
> >
> > On 7/13/14 7:42 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
> >
> > >Hi,
> > >
> > >After my latest Mavenizer and Flexmojos changes seem to compile all of
> > >my Flex projects without problems, I wanted to get started on adding
> > >Falcon support.
> > >Now instead of re-deploying the entire compiler, I would much more like
> > >to have the falcon-compiler depend on the normal compiler by
> > >referencing the falcon libs and adding a dependency on the normal
> > >compiler artifact and exclude the old compiler libs.
> > >
> > >Could someone here on the list please describe me exactly which libs
> > >Falcon consists of and where I can get them from as well as which libs
> > >in the classic sdk are needed? I think being able to switch the
> > >compilers by changing a dependency in maven would make experimenting a
> > lot easier.
> > >
> > >Chris
> >
> >
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>
Re: Mavenizing Falcon
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Just curious, how is this related to Jose Barragan's work on the
flex-falcon maven branch [1]?
Thanks,
Om
[1]
https://git-wip-us.apache.org/repos/asf/flex-falcon/repo?p=flex-falcon.git;a=shortlog;h=refs/heads/maven
On Mon, Jul 14, 2014 at 2:11 AM, Christofer Dutz <ch...@c-ware.de>
wrote:
> I think the problem with this is that nobody is maintaining FlashBuilder
> anymore, so if we want to switch the Compiler, we have to trick it into
> beleaving it's the old compiler.
> I bet the IntelliJ guys would take about 5 minutes to implement support
> for both compilers at the same time, but as long as we can't change the
> FlashBuilder this seems to be the best solution.
>
> Chris
>
>
>
> ________________________________________
> Von: Erik de Bruin <er...@ixsoftware.nl>
> Gesendet: Sonntag, 13. Juli 2014 19:25
> An: dev@flex.apache.org
> Betreff: Re: Mavenizing Falcon
>
> Ideally, we would have both the 'old compiler' and Falcon in the normal
> SDK. This would, I think, benefit all three projects - yours, FlexJS/VF2JS
> and the normal SDK itself (the latter because it would help start the
> transition from 'old' to 'new'.
>
> EdB
>
>
>
>
> On Sun, Jul 13, 2014 at 7:03 PM, Christofer Dutz <
> christofer.dutz@c-ware.de>
> wrote:
>
> > Just forgot to ask,
> >
> > Another question ... when using Falcon, is there any difference in the
> > Framework part? Are the swcs the same as in the normal SDK? If yes, what
> > exactly is different?
> >
> > At least this would be what I am currently expecting. I know I will have
> > to reference other things when starting to use FlexJS, but at the moment
> I
> > just want to have my application compiled using the new Compiler.
> >
> > Chris
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Alex Harui [mailto:aharui@adobe.com]
> > Gesendet: Sonntag, 13. Juli 2014 17:54
> > An: dev@flex.apache.org
> > Betreff: Re: Mavenizing Falcon
> >
> > Gordon or Darrell might know the real answer.
> >
> > If you build the Falcon repo or unpack a binary package, you should see a
> > compiler/lib folder. In it are the external dependencies require by the
> > build. Antlr, Commons-io, Commons-cli, guava, Jburg, Jflex, LZMA.
> >
> > Pretty sure Jburg is need to build, but not to run. Pretty sure
> > Commons-io and Commons-cli is need to run as well as LZMA.
> >
> > Not sure about Antr and Jflex. Might only be build tools.
> >
> > In generated/dist/sdk/lib are the jars that result from the build. They
> > are:
> > Compiler.jar
> > Falcon-asc.jar
> > Falcon-compc.jar
> > Falcon-mxmlc.jar
> > Falcon-optimizer.jar
> > Falcon-swfdump.jar
> > Flex-oem-compiler.jar
> >
> > Pretty sure you want the first 5, although really, I think falcon-asc,
> > falcon-compc, falcon-mxmlc use call compiler.jar. Not sure how the
> > optimizer works. The 5 jars can be moved into a lib folder with the
> > compiler/lib jars so they are all in one place.
> >
> > You don't need falcon-swfdump unless you want to dump SWFs, and
> > flex-oem-compiler.jar is only for FB integration.
> >
> > AFAIK, these jars do not have dependencies on the current Flex SDK. When
> > we build up an overlaid SDK we move the current SDK compiler to a
> > bin-legacy and lib-legacy folder, but that's just so folks can revert
> back
> > if Falcon isn't working. Also, the old SWFDump is much better, IMO.
> >
> > HTH
> > -Alex
> >
> > On 7/13/14 7:42 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
> >
> > >Hi,
> > >
> > >After my latest Mavenizer and Flexmojos changes seem to compile all of
> > >my Flex projects without problems, I wanted to get started on adding
> > >Falcon support.
> > >Now instead of re-deploying the entire compiler, I would much more like
> > >to have the falcon-compiler depend on the normal compiler by
> > >referencing the falcon libs and adding a dependency on the normal
> > >compiler artifact and exclude the old compiler libs.
> > >
> > >Could someone here on the list please describe me exactly which libs
> > >Falcon consists of and where I can get them from as well as which libs
> > >in the classic sdk are needed? I think being able to switch the
> > >compilers by changing a dependency in maven would make experimenting a
> > lot easier.
> > >
> > >Chris
> >
> >
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>
AW: Mavenizing Falcon
Posted by Christofer Dutz <ch...@c-ware.de>.
I think the problem with this is that nobody is maintaining FlashBuilder anymore, so if we want to switch the Compiler, we have to trick it into beleaving it's the old compiler.
I bet the IntelliJ guys would take about 5 minutes to implement support for both compilers at the same time, but as long as we can't change the FlashBuilder this seems to be the best solution.
Chris
________________________________________
Von: Erik de Bruin <er...@ixsoftware.nl>
Gesendet: Sonntag, 13. Juli 2014 19:25
An: dev@flex.apache.org
Betreff: Re: Mavenizing Falcon
Ideally, we would have both the 'old compiler' and Falcon in the normal
SDK. This would, I think, benefit all three projects - yours, FlexJS/VF2JS
and the normal SDK itself (the latter because it would help start the
transition from 'old' to 'new'.
EdB
On Sun, Jul 13, 2014 at 7:03 PM, Christofer Dutz <ch...@c-ware.de>
wrote:
> Just forgot to ask,
>
> Another question ... when using Falcon, is there any difference in the
> Framework part? Are the swcs the same as in the normal SDK? If yes, what
> exactly is different?
>
> At least this would be what I am currently expecting. I know I will have
> to reference other things when starting to use FlexJS, but at the moment I
> just want to have my application compiled using the new Compiler.
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Sonntag, 13. Juli 2014 17:54
> An: dev@flex.apache.org
> Betreff: Re: Mavenizing Falcon
>
> Gordon or Darrell might know the real answer.
>
> If you build the Falcon repo or unpack a binary package, you should see a
> compiler/lib folder. In it are the external dependencies require by the
> build. Antlr, Commons-io, Commons-cli, guava, Jburg, Jflex, LZMA.
>
> Pretty sure Jburg is need to build, but not to run. Pretty sure
> Commons-io and Commons-cli is need to run as well as LZMA.
>
> Not sure about Antr and Jflex. Might only be build tools.
>
> In generated/dist/sdk/lib are the jars that result from the build. They
> are:
> Compiler.jar
> Falcon-asc.jar
> Falcon-compc.jar
> Falcon-mxmlc.jar
> Falcon-optimizer.jar
> Falcon-swfdump.jar
> Flex-oem-compiler.jar
>
> Pretty sure you want the first 5, although really, I think falcon-asc,
> falcon-compc, falcon-mxmlc use call compiler.jar. Not sure how the
> optimizer works. The 5 jars can be moved into a lib folder with the
> compiler/lib jars so they are all in one place.
>
> You don't need falcon-swfdump unless you want to dump SWFs, and
> flex-oem-compiler.jar is only for FB integration.
>
> AFAIK, these jars do not have dependencies on the current Flex SDK. When
> we build up an overlaid SDK we move the current SDK compiler to a
> bin-legacy and lib-legacy folder, but that's just so folks can revert back
> if Falcon isn't working. Also, the old SWFDump is much better, IMO.
>
> HTH
> -Alex
>
> On 7/13/14 7:42 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>
> >Hi,
> >
> >After my latest Mavenizer and Flexmojos changes seem to compile all of
> >my Flex projects without problems, I wanted to get started on adding
> >Falcon support.
> >Now instead of re-deploying the entire compiler, I would much more like
> >to have the falcon-compiler depend on the normal compiler by
> >referencing the falcon libs and adding a dependency on the normal
> >compiler artifact and exclude the old compiler libs.
> >
> >Could someone here on the list please describe me exactly which libs
> >Falcon consists of and where I can get them from as well as which libs
> >in the classic sdk are needed? I think being able to switch the
> >compilers by changing a dependency in maven would make experimenting a
> lot easier.
> >
> >Chris
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Mavenizing Falcon
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Ideally, we would have both the 'old compiler' and Falcon in the normal
SDK. This would, I think, benefit all three projects - yours, FlexJS/VF2JS
and the normal SDK itself (the latter because it would help start the
transition from 'old' to 'new'.
EdB
On Sun, Jul 13, 2014 at 7:03 PM, Christofer Dutz <ch...@c-ware.de>
wrote:
> Just forgot to ask,
>
> Another question ... when using Falcon, is there any difference in the
> Framework part? Are the swcs the same as in the normal SDK? If yes, what
> exactly is different?
>
> At least this would be what I am currently expecting. I know I will have
> to reference other things when starting to use FlexJS, but at the moment I
> just want to have my application compiled using the new Compiler.
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Sonntag, 13. Juli 2014 17:54
> An: dev@flex.apache.org
> Betreff: Re: Mavenizing Falcon
>
> Gordon or Darrell might know the real answer.
>
> If you build the Falcon repo or unpack a binary package, you should see a
> compiler/lib folder. In it are the external dependencies require by the
> build. Antlr, Commons-io, Commons-cli, guava, Jburg, Jflex, LZMA.
>
> Pretty sure Jburg is need to build, but not to run. Pretty sure
> Commons-io and Commons-cli is need to run as well as LZMA.
>
> Not sure about Antr and Jflex. Might only be build tools.
>
> In generated/dist/sdk/lib are the jars that result from the build. They
> are:
> Compiler.jar
> Falcon-asc.jar
> Falcon-compc.jar
> Falcon-mxmlc.jar
> Falcon-optimizer.jar
> Falcon-swfdump.jar
> Flex-oem-compiler.jar
>
> Pretty sure you want the first 5, although really, I think falcon-asc,
> falcon-compc, falcon-mxmlc use call compiler.jar. Not sure how the
> optimizer works. The 5 jars can be moved into a lib folder with the
> compiler/lib jars so they are all in one place.
>
> You don't need falcon-swfdump unless you want to dump SWFs, and
> flex-oem-compiler.jar is only for FB integration.
>
> AFAIK, these jars do not have dependencies on the current Flex SDK. When
> we build up an overlaid SDK we move the current SDK compiler to a
> bin-legacy and lib-legacy folder, but that's just so folks can revert back
> if Falcon isn't working. Also, the old SWFDump is much better, IMO.
>
> HTH
> -Alex
>
> On 7/13/14 7:42 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>
> >Hi,
> >
> >After my latest Mavenizer and Flexmojos changes seem to compile all of
> >my Flex projects without problems, I wanted to get started on adding
> >Falcon support.
> >Now instead of re-deploying the entire compiler, I would much more like
> >to have the falcon-compiler depend on the normal compiler by
> >referencing the falcon libs and adding a dependency on the normal
> >compiler artifact and exclude the old compiler libs.
> >
> >Could someone here on the list please describe me exactly which libs
> >Falcon consists of and where I can get them from as well as which libs
> >in the classic sdk are needed? I think being able to switch the
> >compilers by changing a dependency in maven would make experimenting a
> lot easier.
> >
> >Chris
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
AW: Mavenizing Falcon
Posted by Christofer Dutz <ch...@c-ware.de>.
Just forgot to ask,
Another question ... when using Falcon, is there any difference in the Framework part? Are the swcs the same as in the normal SDK? If yes, what exactly is different?
At least this would be what I am currently expecting. I know I will have to reference other things when starting to use FlexJS, but at the moment I just want to have my application compiled using the new Compiler.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Sonntag, 13. Juli 2014 17:54
An: dev@flex.apache.org
Betreff: Re: Mavenizing Falcon
Gordon or Darrell might know the real answer.
If you build the Falcon repo or unpack a binary package, you should see a compiler/lib folder. In it are the external dependencies require by the build. Antlr, Commons-io, Commons-cli, guava, Jburg, Jflex, LZMA.
Pretty sure Jburg is need to build, but not to run. Pretty sure Commons-io and Commons-cli is need to run as well as LZMA.
Not sure about Antr and Jflex. Might only be build tools.
In generated/dist/sdk/lib are the jars that result from the build. They
are:
Compiler.jar
Falcon-asc.jar
Falcon-compc.jar
Falcon-mxmlc.jar
Falcon-optimizer.jar
Falcon-swfdump.jar
Flex-oem-compiler.jar
Pretty sure you want the first 5, although really, I think falcon-asc, falcon-compc, falcon-mxmlc use call compiler.jar. Not sure how the optimizer works. The 5 jars can be moved into a lib folder with the compiler/lib jars so they are all in one place.
You don't need falcon-swfdump unless you want to dump SWFs, and flex-oem-compiler.jar is only for FB integration.
AFAIK, these jars do not have dependencies on the current Flex SDK. When we build up an overlaid SDK we move the current SDK compiler to a bin-legacy and lib-legacy folder, but that's just so folks can revert back if Falcon isn't working. Also, the old SWFDump is much better, IMO.
HTH
-Alex
On 7/13/14 7:42 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Hi,
>
>After my latest Mavenizer and Flexmojos changes seem to compile all of
>my Flex projects without problems, I wanted to get started on adding
>Falcon support.
>Now instead of re-deploying the entire compiler, I would much more like
>to have the falcon-compiler depend on the normal compiler by
>referencing the falcon libs and adding a dependency on the normal
>compiler artifact and exclude the old compiler libs.
>
>Could someone here on the list please describe me exactly which libs
>Falcon consists of and where I can get them from as well as which libs
>in the classic sdk are needed? I think being able to switch the
>compilers by changing a dependency in maven would make experimenting a lot easier.
>
>Chris
AW: Mavenizing Falcon
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Alex,
thanks for that update ... I think I'll try with Mavenizing the "generated/sdk" directory and experiment a little with that.
As Flashbuilder is able to, hopefully Flexmojos will also be able to work with falcon without any modification (I will have to update the checkers in Flexmojos though to allow a "compiler-falcon" artifact instead of insisting on "compiler", but that should take at most 5 minutes :-)
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Sonntag, 13. Juli 2014 17:54
An: dev@flex.apache.org
Betreff: Re: Mavenizing Falcon
Gordon or Darrell might know the real answer.
If you build the Falcon repo or unpack a binary package, you should see a compiler/lib folder. In it are the external dependencies require by the build. Antlr, Commons-io, Commons-cli, guava, Jburg, Jflex, LZMA.
Pretty sure Jburg is need to build, but not to run. Pretty sure Commons-io and Commons-cli is need to run as well as LZMA.
Not sure about Antr and Jflex. Might only be build tools.
In generated/dist/sdk/lib are the jars that result from the build. They
are:
Compiler.jar
Falcon-asc.jar
Falcon-compc.jar
Falcon-mxmlc.jar
Falcon-optimizer.jar
Falcon-swfdump.jar
Flex-oem-compiler.jar
Pretty sure you want the first 5, although really, I think falcon-asc, falcon-compc, falcon-mxmlc use call compiler.jar. Not sure how the optimizer works. The 5 jars can be moved into a lib folder with the compiler/lib jars so they are all in one place.
You don't need falcon-swfdump unless you want to dump SWFs, and flex-oem-compiler.jar is only for FB integration.
AFAIK, these jars do not have dependencies on the current Flex SDK. When we build up an overlaid SDK we move the current SDK compiler to a bin-legacy and lib-legacy folder, but that's just so folks can revert back if Falcon isn't working. Also, the old SWFDump is much better, IMO.
HTH
-Alex
On 7/13/14 7:42 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Hi,
>
>After my latest Mavenizer and Flexmojos changes seem to compile all of
>my Flex projects without problems, I wanted to get started on adding
>Falcon support.
>Now instead of re-deploying the entire compiler, I would much more like
>to have the falcon-compiler depend on the normal compiler by
>referencing the falcon libs and adding a dependency on the normal
>compiler artifact and exclude the old compiler libs.
>
>Could someone here on the list please describe me exactly which libs
>Falcon consists of and where I can get them from as well as which libs
>in the classic sdk are needed? I think being able to switch the
>compilers by changing a dependency in maven would make experimenting a lot easier.
>
>Chris
Re: Mavenizing Falcon
Posted by Alex Harui <ah...@adobe.com>.
Gordon or Darrell might know the real answer.
If you build the Falcon repo or unpack a binary package, you should see a
compiler/lib folder. In it are the external dependencies require by the
build. Antlr, Commons-io, Commons-cli, guava, Jburg, Jflex, LZMA.
Pretty sure Jburg is need to build, but not to run. Pretty sure
Commons-io and Commons-cli is need to run as well as LZMA.
Not sure about Antr and Jflex. Might only be build tools.
In generated/dist/sdk/lib are the jars that result from the build. They
are:
Compiler.jar
Falcon-asc.jar
Falcon-compc.jar
Falcon-mxmlc.jar
Falcon-optimizer.jar
Falcon-swfdump.jar
Flex-oem-compiler.jar
Pretty sure you want the first 5, although really, I think falcon-asc,
falcon-compc, falcon-mxmlc use call compiler.jar. Not sure how the
optimizer works. The 5 jars can be moved into a lib folder with the
compiler/lib jars so they are all in one place.
You don't need falcon-swfdump unless you want to dump SWFs, and
flex-oem-compiler.jar is only for FB integration.
AFAIK, these jars do not have dependencies on the current Flex SDK. When
we build up an overlaid SDK we move the current SDK compiler to a
bin-legacy and lib-legacy folder, but that's just so folks can revert back
if Falcon isn't working. Also, the old SWFDump is much better, IMO.
HTH
-Alex
On 7/13/14 7:42 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Hi,
>
>After my latest Mavenizer and Flexmojos changes seem to compile all of my
>Flex projects without problems, I wanted to get started on adding Falcon
>support.
>Now instead of re-deploying the entire compiler, I would much more like
>to have the falcon-compiler depend on the normal compiler by referencing
>the falcon libs and adding a dependency on the normal compiler artifact
>and exclude the old compiler libs.
>
>Could someone here on the list please describe me exactly which libs
>Falcon consists of and where I can get them from as well as which libs in
>the classic sdk are needed? I think being able to switch the compilers by
>changing a dependency in maven would make experimenting a lot easier.
>
>Chris