Re: Apache Flex SDK 4.13.0 still awaiting approval

[Erik de Bruin]

>
> As you can see in the 'constructFlexForIDE' script, the only 'adl' copied
> is the Windows version:
>
> 156bin/adl.exe
>
> So, no problem on Windows. And with a known workaround for Mac. And
> really, from a user's perspective, this is an edge case anyway, as Alex
> explained, so let's please move on.
>

My bad. On Windows you'd run the '.bat' version, of course. And that has
the correct instruction on line 137.

So that makes the copying of 'adl.exe' and 'adt.bat' in the Unix version of
the script all the more confusing. My guess is that removing the extensions
from those names will fix the issue, but I have no cycles to test this
assumption. Also, looking at the Git history, the offending lines have been
around since the original commit by Carol Frampton
(0034f06ced0ec5a59b14120d5375fe90fdd0ed33) way back in 2012. So your issue
isn't even a regression, it's just a regular bug that apparently, until
now, has never bothered anyone.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Alex Harui]

On 7/15/14 10:51 PM, "Justin Mclean"  wrote:

>Hi,
>
>> Because you claim the source package should contain bin/adl.
>I'm am not or never had claimed that. All I said is if you follow the
>steps in the README you should get a usable SDK, currently you don't.
I see, you are claiming the compiled results should copy an
incompatibly-licensed file into the resulting folders.  AIUI, even
compiled results cannot do that for required features.   But really, you
did more than compile, you started running some of those IDE scripts.  The
compiled results can compile an AIR app.  ADL is not needed to compile.
>
>> A regression from what release of Apache Flex?
>From 4.12.0 or 4.12.1 I believe but are unable to check right this second.
My 4.9, 4.10, 4.11 and 4.12.0 compiled source packages do not contain
bin/adl.  Git says the head of constructFlexForIDE.sh was tagged for 4.10.
 I'm not going to spend time disproving that this is a regression.  You
will have to prove it.

Feel free to fix the scripts and if someone complains we can hand them the
fixed script and it will go in the next release.

It is now late for me, and I want to give time to Fred to see if he wants
to vote -1 and Nick to see if he wants to vote other than -1 before I
close the vote, so I will wait until my morning to count votes again.

-Alex

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Erik de Bruin]

>
> How exactly is this a false alarm? If you following the instructions in
> the README you end up with an SDK that is unable to compile AIR or mobile
> applications. In my books that makes it a regression issue.
>

If you were following the instructions in the README, as you claim, you
would never have run 'constructFlexForIDE', as it is not mentioned in that
document at all...

Are you in fact claiming that partial failure of an undocumented feature,
with a known workaround, constitutes a blocking issue?

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Erik de Bruin]

As you can see in the 'constructFlexForIDE' script, the only 'adl' copied
is the Windows version:

156bin/adl.exe

So, no problem on Windows. And with a known workaround for Mac. And really,
from a user's perspective, this is an edge case anyway, as Alex explained,
so let's please move on.

EdB




On Wed, Jul 16, 2014 at 8:05 AM, Justin Mclean 
wrote:

> Hi,
>
> > I love it how you completely ignore my proposed "solution". What do you
> say
> > about "addAIRtoSDK"?
>
> How would someone know it was a solution? And I've no idea what the
> situation is on windows.
>
> Justin




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Justin Mclean]

Hi,

> I love it how you completely ignore my proposed "solution". What do you say
> about "addAIRtoSDK"?

How would someone know it was a solution? And I've no idea what the situation 
is on windows.

Justin

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Erik de Bruin]

Alex,


> I say we ship as is.  Folks can argue about how to change the README when
> some user actually asks about this problem.
>

I agree completely.

My README remark was only meant to try to get Justin to maybe change his
vote - not that it's needed, but it sure would be nice.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [VOTE] Apache Flex SDK 4.13.0 RC3

[Erik de Bruin]

Not sure if you can - or should - cast a binding vote without completely
testing the release. Are you just casting the -1 vote because you agree
with Justin, or have you actually replicated the issue?

EdB



On Wed, Jul 16, 2014 at 5:04 AM, Nicholas Kwiatkowski 
wrote:

> I haven't been able to do a full test on the suite -- but ADL missing is a
> huge -1.
>
> We are worried about small regressions that fix bugs -- we can't let
> something like this pass.
>
> -1 Binding
>
> -Nick
>
>
> On Tue, Jul 15, 2014 at 5:49 PM, Frédéric THOMAS 
> wrote:
>
> > +1 (Binding)
> >
> > Package
> >
> https://dist.apache.org/repos/dist/dev/flex/sdk/4.13.0/rc3/apache-flex-sdk-4.13.0-src.zip
> > Java 1.7
> > OS: Windows 7 x86 6.1
> > Source kit signatures match: y
> > Source kit builds: y
> > README is ok: y
> > RELEASE_NOTES is ok: y
> > NOTICE is ok: y
> > LICENSE is ok: y
> > No unapproved licenses or archives: y
> > No unapproved binaries: y
> >
> >
> > main:
> >
> > BUILD SUCCESSFUL
> > Total time: 47 minutes 38 seconds
> >
> > I've been able to compile, run and debug (using FDB)
> > https://github.com/doublefx/easyWorker/  Flex/AIR/PureAS3 project and
> > sub-modules using Apache Flex 4.13.0 FP 14 AIR 14 en_US downloaded with
> the
> > Installer 3.1 and applied to my modules SDKs from IntelliJ, I haven't
> tried
> > to use the scripts to make the built SDK working within IDEs though
> >
> > Frédéric THOMAS
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Alex Harui]

On 7/15/14 10:41 PM, "Erik de Bruin"  wrote:

>A simple addition of the need to run 'addAIRtoSDK' to the README is enough
>to 'fix' this. No need for a new RC, no need for further delay.
But that's only if you try to use the source package in an IDE.  I built
the source package, and was able to run bin/amxmlc to compile an AIR app
without running any other scripts.  And was able to use the adl in the AIR
SDK pointed to by the AIR_HOME environment variable to run the app.

So, IMO, this failure case is not for all users of the source-package (if
there are any), but for those trying to transform the results into an
IDE-compatible SDK, for which there is no mention of that in the README's
section on the source distribution.

I say we ship as is.  Folks can argue about how to change the README when
some user actually asks about this problem.

-Alex

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Erik de Bruin]

Justin,

I love it how you completely ignore my proposed "solution". What do you say
about "addAIRtoSDK"?

EdB




On Wed, Jul 16, 2014 at 7:51 AM, Justin Mclean 
wrote:

> Hi,
>
> > Because you claim the source package should contain bin/adl.
> I'm am not or never had claimed that. All I said is if you follow the
> steps in the README you should get a usable SDK, currently you don't.
>
> > A regression from what release of Apache Flex?
> From 4.12.0 or 4.12.1 I believe but are unable to check right this second.
>
> Justin




-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Justin Mclean]

Hi,

> Because you claim the source package should contain bin/adl.  
I'm am not or never had claimed that. All I said is if you follow the steps in 
the README you should get a usable SDK, currently you don't.

> A regression from what release of Apache Flex? 
From 4.12.0 or 4.12.1 I believe but are unable to check right this second.

Justin

Re: [VOTE] Apache Flex SDK 4.13.0 RC3

[Alex Harui]

+1 (binding)
Package 
https://dist.apache.org/repos/dist/dev/flex/sdk/4.13.0/rc3/apache-flex-sdk-
4.13.0-src.tar.gz
Java 1.7
OS: Mac OS X x86_64 10.8.5
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y




On 7/2/14 1:06 AM, "Alex Harui"  wrote:

>Hi,
>
>This is a  Apache Flex 4.13.0 release candidate 3. Please see the
>RELEASE_NOTES and the README.
>
>There is a known bug in Adobe Flash Builder 4.6 and 4.7 that causes a
>issue when creating new applications.
>Adobe has provided a work around for FB 4.7 but not for 4.6.
>
>The release candidate can be found here;
>https://dist.apache.org/repos/dist/dev/flex/sdk/4.13.0/rc3/
>
>The binary distributions as a convenience for the respective platforms,
>available here:
>https://dist.apache.org/repos/dist/dev/flex/sdk/4.13.0/rc3/binaries
>
>
>The most convenient way to use the binary package is to install it via Ant
>or the Installer. To use an Installer you must use InstallApacheFlex
>version 3.1 or later which is still in release candidate status at this
>time. You can get InstallApacheFlex 3.1 here:
>https://dist.apache.org/repos/dist/dev/flex/installer/3.1/rc5/binaries/
>
>
>Before voting please review the section,"What are the ASF requirements on
>approving a release?", at:
>http://www.apache.org/dev/release.html#approving-a-release
>
>At a minimum you would be expected to check that:
>- MD5 and signed packages are correct
>- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
>- That you can compile from source package
>- That the SDK can be used in your IDE of choice
>- That the SDK can be used to make a mobile, desktop and browser
>application
>
>When testing please check the md5 and asc files and make sure that the
>source can be compiled.
>
>Please vote to approve this release:
>+1 Approve the release
>-1 Veto the release (please provide specific comments to why)
>
>This vote will be open for 72 hours or until a result can be called.
>
>The vote passes if there is:
>- At least 3 +1 votes from the PMC
>- More positive votes than negative votes
>
>If you find an issue with the release that's a "show stopper" please don't
>hold off voting -1. If someone votes -1 please continue testing we want to
>try and catch as many issues as we can and cut down on the number of
>release candidates. Remember existing voters can change their vote during
>the voting process.
>
>People who are not in PMC are also encouraged to test out the release and
>vote, although their votes will not be binding, they can influence how the
>PMC votes.
>
>When voting please indicate what OS, IDE, Flash Player version and AIR
>version you tested the SDK with.
>
>Please put all discussion about this release in the DISCUSSION thread not
>this VOTE thread.
>
>For your convenience, I have added an Ant script to the RC folder. This
>ant
>script automates the checks a voter should perform on the RC.
>It will:
>  - download the default source package for your OS (use -Dpackage.suffix
>to override)
>  - run md5 and gpg checks (this assumes you have gpg installed in your
>path)
>  - uncompress the source package
>  - install and run rat
>  - display the rat report and ask you to verify
>  - display the rat report without the AL files and ask you to verify the
>non-AL files
>  - display the README and ask you to verify
>  - display the RELEASE_NOTES and ask you to verify
>  - display the NOTICE and ask you to verify
>
>  - display the LICENSE and ask you to verify
>  - run the build and any tests run by the build.
>
>
>You should be able to go away for a while during the build.  When it is
>finished, it will display information to be copied into the vote thread.
>You are not required to use this script, and more testing of the packages
>and build results are always encouraged.
>
>To use this script (assuming you have Ant installed), it should be as
>simple as:
>- Create an empty folder
>- Download ApproveSDK.xml into that folder from:
>  
>https://dist.apache.org/repos/dist/dev/flex/sdk/4.13.0/rc3/ApproveSDK.xml
>- Run: ant -e -f ApproveSDK.xml -Drelease.version=4.13.0 -Drc=3
>
>
>Thanks,
>Alex
>
>
>
>
>
>
>
>
>

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Erik de Bruin]

A simple addition of the need to run 'addAIRtoSDK' to the README is enough
to 'fix' this. No need for a new RC, no need for further delay.

EdB



On Wednesday, July 16, 2014, Alex Harui  wrote:

>
> On 7/15/14 10:08 PM, "Justin Mclean"  > wrote:
>
> >Hi,
> >
> >> Furthermore, adl is part of the AIR sdk and is not owned by Apache Flex,
> >> and not under Apache Flex source control.  It should not be in the
> >>source
> >> package nor should it end up in the bin folder after building.
> >
> >Correct (and adl is not in the source package) but it is required for a
> >working SDK. Just because something compiles doesn't mean we should
> >release it - it needs to work as well. :-)
> >
> >> I appreciate your desire to look for problems, but please be careful
> >> before pulling the fire alarm.  There's been a lot of false alarms.
> >
> >How exactly is this a false alarm?
> Because you claim the source package should contain bin/adl.  I"m not
> seeing any way we can bundle that in the source package as ADL is under
> Adobe licensing.
>
> > If you following the instructions in the README you end up with an SDK
> >that is unable to compile AIR or mobile applications. In my books that
> >makes it a regression issue.
> A regression from what release of Apache Flex?  Or are you trying to
> compare the source package against Adobe Flex 4.6?
>
> >
> >
> >Not even sure why this is being discussed further, it been confined by
> >several people this is an issue with the RC, either you think it is
> >something we should fix before releasing and thus should vote -1 on the
> >release or you think we should fix later and release the RC now and vote
> >+1.
> What change would you propose to the RC that would conform to source
> package requirements about dependency licenses?
>
> -Alex
>
>

-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Alex Harui]

On 7/15/14 10:08 PM, "Justin Mclean"  wrote:

>Hi,
>
>> Furthermore, adl is part of the AIR sdk and is not owned by Apache Flex,
>> and not under Apache Flex source control.  It should not be in the
>>source
>> package nor should it end up in the bin folder after building.
>
>Correct (and adl is not in the source package) but it is required for a
>working SDK. Just because something compiles doesn't mean we should
>release it - it needs to work as well. :-)
>
>> I appreciate your desire to look for problems, but please be careful
>> before pulling the fire alarm.  There's been a lot of false alarms.
>
>How exactly is this a false alarm?
Because you claim the source package should contain bin/adl.  I"m not
seeing any way we can bundle that in the source package as ADL is under
Adobe licensing.

> If you following the instructions in the README you end up with an SDK
>that is unable to compile AIR or mobile applications. In my books that
>makes it a regression issue.
A regression from what release of Apache Flex?  Or are you trying to
compare the source package against Adobe Flex 4.6?

> 
>
>Not even sure why this is being discussed further, it been confined by
>several people this is an issue with the RC, either you think it is
>something we should fix before releasing and thus should vote -1 on the
>release or you think we should fix later and release the RC now and vote
>+1.
What change would you propose to the RC that would conform to source
package requirements about dependency licenses?

-Alex

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Justin Mclean]

Hi,

> Furthermore, adl is part of the AIR sdk and is not owned by Apache Flex,
> and not under Apache Flex source control.  It should not be in the source
> package nor should it end up in the bin folder after building.

Correct (and adl is not in the source package) but it is required for a working 
SDK. Just because something compiles doesn't mean we should release it - it 
needs to work as well. :-)

> I appreciate your desire to look for problems, but please be careful
> before pulling the fire alarm.  There's been a lot of false alarms.

How exactly is this a false alarm? If you following the instructions in the 
README you end up with an SDK that is unable to compile AIR or mobile 
applications. In my books that makes it a regression issue. 

Not even sure why this is being discussed further, it been confined by several 
people this is an issue with the RC, either you think it is something we should 
fix before releasing and thus should vote -1 on the release or you think we 
should fix later and release the RC now and vote +1.

Thanks,
Justin

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Alex Harui]

Furthermore, adl is part of the AIR sdk and is not owned by Apache Flex,
and not under Apache Flex source control.  It should not be in the source
package nor should it end up in the bin folder after building.  That's
what these other scripts do: they copy incompatibly-licensed external
stuff into your source folders.

I appreciate your desire to look for problems, but please be careful
before pulling the fire alarm.  There's been a lot of false alarms.

-Alex

On 7/15/14 9:14 PM, "Erik de Bruin"  wrote:

>Justin,
>
>Adl is missing because the 'constructForIDE' script doesn't copy it for
>the
>Mac. Use the 'AddAIRToSDK' script in addition to it and all is well. See
>my
>previous vote email on the subject, where I change my vote to +1.
>
>EdB
>
>
>
>On Wednesday, July 16, 2014, Justin Mclean  wrote:
>
>> Hi,
>>
>> > Is it a stopper for this release as most if not all the people use the
>> installer ?
>>
>>
>> IMO yes - hence my vote - but other PMC members are free to vote how
>>they
>> like. Again if it get 3 +1 votes and more +1 than -1 that makes it a
>>valid
>> release. Remember you're voting on this source release not any other
>> release or the binary release.
>>
>> It's also a big assumption that most people use the installer, but we
>> don't actually know how people install it, but it's probably correct.
>>
>> Justin
>>
>
>
>-- 
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Erik de Bruin]

Justin,

Adl is missing because the 'constructForIDE' script doesn't copy it for the
Mac. Use the 'AddAIRToSDK' script in addition to it and all is well. See my
previous vote email on the subject, where I change my vote to +1.

EdB



On Wednesday, July 16, 2014, Justin Mclean  wrote:

> Hi,
>
> > Is it a stopper for this release as most if not all the people use the
> installer ?
>
>
> IMO yes - hence my vote - but other PMC members are free to vote how they
> like. Again if it get 3 +1 votes and more +1 than -1 that makes it a valid
> release. Remember you're voting on this source release not any other
> release or the binary release.
>
> It's also a big assumption that most people use the installer, but we
> don't actually know how people install it, but it's probably correct.
>
> Justin
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [VOTE] Apache Flex SDK 4.13.0 RC3

[Nicholas Kwiatkowski]

I haven't been able to do a full test on the suite -- but ADL missing is a
huge -1.

We are worried about small regressions that fix bugs -- we can't let
something like this pass.

-1 Binding

-Nick


On Tue, Jul 15, 2014 at 5:49 PM, Frédéric THOMAS 
wrote:

> +1 (Binding)
>
> Package
> https://dist.apache.org/repos/dist/dev/flex/sdk/4.13.0/rc3/apache-flex-sdk-4.13.0-src.zip
> Java 1.7
> OS: Windows 7 x86 6.1
> Source kit signatures match: y
> Source kit builds: y
> README is ok: y
> RELEASE_NOTES is ok: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives: y
> No unapproved binaries: y
>
>
> main:
>
> BUILD SUCCESSFUL
> Total time: 47 minutes 38 seconds
>
> I've been able to compile, run and debug (using FDB)
> https://github.com/doublefx/easyWorker/  Flex/AIR/PureAS3 project and
> sub-modules using Apache Flex 4.13.0 FP 14 AIR 14 en_US downloaded with the
> Installer 3.1 and applied to my modules SDKs from IntelliJ, I haven't tried
> to use the scripts to make the built SDK working within IDEs though
>
> Frédéric THOMAS

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Nicholas Kwiatkowski]

I haven't been able to do a full test on the suite -- but ADL missing is a
huge -1.

We are worried about small regressions that fix bugs -- we can't let
something like this pass.

-1 Binding

-Nick


On Tue, Jul 15, 2014 at 7:05 PM, Justin Mclean  wrote:

> Hi,
>
> > Is it a stopper for this release as most if not all the people use the
> installer ?
>
>
> IMO yes - hence my vote - but other PMC members are free to vote how they
> like. Again if it get 3 +1 votes and more +1 than -1 that makes it a valid
> release. Remember you're voting on this source release not any other
> release or the binary release.
>
> It's also a big assumption that most people use the installer, but we
> don't actually know how people install it, but it's probably correct.
>
> Justin
>

RE: Apache Flex SDK 4.13.0 still awaiting approval

[Frédéric THOMAS]

Ideally, if the fix doesn't delay to much the release, it would be nice to have 
it, otherwise, there's the workaround as mention Erik:
After running 'ant frameworks-rsls', ./'ide/constructFlexForIDE.sh' AND
'./ide/addAIRtoSDK.sh':
- SDK is recognised by Flash Builder
- Flash Player apps build and run correctly
- AIR apps build and run correctlyFrédéric THOMAS

> Subject: Re: Apache Flex SDK 4.13.0 still awaiting approval
> From: justinmcl...@me.com
> Date: Wed, 16 Jul 2014 09:05:34 +1000
> To: dev@flex.apache.org
> 
> Hi,
> 
> > Is it a stopper for this release as most if not all the people use the 
> > installer ?
> 
> 
> IMO yes - hence my vote - but other PMC members are free to vote how they 
> like. Again if it get 3 +1 votes and more +1 than -1 that makes it a valid 
> release. Remember you're voting on this source release not any other release 
> or the binary release.
> 
> It's also a big assumption that most people use the installer, but we don't 
> actually know how people install it, but it's probably correct.
> 
> Justin
  

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Justin Mclean]

Hi,

> Is it a stopper for this release as most if not all the people use the 
> installer ?


IMO yes - hence my vote - but other PMC members are free to vote how they like. 
Again if it get 3 +1 votes and more +1 than -1 that makes it a valid release. 
Remember you're voting on this source release not any other release or the 
binary release.

It's also a big assumption that most people use the installer, but we don't 
actually know how people install it, but it's probably correct.

Justin

RE: Apache Flex SDK 4.13.0 still awaiting approval

[Frédéric THOMAS]

I also confirm adl is missing.

Is it a stopper for this release as most if not all the people use the 
installer ?

Frédéric THOMAS

> Subject: Re: Apache Flex SDK 4.13.0 still awaiting approval
> From: jus...@classsoftware.com
> Date: Wed, 16 Jul 2014 08:08:30 +1000
> To: dev@flex.apache.org
> 
> Hi,
> 
> > My understanding (from the installer vote thread) was that you were having
> > trouble with AIR apps after installing 4.12 and it went away after
> > re-starting FB.  Is that not the case?
> 
> The 4.13.0 RC3 source package when compiled fails to compile any AIR or 
> mobile application as it is missing bin/adl. The error is in the vote thread 
> and the issue was confirmed by Erik. 
> 
> Please see [1] and [2] a release is the source distribution and votes need to 
> be on the source package.
> 
> Justin
> 
> 1. http://www.apache.org/dev/release.html#what
> 2. http://www.apache.org/dev/release.html#approving-a-release
  

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Justin Mclean]

Hi,

> My understanding (from the installer vote thread) was that you were having
> trouble with AIR apps after installing 4.12 and it went away after
> re-starting FB.  Is that not the case?

The 4.13.0 RC3 source package when compiled fails to compile any AIR or mobile 
application as it is missing bin/adl. The error is in the vote thread and the 
issue was confirmed by Erik. 

Please see [1] and [2] a release is the source distribution and votes need to 
be on the source package.

Justin

1. http://www.apache.org/dev/release.html#what
2. http://www.apache.org/dev/release.html#approving-a-release

RE: [VOTE] Apache Flex SDK 4.13.0 RC3

[Frédéric THOMAS]

+1 (Binding)

Package 
https://dist.apache.org/repos/dist/dev/flex/sdk/4.13.0/rc3/apache-flex-sdk-4.13.0-src.zip
Java 1.7
OS: Windows 7 x86 6.1
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y


main:

BUILD SUCCESSFUL
Total time: 47 minutes 38 seconds

I've been able to compile, run and debug (using FDB) 
https://github.com/doublefx/easyWorker/  Flex/AIR/PureAS3 project and 
sub-modules using Apache Flex 4.13.0 FP 14 AIR 14 en_US downloaded with the 
Installer 3.1 and applied to my modules SDKs from IntelliJ, I haven't tried to 
use the scripts to make the built SDK working within IDEs though

Frédéric THOMAS   

Re: [ANNOUNCE] Radiate IDE 0.0.1 is now an open source project

[OmPrakash Muppirala]

On Tue, Jul 15, 2014 at 9:32 AM, jude  wrote:

> I received a few emails stating that making it open source is not the same
> as donating it to Apache Flex which is what I wanted to do. I'm in the
> process of seeing what that takes and finding out even if Apache Flex
> community wants it to be part of the Apache Flex project at all. That would
> mean the community would be responsible updates, patches and releases for
> it. That's something to discuss. In the mean time I've released it under
> Apache 2.0 license (if this works for everyone bueler bueler?). Just to be
> clear you can branch it, make your own projects and derivations from it or
> work on the main branch.
>
> BTW, What my main focus has been is to be able to design something that
> then generates a web site or an application with a lot of hooks and tools
> to do our job (web, mobile and desktop). Why not use Photoshop or Ai to
> accomplish that? I could! That will work for some projects but I'm trying
> to support the full Flex framework. And there's projects I'd like to do
> that would require it's own environment. Also, code editing or text editing
> might better be handled in things like FDT, FB, or IntelliJ. Blah blah blah
> blah...
>

Jude,

Thanks for offering to donate Radiate to Apache Flex. It would be great to
have Radiate as part of Apache Flex.  I think the community would be
benefited from such a tool.

If no one has objections, I will start a [POLL] thread on this so that we
can get a real gauge on the community interest.

Thanks,
Om

Re: [ANNOUNCE] Radiate IDE 0.0.1 is now an open source project

[jude]

I received a few emails stating that making it open source is not the same
as donating it to Apache Flex which is what I wanted to do. I'm in the
process of seeing what that takes and finding out even if Apache Flex
community wants it to be part of the Apache Flex project at all. That would
mean the community would be responsible updates, patches and releases for
it. That's something to discuss. In the mean time I've released it under
Apache 2.0 license (if this works for everyone bueler bueler?). Just to be
clear you can branch it, make your own projects and derivations from it or
work on the main branch.

BTW, What my main focus has been is to be able to design something that
then generates a web site or an application with a lot of hooks and tools
to do our job (web, mobile and desktop). Why not use Photoshop or Ai to
accomplish that? I could! That will work for some projects but I'm trying
to support the full Flex framework. And there's projects I'd like to do
that would require it's own environment. Also, code editing or text editing
might better be handled in things like FDT, FB, or IntelliJ. Blah blah blah
blah...

Re: Unit testing the SDK

[Mihai Chira]

All right, good to know.

About the path - should I add a unit test called
HierarchicalCollectionViewCursorTest_FLEX_34119 in
sdk\frameworks\projects\advancedgrids\test\mx\collections, or is it
better in sdk\frameworks\tests\mx\collections?

Also, what is the whiteboard? The only things I could find about it
were this[1] and that "Committers are granted access to a whiteboard
where they can share thoughts and code for discussion through a
Whiteboard"[2].

[1] 
https://cwiki.apache.org/confluence/display/FLEX/Instructions+for+Github+based+Whiteboard
[2] https://cwiki.apache.org/confluence/display/FLEX/Decisions+so+far

On 15 July 2014 16:30, Michael A. Labriola  wrote:
>>I have about 80 or so FlexUnit collection tests that were in my white board 
>>to supplement the mustella ones, but they are not currently run automatically.
>
> I also have some in my whiteboard for VectorCollection and there are the 
> FlexUnit tests themselves in the FlexUnit repo.
>
> But no, there are no further unit tests against the SDK.
>
> Mike
>

RE: Unit testing the SDK

[Michael A. Labriola]

>I have about 80 or so FlexUnit collection tests that were in my white board to 
>supplement the mustella ones, but they are not currently run automatically.

I also have some in my whiteboard for VectorCollection and there are the 
FlexUnit tests themselves in the FlexUnit repo.

But no, there are no further unit tests against the SDK. 

Mike

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Alex Harui]

On 7/15/14 1:41 AM, "Justin Mclean"  wrote:

>Hi,
>
>> I think Justin's -1 is because you can't generate RSLs correctly from
>>the source kit.
>The RSL version number being wrong is an issue but not the major one, the
>major issue os that AIR or mobile apps can't be compiled. The error
>message you get in in the vote thread.
My understanding (from the installer vote thread) was that you were having
trouble with AIR apps after installing 4.12 and it went away after
re-starting FB.  Is that not the case?

If there is still a blocking 4.13.0 issue for you, please provide an
updated description of the problem.

-Alex

Re: [VOTE] Apache FlexJS 0.0.2 RC5

[Justin Mclean]

Hi,

> I'm running through all of the examples (using the RC code, not from the
> repo). They all compile cleanly, just need to actually run each (aside
> from the 4 I ran for the vote).
Thanks for that - still a mystery why they fail here, it's probably a setup 
issue /  (perhaps something missing form the readme?). It would be nice to know 
what other people experience in trying to get it to work is. We need more than 
the two people working on this voting on releases.

> I think having a README in each example that explains the intent of the
> example and what it can do and what it needs is a good idea.
I've added a JIRA for that, setting expectations for people trying this out is 
important. If they know up front what work and doesn't work that ay actually 
get them to contribute something.

> but I will make it a priority to have a file in each example going forward.
Much appreciated. 

Thanks,
Justin

Re: Unit testing the SDK

[Justin Mclean]

Hi,

> PS: searching for "[Test]" in all *.as files yields 0 results as well.

I have about 80 or so FlexUnit collection tests that were in my white board to 
supplement the mustella ones, but they are not currently run automatically.

Given that Flex Unit has been released under Apache I see no reason not to use 
it.

Justin

Re: Unit testing the SDK

[piotrz]

TLF unit tests were written in Flex Unit 1, so you will not find in develop
branch any test marked [Test], but in branch FlexUnit4TestsTLF you will find
couple of tests rewritten to Flex Unit 4.

I hope I will back to this soon.

Piotr



-
Apache Flex Committer
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Unit-testing-the-SDK-tp39141p39148.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Unit testing the SDK

[Mihai Chira]

PS: searching for "[Test]" in all *.as files yields 0 results as well.

On 15 July 2014 15:12, Mihai Chira  wrote:
> Thanks for that, good to know.
> But I just did a global search for "flexunit" in all *.as files in
> both the sdk and tlf. The only ones I could find are in
> tlf\automation_core\src\UnitTest\. Does this mean I am going to write
> and commit the first ever unit (i.e. non-mustella) tests for the SDK?
> That feels very unlikely, so I guess I'm not searching right.
>
> On 15 July 2014 14:00, Justin Mclean  wrote:
>> Hi,
>>
>>> Do I need to write mustella tests, or can I write FlexUnit ones?
>> IMO any tests are fine and mustella test can be tricky to write if you're 
>> new to it.
>>
>> Justin

Re: Unit testing the SDK

[Mihai Chira]

Thanks for that, good to know.
But I just did a global search for "flexunit" in all *.as files in
both the sdk and tlf. The only ones I could find are in
tlf\automation_core\src\UnitTest\. Does this mean I am going to write
and commit the first ever unit (i.e. non-mustella) tests for the SDK?
That feels very unlikely, so I guess I'm not searching right.

On 15 July 2014 14:00, Justin Mclean  wrote:
> Hi,
>
>> Do I need to write mustella tests, or can I write FlexUnit ones?
> IMO any tests are fine and mustella test can be tricky to write if you're new 
> to it.
>
> Justin

Re: [VOTE] Apache FlexJS 0.0.2 RC5

[Peter Ent]

I'm running through all of the examples (using the RC code, not from the
repo). They all compile cleanly, just need to actually run each (aside
from the 4 I ran for the vote). The AS version of DataGrid isn't working
right, but the JS version is (the multiple scrollbars are known and have
been there since the beginning). The DataGrid is more of a POC using a
ButtonBar for the header and separate lists for the columns. Scrolling
would need to be synchronized between the lists. What we are looking for
are ideas. Someone could write a self-contained DataGrid if they wanted
to, of course. 

I think having a README in each example that explains the intent of the
example and what it can do and what it needs is a good idea. I don't think
we should hold up this release for it, but I will make it a priority to
have a file in each example going forward.

Peter

On 7/14/14 6:31 PM, "Justin Mclean"  wrote:

>Hi,
>
>> Note: I tested 4 of the examples: DataBindingText, FlexJSTest_SVG,
>> ListsTests, and StatesTest
>
>And are you OK with the DataGrid test no longer working or the multiple
>scroll bars in ListTests (in the JS version)? I know it alpha software be
>this seems to be a step backwards from 0.0.1.
>
>Would also be helpful to see some documentation around the examples ie
>know which ones work and which ones don't and/or what is broken. This
>issue was raised when releasing 0.0.1. I've raised a JIRA this time
>https://issues.apache.org/jira/browse/FLEX-34416.
>
>Thanks,
>Justin

Re: Unit testing the SDK

[Justin Mclean]

Hi,

> Do I need to write mustella tests, or can I write FlexUnit ones?
IMO any tests are fine and mustella test can be tricky to write if you're new 
to it.

Justin

Re: Unit testing the SDK

[piotrz]

Hi Mihai,

You can check branch with TLF unit tests, maybe it will help you a bit.
http://bit.ly/1zEX3GY

Piotr



-
Apache Flex Committer
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Unit-testing-the-SDK-tp39141p39143.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

AW: Building Falcon with Maven

[Christofer Dutz]

Hi Jose,

having such a thing would have the major benefit hof being able to publish 
SNAPSHOTS of the compiler automatically.
I think this would be a major breakthrough for bleeding edge developers ... 
simply referencing org.apache.flex.compiler:falcon-compiler:pom:4.13.0-SNAPSHOT 
would allow you to use the latest nightly build version with no need to 
manually update anything :-)

I also saw that you seem to be struggling with Antlr ... it's a real beast and 
I could see that you too gave 4.x a try and reverted to 3.x ... I use that in 
all of my projects too :-)
But why are you mixing both antlr versions? Seems you are using Antlr2 for some 
and Antlr3 for other grammar files.

Probably I could help with the grammar files as well as with the setup, if you 
are having any trouble. Just tell me what the problem is and I'll try to help 
sort that out as fast as possible.

Chris




Von: Jose Barragan 
Gesendet: Dienstag, 15. Juli 2014 12:18
An: dev@flex.apache.org
Betreff: Re: Building Falcon with Maven

Hi Chris,

Good to chat to you again, finally.

I just continue the original initiative, started by Carlos Rovira in order to 
mavenized the falcon project from their build process.

Regarding the group id name you mentioned, I don't have any problem to adopt 
your proposal.
I'm open to get help from you and others like Frank Wienberg, whose self 
offered to participate it too, due to I'm pretty busy (with chaotic mind), at 
last times after my first son was born, this causes that my effort on this work 
will a really hard defiance, due I'm working on it at my little ocio time.

Well, after say this... I'll keep on working on it, taking in account your 
comments, and trying to maintain the efforts synchronized with all of you.

Thanks,
__
Jose Barragan
Senior Software Engineer

On 15 Jul 2014, at 09:09, Christofer Dutz  wrote:

> Hi (especially) Jose,
>
>
>
> I was just informed that you are working on making falcon buildable with 
> Maven. First of all that is great.
>
> But we should coordinate how the artifacts are called.
>
> I could see that your artifacts for the compiler are located in the groupId 
> "org.apache.flex". You would make things a lot easier if you used 
> "org.apache.flex.compiler" instead. Otherwise the structure would start 
> getting a little messy. This way all compiler related artifacts are generated 
> to "org.apache.flex.compiler", all framework related artifacts are generated 
> to "org.apache.flex.framework". This is also somewhat the structure all maven 
> forms of Flex have had and I strongly suggest to continue this. Secondly I 
> would suggest to either generate the artifacts to 
> "org.apache.flex.compiler.falcon" groupId or call the artifact 
> "falcon-compiler" because the normal FDKs allready have an artifact called 
> compiler.
>
>
>
> If you need any help with this work, I'd rather help here than implement a 
> Mavenizer for Falcon (Which I had allready started working on) ;-)
>
> For example I remember a plugin for downloading and locally deploying a 
> single jar file. This might be good for the jburg dependency.
>
>
>
> Chris

Unit testing the SDK

[Mihai Chira]

Is there a way to write and run unit tests (e.g. FlexUnit) to test the
SDK? I know we use Mustella, but from what I can tell, mustella tests
need a UI / swf to run, rather than just testing a class without the
need for a UI.

I ask because I'd like to write some unit tests for
HierarchicalCollectionViewCursor for this bug[1] I'm working on. Do I
need to write mustella tests, or can I write FlexUnit ones?

Thanks.
Mihai

[1] https://issues.apache.org/jira/browse/FLEX-34119

Re: Apache Flex committer invite

[Tom Chiverton]

On 15/07/14 13:02, Mihai Chira wrote:
> Is the profile still updatable via svn, then?
The Wiki looks right to me. It's SVN rather than GIT because that's what
the CMS uses.

Tom

Re: Apache Flex committer invite

[Mihai Chira]

Hi all,


is this[1] still valid? I can't see the folder "site" in our git repo.
Is the profile still updatable via svn, then?

[1] 
https://cwiki.apache.org/confluence/display/FLEX/Updating+your+profile+on+Team+page

On 14 July 2014 11:29, Mihai Chira  wrote:
> I've just edited that page to mention git instead of svn. If something's
> wrong or missing, please let me know and I'll change it, or, of course, feel
> free to edit the page yourself.
>
>
> On 10 July 2014 12:15, Mihai Chira  wrote:
>>
>> Shall we update this wiki page[1] about our source code (and
>> potentially others)?
>>
>> I'm happy to do it as part of making my first commit. If you have a
>> link to a discussion thread or other wiki page with more info about
>> the transition to git, please let me know.
>>
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/FLEX/Getting+Started#GettingStarted-source
>>
>> On 7 July 2014 00:39, Mark Kessler  wrote:
>> > I'll throw tortoisegit [1] in the pot as well for a nice GUI git that
>> > has a
>> > good integrated context menu set.
>> >
>> > [1] https://code.google.com/p/tortoisegit/
>> >
>> >
>> > -Mark
>
>

Re: Building Falcon with Maven

[Jose Barragan]

Hi Chris,

Good to chat to you again, finally.

I just continue the original initiative, started by Carlos Rovira in order to 
mavenized the falcon project from their build process.

Regarding the group id name you mentioned, I don't have any problem to adopt 
your proposal. 
I'm open to get help from you and others like Frank Wienberg, whose self 
offered to participate it too, due to I'm pretty busy (with chaotic mind), at 
last times after my first son was born, this causes that my effort on this work 
will a really hard defiance, due I'm working on it at my little ocio time.

Well, after say this... I'll keep on working on it, taking in account your 
comments, and trying to maintain the efforts synchronized with all of you.

Thanks,
__
Jose Barragan
Senior Software Engineer

On 15 Jul 2014, at 09:09, Christofer Dutz  wrote:

> Hi (especially) Jose,
> 
> 
> 
> I was just informed that you are working on making falcon buildable with 
> Maven. First of all that is great.
> 
> But we should coordinate how the artifacts are called.
> 
> I could see that your artifacts for the compiler are located in the groupId 
> "org.apache.flex". You would make things a lot easier if you used 
> "org.apache.flex.compiler" instead. Otherwise the structure would start 
> getting a little messy. This way all compiler related artifacts are generated 
> to "org.apache.flex.compiler", all framework related artifacts are generated 
> to "org.apache.flex.framework". This is also somewhat the structure all maven 
> forms of Flex have had and I strongly suggest to continue this. Secondly I 
> would suggest to either generate the artifacts to 
> "org.apache.flex.compiler.falcon" groupId or call the artifact 
> "falcon-compiler" because the normal FDKs allready have an artifact called 
> compiler.
> 
> 
> 
> If you need any help with this work, I'd rather help here than implement a 
> Mavenizer for Falcon (Which I had allready started working on) ;-)
> 
> For example I remember a plugin for downloading and locally deploying a 
> single jar file. This might be good for the jburg dependency.
> 
> 
> 
> Chris

Re:Re: Apache Flex SDK 4.13.0 still awaiting approval

[DarkStone]

Hi,

I can compile and run the AIR desktop & mobile apps by using Flex SDK 4.13.0 
RC2 with Flash Builder 4.7

I haven't tried RC3 yet, are there some major differences between RC2 & RC3?


DarkStone
2014-07-15


At 2014-07-15 04:41:01, "Justin Mclean"  wrote:
>Hi,
>
>> I think Justin's -1 is because you can't generate RSLs correctly from the 
>> source kit.
>The RSL version number being wrong is an issue but not the major one, the 
>major issue os that AIR or mobile apps can't be compiled. The error message 
>you get in in the vote thread.
>
>Justin
>

Re:Re: [Translation] Maybe some issue in english text

[DarkStone]

IMO, no need to change that, I've seen some other software writing the same 
sentence.
At 2014-07-15 01:19:42, "Alex Harui"  wrote:
>IMO, it can be either way, but thanks for pointing that out.  One could
>argue that there shouldn't be a question mark at the end.
>
>I think I've seen lots of legal acceptance statements that aren't asked in
>the form of a question.
>
>We'll see if some native english speaker feels strongly enough about it to
>change it.
>
>Thanks,
>-Alex
>
>On 7/14/14 1:06 PM, "piotrz"  wrote:
>
>>Hi Guys,
>>
>>I'm not a native english speaker and I am far from that:), but I have
>>found
>>in this file http://bit.ly/1qZ4QeO
>>some sentence witch looks a bit odd for me.
>>
>>This is osmf.prompt.text, at the end we have sentence
>>
>>"I have read the MPL1.1 license information above?"
>>
>>I think it should looks more like a question maybe something like this
>>
>>"Have you read the MPL1.1 license information above?"
>>
>>Piotr :)
>>
>>
>>
>>
>>
>>-
>>Apache Flex Committer
>>piotrzarzyck...@gmail.com
>>--
>>View this message in context:
>>http://apache-flex-development.247.n4.nabble.com/Translation-Maybe-som
>>e-issue-in-english-text-tp39114.html
>>Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

RE: Build failed in Jenkins: flex-sdk #218

[arronlee]

Hi,
As for me, I am testing the related  java barcode generator
   these days. Do you
have any ideas about it? Or any good suggestion? I am totally a green hand
on barcode generating field. Any suggestion will be appreciated. Thanks in
advance.


Best regards,
Arron



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/RE-Build-failed-in-Jenkins-flex-sdk-218-tp42p39133.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Apache Flex SDK 4.13.0 still awaiting approval

[Justin Mclean]

Hi,

> I think Justin's -1 is because you can't generate RSLs correctly from the 
> source kit.
The RSL version number being wrong is an issue but not the major one, the major 
issue os that AIR or mobile apps can't be compiled. The error message you get 
in in the vote thread.

Justin

Re: [VOTE] Apache FlexJS 0.0.2 RC5

[OmPrakash Muppirala]

On Jul 14, 2014 11:29 PM, "Alex Harui"  wrote:
>
> Hey Om, I agree with you.  But instead of arguing this with Justin, can
> you instead find the time to vote on this package?  FalconJX has enough
> votes.  SDK 4.13.0 doesn't unless Justin changes his vote.  FlexJS doesn't
> unless Justin changes his vote.

Will do :-)

>
> Justin is getting failures in FlexJS that Peter and I are not getting.  If
> you can successfully build the DataGridExample and otherwise approve the
> package, then I'll feel better shipping it knowing that at it is working
> for at least one other person other than Peter and me.
>
> Thanks,
> -Alex
>
> On 7/14/14 4:16 PM, "OmPrakash Muppirala"  wrote:
>
> >On Mon, Jul 14, 2014 at 4:00 PM, Justin Mclean 
> >wrote:
> >
> >> Hi,
> >>
> >> > It might be a regression, but is it really a release blocker?
> >> I don't think it's a release blocker but IMO we should be releasing
> >>better
> >> quality software especially if we want people to try and it and lend a
> >>hand
> >> to fix stuff.
> >
> >
> >It is a vicious cycle.  If we don't release often we risk losing the
> >community's interest.  We have been churning on these release candidates
> >for a quite a bit now.  We should resist the urge to fix every little
> >issue
> >we find.
> >
> >
> >> Knowing how to compile it correctly helps (the instructions are
> >>currently
> >> misleading re FP 11.1) and there's no list of what works or what
doesn't
> >> for the examples. We had the same discussion for the last release and
> >> nothing improved  since then.
> >
> >
> >Expecting one or two people to fix all this within a release is not
> >reasonable.  We need more people working on this.  Again, the key to
> >attracting more volunteers is to getting this SDK into their hands.
> >
> >Thanks,
> >Om
> >
> >
> >> As with all releases if it gets the required 3 +1's (and more +1s than
> >> -1s) it can be released.
> >>
> >> >  IMO, we should log a JIRA ticket and address it in the next release.
> >> Already done see https://issues.apache.org/jira/browse/FLEX-34416
> >>
> >> Thanks,
> >> Justin
>

Re: [VOTE] Apache FlexJS 0.0.2 RC5

[Erik de Bruin]

Hey, don't forget about votes [1] from mere committers such as myself!

:-)

EdB

1:
https://mail-archives.apache.org/mod_mbox/flex-dev/201407.mbox/%3CCAJs%2BwW3sASPzaQT9K3PuYT3etm5SrfObaEwzEC6aS-oqQTBqHg%40mail.gmail.com%3E



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Building Falcon with Maven

[Christofer Dutz]

Hi (especially) Jose,



I was just informed that you are working on making falcon buildable with Maven. 
First of all that is great.

But we should coordinate how the artifacts are called.

I could see that your artifacts for the compiler are located in the groupId 
"org.apache.flex". You would make things a lot easier if you used 
"org.apache.flex.compiler" instead. Otherwise the structure would start getting 
a little messy. This way all compiler related artifacts are generated to 
"org.apache.flex.compiler", all framework related artifacts are generated to 
"org.apache.flex.framework". This is also somewhat the structure all maven 
forms of Flex have had and I strongly suggest to continue this. Secondly I 
would suggest to either generate the artifacts to 
"org.apache.flex.compiler.falcon" groupId or call the artifact 
"falcon-compiler" because the normal FDKs allready have an artifact called 
compiler.



If you need any help with this work, I'd rather help here than implement a 
Mavenizer for Falcon (Which I had allready started working on) ;-)

For example I remember a plugin for downloading and locally deploying a single 
jar file. This might be good for the jburg dependency.



Chris

AW: Mavenizing Falcon

[Christofer Dutz]

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: omup...@gmail.com  im Auftrag von OmPrakash Muppirala 

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 
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 
> 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.d...@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:aha...@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"  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
>