[4.14] # Apache Flex SDK 4.14 nightly build 58: Successful

flex-sdk_release-candidate - Build #58 - Successful Changes since last build: [jmclean] Updated year and made first part consistent with http://www.apache.org/dev/licensing-howto.html#simple [jmclean] removed unneeded lines for Xerces as per http://www.apache.org/dev/licensing-howto.html#bundle

Re: rc_flex-sdk_mustella - Build # 80 - Failure!

Hmmm, could these failures be exclusive to the v 16 player? EdB On Sunday, January 4, 2015, wrote: > rc_flex-sdk_mustella - Build # 80 - Failure: > > http://flex-mustella.cloudapp.net/job/rc_flex-sdk_mustella/80/ > > Changes for Build #80 > No changes > > > >

Re: rc_flex-sdk_mustella - Build # 80 - Failure!

I've changed the Jenkins script to always increment the version of FP used in the next run. That will allow us to see if a failure is only happening on one FP version... EdB On Sun, Jan 4, 2015 at 12:28 PM, Erik de Bruin wrote: > Hmmm, could these failures be exclusive to the v 16 player? > >

Re: [4.14] binary vs. source package legal docs

> Blocking issues: > - saxon9 if bundled NOTICE will needs to be modified. I look into that > depending on if we decide to bundle it or not. > - saxon9 if not not bundled in the binary release will need to be removed > from LICENSE Currently, Saxon is bundled, right? And you and Alex disagree on

TLF test output

Erik, I think this question is for you. Is there any way to see the output files from the TLF unit tests on the Jenkins server? They should be located here: [TLF]/bin/apps/automation_apps/bin I’d like to be able to check the output and stack trace of failed tests. Thanks, Harbs

Re: [4.14] binary vs. source package legal docs

HI, > Currently, Saxon is bundled, right? And you and Alex disagree on if it > can stay that way? Well we can go ether way but I would prefer it was bundled as it currently is. If it is bundled we need to modify NOTICE and I can make the changes to NOTICE to accommodate that > I will call a vo

Re: TLF test output

I don't see that path, neither on the build machine nor on my local machine :-( Is there maybe a cleanup after a run when you do 'ant all' that makes the 'bin' directory go away? EdB On Sun, Jan 4, 2015 at 1:03 PM, Harbs wrote: > Erik, I think this question is for you. > > Is there any way to

Re: [4.14] binary vs. source package legal docs

>> Currently, Saxon is bundled, right? And you and Alex disagree on if it >> can stay that way? > > Well we can go ether way but I would prefer it was bundled as it currently > is. If it is bundled we need to modify NOTICE and I can make the changes to > NOTICE to accommodate that That's what I

Re: [4.14] binary vs. source package legal docs

Hi, > If you and Alex keep on disagreeing I actually don't think there's any disagreement here. Justin

Re: [4.14] binary vs. source package legal docs

That is awesome! So, just change NOTICE and we're done with this? EdB On Sun, Jan 4, 2015 at 2:51 PM, Justin Mclean wrote: > Hi, > >> If you and Alex keep on disagreeing > > I actually don't think there's any disagreement here. > > Justin -- Ix Multimedia Software Jan Luykenstraat 27 352

[4.14] # Apache Flex SDK 4.14 nightly build 59: Successful

flex-sdk_release-candidate - Build #59 - Successful Changes since last build: [erik] Always write out last run versions For more information, check the console output at http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/59/.

Re: TLF test output

My bad: I see the output you're looking for on my local machine. On the build VM however, the 'bin' dir only contains the SWC and no sub dirs :-( EdB On Sun, Jan 4, 2015 at 1:26 PM, Erik de Bruin wrote: > I don't see that path, neither on the build machine nor on my local machine > :-( > > Is

Re: [FLEXJS] RemoveEventListener

In Closure, 'addEventListener' is deprecated. Use 'goog.events.listen' instead. The latter takes an 'opt_handler' as 5th argument, making the use of 'goog.bind' unnecessary. It also returns a 'key', which you can use with 'unlistenByKey'. If you don't want to do that, just use 'unlisten' with the s

Re: [4.14] binary vs. source package legal docs

From [1], I would interpret the following: For the purposes of being a dependency to an Apache product, which licenses are considered to be similar in terms to the Apache License 2.0?Works under the following licenses may be included within Apache products: * Apache License 2.0

Re: [4.14] binary vs. source package legal docs

I should have thought of this sooner, but I went and looked at COLT and it includes a GenericSorter! I’m short on time today to verify this is the same one as Saxon uses, but assuming it is, I’d say then Saxon should be ok. Also, I haven’t reviewed Justin’s changes to L & N in detail, but from th

Re: -keep-generated-actionscript error?

Just tested, creating an empty TabNavApp and enabling -keep-generated-actionscript causes the same error. On Sat, Jan 3, 2015 at 11:00 PM, Alex Harui wrote: > Can you reduce it down to just an empty TabNavApp and no ANEs and still > get the issue? > > -Alex > > On 1/3/15, 9:16 AM, "Héctor A" wr

Re: TLF test output

Interesting. I’m not sure how to follow up on the failures. Do you get any of the failures on your local machine? On Jan 4, 2015, at 3:58 PM, Erik de Bruin wrote: > My bad: I see the output you're looking for on my local machine. On > the build VM however, the 'bin' dir only contains the SWC a

Re: [4.14] binary vs. source package legal docs

HI, > I think some changes need to be made to the build script to pull out the W3C > licenses to where they are supposed to be. That's correct - I've not done that yet. Justin

Re: TLF test output

Hi Guys, This is really weird, reports should appear in this location /bin/apps/automation_apps/bin. I will try to place tests reports in other location. Will see how jenkins respond. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-d

Re: TLF test output

Maybe some other ant script than this in TLF folder are cleaning bin directory. Just a thought. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/TLF-test-output-tp44123p44138.html Sent from the Apache Fl

Re: TLF test output

I know why these reports are not appear on build VM. Once build of TLF is finished, automatically is launching build of flex-sdk. Flex SDK is launching build.xml file from this location frameworks\projects\textLayout\build.xml and there is a target: The console output is

Re: [Mobile] [Mustella] Need help with the Mustella tests

I am officially out of time. I will be on my computer sparingly over the next 3 weeks. Sorry for the inconvenience, but I tried my best to fix these tests. I just wish I had more time. I just want to point out that the DateSpinner and SpinnerList tests are quite trivial. The selected item colo

Re: [4.14] binary vs. source package legal docs

OK, I went through the changes. I didn’t see anything that looked wrong. A question or two for this: +This produce bundles SAX2 available under a Public Domain license. +For more details see lib/external/LICENSE.sax.txt Why did you decide to call it SAX2 and not just SAX or SAX 2.0? And should

Re: [4.14] binary vs. source package legal docs

Hi, > Why did you decide to call it SAX2 and not just SAX or SAX 2.0? That's the product name eg http://shop.oreilly.com/product/9780596002374.do > And should we also be putting version numbers on all of the other > dependencies? We could, and it is useful, but AFAIK not required. > Also, I

Re: TLF test output

The second thing about that is - Maybe we shouldn't build SDK right after building of TLF ? It will resolve the problem without modifying code. Erik what do you thing about that ? Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-devel

Re: TLF test output

Why don’t we just output the test results to somewhere outside the bin directory? Maybe test_output or something? On Jan 5, 2015, at 8:32 AM, piotrz wrote: > The second thing about that is - Maybe we shouldn't build SDK right after > building of TLF ? > > It will resolve the problem without m

[4.14] # Apache Flex SDK 4.14 nightly build 60: Successful

flex-sdk_release-candidate - Build #60 - Successful Changes since last build: [Alex Harui] fix typos For more information, check the console output at http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/60/.

Re: TLF test output

Now I know where they end up, I'll 'archive' them using Jenkins, and have Jenkins 'analyze' them as well. That way we get a report AND keep the files (of the last run) in a readily available URL. EdB On Mon, Jan 5, 2015 at 7:43 AM, Harbs wrote: > Why don’t we just output the test results to so