I do agree, having the possibility to specify a precise target as a dep
while testing an upgrade is by far a better solution then having a moving
target
I think it has already been notified to builds@ ...
Il giorno 08/gen/2013 00:19, "Howard Lewis Ship" ha
scritto:
> Probably ran out of memory or disk space; huge backlog of jobs, dead
> servers. Who do we notify?
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tap
On Mon, Jan 7, 2013 at 1:49 AM, Ulrich Stärk wrote:
> On 07.01.2013 00:29, Howard Lewis Ship wrote:
> > Snapshots have their place, but the stability of a preview release has
> its
> > value, despite the hoops Nexus makes you jump through. It says that this
> > particular binary represents a cons
This is not a trivial undertaking, and it is not an issue for the majority
of Tapestry applications.
I've found that apps that have this issue have gone down the Ubercomponent
route.
That being said, I'd like to fix it, but the amount of time it would take
to even track down how to speed things u
There are also a couple of performance tips at the very bottom of
http://tapestry.apache.org/class-reloading.html
On Mon, Jan 7, 2013 at 10:33 AM, Thiago H de Paula Figueiredo
wrote:
> On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
> wrote:
>
>> Hi,
>
>
> Hi!
>
>
>> we have a big project with
On Mon, 07 Jan 2013 12:29:37 -0200, Michael Wyraz
wrote:
Hi,
Hi!
we have a big project with Tapestry 5.3. There are many pages, lots of
components and many links between the pages (@Injects of other pages).
The problem is that after a change, the first page reload takes >5
seconds on g
Hi,
we have a big project with Tapestry 5.3. There are many pages, lots of
components and many links between the pages (@Injects of other pages).
The problem is that after a change, the first page reload takes >5
seconds on good hardware because there is much work for the tapestry
page compile
Here is my use case fwiw.
I was using a couple of block contributions that used components that
used AJAX, and they all stopped working after introducing the
cloak/decloak feature.
The main one was a really handy component for automatically rendering
a composition relationship between two entities
On 07.01.2013 00:29, Howard Lewis Ship wrote:
> We had a big discussion some time agao about the way to do things, and we
> even captured the results of the dicussion in Confluence:
>
> http://tapestry.apache.org/version-numbers.html
>
> So for once, I feel like I'm on the right side of a "follow
