AW: [LAST CALL] FlexUnit 4.3

2015-04-01 Thread Christofer Dutz
Hi Alex,

I didn't explicitly set one up, but I could do that. All I did was to add the 
Maven artifact generation, signing and deployment stuff to the build. If it's 
ok with you I could change the current version from 4.3.0 to 4.3.0-SNAPSHOT and 
have an automatic build job that also deploys the Maven artifacts to the 
snapshot repo.

Chris



Von: Alex Harui 
Gesendet: Mittwoch, 1. April 2015 06:33
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] FlexUnit 4.3

Hi Chris,

Is there a nightly build we can examine?  Or maybe put something out on
staging but don’t call a vote.  The idea is that we’re supposed to iron
out the issues before cutting an official RC.

Also, how do we use/test the code?

Thanks,
-Alex

On 3/30/15, 6:08 AM, "Mihai Chira"  wrote:

>Hi Chris,
>
>
>I'm very much looking forward to this. Then we'll be able to get our
>test runner to use this version[1], which should finally get
>FLEX_34625_Tests to pass.
>
>
>[1] http://s.apache.org/GKN
>
>
>On 30 March 2015 at 13:22, Christofer Dutz 
>wrote:
>> Hi,
>>
>>
>> I am preparing to start a new release of FlexUnit. Even if only a
>>hand-full of bugs were fixed, this time I am intending on also releasing
>>the Maven artifacts for FlexUnit so I think it's worth a 4.3 :-)
>>
>>
>> Eventually (depending on the german wether during the Easter public
>>holidays) I'm planning on staging the RC next Monday. So if you have
>>anything to go into the package ... get started right away :-)
>>
>>
>> Chris



Re: [TDF Mobile] Releasing TDF Mobile

2015-04-01 Thread Bertrand Delacretaz
Hi,

On Wed, Apr 1, 2015 at 6:40 AM, Alex Harui  wrote:
> ...IIRC, there is an experiment going on at the ASF about signing
> binaries

That's in production actually,
https://blogs.apache.org/infra/entry/code_signing_service_now_available

-Bertrand


Re: [1/2] git commit: [flex-tlf] [refs/heads/develop] - FLEX-34756 Split the functionality provided by FlowComposerBase.isDamaged() and StandardFlowComposer.isDamaged() into two separate functions, be

2015-04-01 Thread Mihai Chira
Cool, thanks for letting me know. I can only take a look at them mid-next
week, so if you need them taken care of earlier, I can revert the changes.
On 31 Mar 2015 08:16, "piotrz"  wrote:

> Mihai,
>
> Couple of other tests has failed in the next build and I think this is
> probably caused by your changes:
>
> http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/408/#showFailuresLink
>
> UnitTest.Tests::ImportAPITest.clipboardImporterTest
> UnitTest.Tests::ImportAPITest.clipboardExporterTest
> UnitTest.Tests::KeyboardGestureTest.TabPromoteDemoteListTest
>
> Piotr
>
>
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/Re-1-2-git-commit-flex-tlf-refs-heads-develop-FLEX-34756-Split-the-functionality-provided-by-FlowComL-tp45873p45882.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>


RE: [TDF Mobile] Releasing TDF Mobile

2015-04-01 Thread Kessler CTR Mark J
Well the problem is Adobe signed RSLs get put in the special cache outside of 
your browser so it stays even when you clear your cache.  If we sign it, the 
rsls will still be placed in the browser cache.  It still has a benefit, but is 
obviously more limited.

-Mark

-Original Message-
From: Erik de Bruin [mailto:e...@ixsoftware.nl]
Sent: Wednesday, April 01, 2015 2:08 AM
To: dev@flex.apache.org
Subject: Re: [TDF Mobile] Releasing TDF Mobile

>> Would this allow for RSLs to be signed?
>
> Yes but not much point as the Flash Player wouldn't recognise them as signed 
> and then cache them, it only recognised Adobe signed RSLs.

Ah, that was it. And I'm sure Adobe won't train the FP to recognise
the Apache signed RSLs (I assume this has been discussed, but I can't
recall)?

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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


RE: [TDF Mobile] Releasing TDF Mobile

2015-04-01 Thread Sugan Naicker
Hi,

I would be interested in testing on Android and IOS.

Tour de Flex Mobile -> It is good enough :-)

Thanks.

Sugan

-Original Message-
From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash 
Muppirala
Sent: Wednesday, April 1, 2015 1:47 AM
To: dev@flex.apache.org
Cc: us...@flex.apache.org
Subject: Re: [TDF Mobile] Releasing TDF Mobile

I am assuming there are no objections to my proposal.  If you are interested in 
testing the apps, please let me know.

Thanks,
Om

On Mon, Mar 30, 2015 at 12:19 PM, OmPrakash Muppirala 
wrote:

> Now that 4.14.1 is out of the way, I want to concentrate on releasing 
> the new Tour de Flex Mobile app on Google Play and Apple App stores.  
> I have rebuilt the iOS and Android apps with the new skins and they do 
> look pretty good, good enough to release.  I plan to be the release 
> manager for this release.
>
> Here are a few issues we need to consider:
>
> 1. The ASF does not currently have a way to let TLP projects to sign 
> app store binaries.  Instead of waiting on them, I plan to release it 
> under my own name, but with enough disclaimers to say that this is an 
> [un]official release of the Apache Flex project (only the binaries)  
> We will be releasing the source under the normal release process, of course.
> 2.  Does anyone want to suggest a better name than Tour de Flex Mobile?
> Or is this good enough?
>
> 3.  Testing the binaries will be an interesting problem.
>
> a.  For the Android platform, I can put up the .apk file on our Apache 
> dist folder and ask folks to download it from there.
> b.  As far as the iOS app goes, I am planning on creating a TestFlight 
> team and send an invite to users@ and dev@ so that folks can sign up 
> for testing those apps.
>
> Any suggestions or concerns, please feel free to raise them here.
>
> Thanks,
> Om
>



Re: [1/2] git commit: [flex-tlf] [refs/heads/develop] - FLEX-34756 Split the functionality provided by FlowComposerBase.isDamaged() and StandardFlowComposer.isDamaged() into two separate functions, be

2015-04-01 Thread piotrz
Actually I can take a look into that, but it is probably something in the TLF
side. I am not so much familiar with TLF in general.

If you wanted to setup your tests environment to debug these tests let me
know. I'm using Intellij and can provide some instruction.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Re-1-2-git-commit-flex-tlf-refs-heads-develop-FLEX-34756-Split-the-functionality-provided-by-FlowComL-tp45873p45901.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


AW: [LAST CALL] FlexUnit 4.3

2015-04-01 Thread Christofer Dutz
Ok so I staged the Maven output at 
https://repository.apache.org/content/repositories/orgapacheflex-1010/
So feel free to evaluate it. I have looked at how to configure the jenkins, but 
currently the build wouldn't support nightly SNAPSHOT versions. I guess this 
was the first project for which I created an Ant script for publishing Maven 
artifacts. I have done this for several other projects now and created a far 
more solid approach (Which I already added to other Flex Modules). I'll switch 
FlexUnit to using this script instead of the current one as soon as I find the 
time. Currently the job does it's job good enough though so I don't want do to 
this prior to releasing 4.3.

I would like to create a sub-directory in our flex-utils repo in which I would 
add a "maven.xml" ant script with documentation that we can use in several 
projects ... no need to re-invent the wheel for every Ant module.

Chris


Von: Christofer Dutz 
Gesendet: Mittwoch, 1. April 2015 09:18
An: dev@flex.apache.org
Betreff: AW: [LAST CALL] FlexUnit 4.3

Hi Alex,

I didn't explicitly set one up, but I could do that. All I did was to add the 
Maven artifact generation, signing and deployment stuff to the build. If it's 
ok with you I could change the current version from 4.3.0 to 4.3.0-SNAPSHOT and 
have an automatic build job that also deploys the Maven artifacts to the 
snapshot repo.

Chris



Von: Alex Harui 
Gesendet: Mittwoch, 1. April 2015 06:33
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] FlexUnit 4.3

Hi Chris,

Is there a nightly build we can examine?  Or maybe put something out on
staging but don’t call a vote.  The idea is that we’re supposed to iron
out the issues before cutting an official RC.

Also, how do we use/test the code?

Thanks,
-Alex

On 3/30/15, 6:08 AM, "Mihai Chira"  wrote:

>Hi Chris,
>
>
>I'm very much looking forward to this. Then we'll be able to get our
>test runner to use this version[1], which should finally get
>FLEX_34625_Tests to pass.
>
>
>[1] http://s.apache.org/GKN
>
>
>On 30 March 2015 at 13:22, Christofer Dutz 
>wrote:
>> Hi,
>>
>>
>> I am preparing to start a new release of FlexUnit. Even if only a
>>hand-full of bugs were fixed, this time I am intending on also releasing
>>the Maven artifacts for FlexUnit so I think it's worth a 4.3 :-)
>>
>>
>> Eventually (depending on the german wether during the Easter public
>>holidays) I'm planning on staging the RC next Monday. So if you have
>>anything to go into the package ... get started right away :-)
>>
>>
>> Chris


AW: [LAST CALL] FlexUnit 4.3

2015-04-01 Thread Christofer Dutz
And regarding examples ... the FlexUnit project does have a 
FlexUnit4SampleCIProject or FlexUnit4Turnkey as well as FlexUnit4Tutorials 
Projects which should answer all questions about how to use FlexUnit (the 
CIProject seems to have an Ant config as well as a Maven config that seem to 
both use Flexunit).

Chris


Von: Christofer Dutz 
Gesendet: Mittwoch, 1. April 2015 13:25
An: dev@flex.apache.org
Betreff: AW: [LAST CALL] FlexUnit 4.3

Ok so I staged the Maven output at 
https://repository.apache.org/content/repositories/orgapacheflex-1010/
So feel free to evaluate it. I have looked at how to configure the jenkins, but 
currently the build wouldn't support nightly SNAPSHOT versions. I guess this 
was the first project for which I created an Ant script for publishing Maven 
artifacts. I have done this for several other projects now and created a far 
more solid approach (Which I already added to other Flex Modules). I'll switch 
FlexUnit to using this script instead of the current one as soon as I find the 
time. Currently the job does it's job good enough though so I don't want do to 
this prior to releasing 4.3.

I would like to create a sub-directory in our flex-utils repo in which I would 
add a "maven.xml" ant script with documentation that we can use in several 
projects ... no need to re-invent the wheel for every Ant module.

Chris


Von: Christofer Dutz 
Gesendet: Mittwoch, 1. April 2015 09:18
An: dev@flex.apache.org
Betreff: AW: [LAST CALL] FlexUnit 4.3

Hi Alex,

I didn't explicitly set one up, but I could do that. All I did was to add the 
Maven artifact generation, signing and deployment stuff to the build. If it's 
ok with you I could change the current version from 4.3.0 to 4.3.0-SNAPSHOT and 
have an automatic build job that also deploys the Maven artifacts to the 
snapshot repo.

Chris



Von: Alex Harui 
Gesendet: Mittwoch, 1. April 2015 06:33
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] FlexUnit 4.3

Hi Chris,

Is there a nightly build we can examine?  Or maybe put something out on
staging but don’t call a vote.  The idea is that we’re supposed to iron
out the issues before cutting an official RC.

Also, how do we use/test the code?

Thanks,
-Alex

On 3/30/15, 6:08 AM, "Mihai Chira"  wrote:

>Hi Chris,
>
>
>I'm very much looking forward to this. Then we'll be able to get our
>test runner to use this version[1], which should finally get
>FLEX_34625_Tests to pass.
>
>
>[1] http://s.apache.org/GKN
>
>
>On 30 March 2015 at 13:22, Christofer Dutz 
>wrote:
>> Hi,
>>
>>
>> I am preparing to start a new release of FlexUnit. Even if only a
>>hand-full of bugs were fixed, this time I am intending on also releasing
>>the Maven artifacts for FlexUnit so I think it's worth a 4.3 :-)
>>
>>
>> Eventually (depending on the german wether during the Easter public
>>holidays) I'm planning on staging the RC next Monday. So if you have
>>anything to go into the package ... get started right away :-)
>>
>>
>> Chris

Re: [1/2] git commit: [flex-tlf] [refs/heads/develop] - FLEX-34756 Split the functionality provided by FlowComposerBase.isDamaged() and StandardFlowComposer.isDamaged() into two separate functions, be

2015-04-01 Thread Mihai Chira
I'm using IntelliJ as well, so that could be useful, yes.
But before you do, can I ask what motivated the use of a custom test
runner? What did the out-of-the-box FlexUnit lack?

On 1 April 2015 at 13:01, piotrz  wrote:
> Actually I can take a look into that, but it is probably something in the TLF
> side. I am not so much familiar with TLF in general.
>
> If you wanted to setup your tests environment to debug these tests let me
> know. I'm using Intellij and can provide some instruction.
>
> Piotr
>
>
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: 
> http://apache-flex-development.247.n4.nabble.com/Re-1-2-git-commit-flex-tlf-refs-heads-develop-FLEX-34756-Split-the-functionality-provided-by-FlowComL-tp45873p45901.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.


Re: [1/2] git commit: [flex-tlf] [refs/heads/develop] - FLEX-34756 Split the functionality provided by FlowComposerBase.isDamaged() and StandardFlowComposer.isDamaged() into two separate functions, be

2015-04-01 Thread piotrz
Mihai,

I don't understand what do you mean saying "custom test runner" and
"out-of-the-box FlexUnit lack" - Could you explain a bit for me ?

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Re-1-2-git-commit-flex-tlf-refs-heads-develop-FLEX-34756-Split-the-functionality-provided-by-FlowComL-tp45873p45905.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.


[Installer 3.2] # Apache Flex SDK Installer 3.2 nightly build 25: Failure

2015-04-01 Thread flex . ci . builds
flex-utilities_installer_release-candidate - Build #25 - Failure

Changes since last build:
No changes

For more information, check the console output at 
http://apacheflexbuild.cloudapp.net:8080/job/flex-utilities_installer_release-candidate/25/.

Re: [LAST CALL] FlexUnit 4.3

2015-04-01 Thread Justin Mclean
Hi,

> Ok so I staged the Maven output at 
> https://repository.apache.org/content/repositories/orgapacheflex-1010/

Is there a source package there? I couldn't find one to review.

Thanks,
Justin