flex-sdk_release-candidate - Build #132 - Successful
Changes since last build:
[Alex Harui] update a few more version vars so mustella test passes
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/132/.
Just as a reminder the mail threads in which I suggest such a refactoring:
http://apache-flex-development.247.n4.nabble.com/BlazeDS-Continuing-work-on-blazeds-td45427.html
http://apache-flex-development.247.n4.nabble.com/BlazeDS-not-compiling-for-clean-copy-of-SDK-source-td43391.html
http:
I'd say FLEX-34879, FLEX-34927, FLEX-34941, FLEX-34945 and FLEX-34852
are features rather than bugs. I'm happy to move them up if it's
agreed. Also, FLEX-34883 and FLEX-34884 are sub-tasks of FLEX-34852 -
do we always include sub-tasks? If so, there are a couple more to add,
and if not, I can remov
Yay! Thank you.
On 10 December 2015 at 17:52, Alex Harui wrote:
>
>
> On 12/10/15, 1:00 AM, "Mihai Chira" wrote:
>
>>Finding "FAIL: .*Sort" in the old reports highlights about 21 lines,
>>and in the new ones none. So I guess the sorting bugs have been fixed?
>>Or should we wait until we restart
The two test classes still failing are ones I wrote. They're failing
because UIImpersonator doesn't work correctly, which is a big hint
that in Jenkins we're using a version of FlexUnit that was compiled
for pure AS development, instead of for Flex development. In March
Chris offered to release Fle
It appears that flex-sdk_test uses the flex-flexunit build on the CI
server. Does that mean the flex-flexunit build is not configured to
produce the right artifacts for Flex customers. If so, that should
probably get fixed.
-Alex
On 12/16/15, 7:56 AM, "mihai.ch...@gmail.com on behalf of Mihai C
On 12/16/15, 4:17 AM, "Christofer Dutz" wrote:
>Just as a reminder the mail threads in which I suggest such a refactoring:
>
>http://apache-flex-development.247.n4.nabble.com/BlazeDS-Continuing-wo
>rk-on-blazeds-td45427.html
>http://apache-flex-development.247.n4.nabble.com/BlazeDS-not-
On Dec 16, 2015 10:03 AM, "Alex Harui" wrote:
>
>
>
> On 12/16/15, 4:17 AM, "Christofer Dutz" wrote:
>
> >Just as a reminder the mail threads in which I suggest such a
refactoring:
> >
> >
http://apache-flex-development.247.n4.nabble.com/BlazeDS-Continuing-wo
> >rk-on-blazeds-td45427.html
> >
Yes I am planning on removing everything outside the modules and then moving
the content of the modules directory up one level, making the pom.xml reside in
the root of the project.
The maven stuff is finished already ... Maven doesn't care if the pom.xml is
located inside a sub-directory ... I
On 12/16/15, 11:57 AM, "Christofer Dutz" wrote:
>Yes I am planning on removing everything outside the modules and then
>moving the content of the modules directory up one level, making the
>pom.xml reside in the root of the project.
>
>The maven stuff is finished already ... Maven doesn't care
flex-sdk_release-candidate - Build #133 - Successful
Changes since last build:
No changes
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/133/.
http://matrix3d.github.io/assets/html5/flexjsstage3d/bin/js-release/#test_puyodot
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/a-new-spriteflexjs-test-tp50666.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
12 matches
Mail list logo