Still Failing: apache/tapestry-5#128 (master - 95413c0)

2016-07-14 Thread Travis CI
Build Update for apache/tapestry-5 - Build: #128 Status: Still Failing Duration: 14 minutes and 53 seconds Commit: 95413c0 (master) Author: Jochen Kemnade Message: TAP5-2548: upgrade embedded Tomcat and Jetty versions View the changeset: https://github.com/ap

Still Failing: apache/tapestry-5#129 (master - f161aa8)

2016-07-14 Thread Travis CI
Build Update for apache/tapestry-5 - Build: #129 Status: Still Failing Duration: 14 minutes and 45 seconds Commit: f161aa8 (master) Author: Barry Books Message: TAP-2327: add support for httpOnly cookies and setting cookies' version/comment View the changeset

Still Failing: apache/tapestry-5#130 (master - e048d95)

2016-07-14 Thread Travis CI
Build Update for apache/tapestry-5 - Build: #130 Status: Still Failing Duration: 18 minutes and 34 seconds Commit: e048d95 (master) Author: Jochen Kemnade Message: TAP5-2327: fix NullPointerException View the changeset: https://github.com/apache/tapestry-5/co

Still Failing: apache/tapestry-5#131 (master - c2a4b96)

2016-07-14 Thread Travis CI
Build Update for apache/tapestry-5 - Build: #131 Status: Still Failing Duration: 16 minutes and 6 seconds Commit: c2a4b96 (master) Author: Jochen Kemnade Message: TAP5-2449, TAP5-1493: add the interfaces to the queue in the correct order View the changeset:

Build failed in Jenkins: tapestry-trunk-freestyle #1584

2016-07-14 Thread Apache Jenkins Server
See Changes: [jkemnade] TAP5-2449, TAP5-1493: add the interfaces to the queue in the correct -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remote

Build failed in Jenkins: tapestry-trunk-freestyle #1585

2016-07-14 Thread Apache Jenkins Server
See Changes: [jkemnade] TAP5-2449: sort the class's own property descriptors last so that they -- Started by an SCM change [EnvInject] - Loading node environment variables. Building rem

Still Failing: apache/tapestry-5#132 (master - 3288d37)

2016-07-14 Thread Travis CI
Build Update for apache/tapestry-5 - Build: #132 Status: Still Failing Duration: 16 minutes and 4 seconds Commit: 3288d37 (master) Author: Jochen Kemnade Message: TAP5-2449: sort the class's own property descriptors last so that they ultimately control the pro

Still Failing: apache/tapestry-5#133 (master - 504f1ad)

2016-07-14 Thread Travis CI
Build Update for apache/tapestry-5 - Build: #133 Status: Still Failing Duration: 14 minutes and 24 seconds Commit: 504f1ad (master) Author: Jochen Kemnade Message: don't use String.format for logging View the changeset: https://github.com/apache/tapestry-5/co

Build failed in Jenkins: tapestry-trunk-freestyle #1586

2016-07-14 Thread Apache Jenkins Server
See Changes: [jkemnade] don't use String.format for logging [jkemnade] fix tests -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubunt

Still Failing: apache/tapestry-5#134 (master - 5d7dfb8)

2016-07-14 Thread Travis CI
Build Update for apache/tapestry-5 - Build: #134 Status: Still Failing Duration: 15 minutes and 7 seconds Commit: 5d7dfb8 (master) Author: Jochen Kemnade Message: fix tests View the changeset: https://github.com/apache/tapestry-5/compare/504f1ada79ec...5d7dfb

Re: 5.5 soon?

2016-07-14 Thread Thiago H de Paula Figueiredo
On Thu, 14 Jul 2016 02:30:14 -0300, Jochen Kemnade wrote: +1 to all of that. ;) On a side note, should we default to the jQuery infrastructure for 5.5? Hmm, current Prototype-based projects would just stop working out of a sudden. I'm not a fan of changing defaults. On the other hand,

Re: 5.5 soon?

2016-07-14 Thread Robert Zeigler
I’m in favor of a transition release where we warn with the big bright warnings that in the next release, we’ll be switching to the jQuery infrastructure by default. I would also suggest adding a means of determining whether people are using the out-of-the-box prototype configuration and adding

Re: 5.5 soon?

2016-07-14 Thread Andreas Ernst
Am 14.07.16 um 15:33 schrieb Robert Zeigler: I’m in favor of a transition release where we warn with the big bright warnings that in the next release, we’ll be switching to the jQuery infrastructure by default. I would also suggest adding a means of determining whether people are using the ou