[Tapestry Wiki] Update of "FrontPage" by UlrichStaerk

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification. The "FrontPage" page has been changed by UlrichStaerk. The comment on this change is: stupid spammer http://wiki.apache.org/tapestry/FrontPage?action=diff&rev1=266&rev2=267 --

Weird error

I'm experiencing weird error during the tapestry-core integration test. The page AssetDemo fails due to template parsing error. Looks like the expression ${context:images/asf_logo_wide.gif} cannot be parsed anymore. Any hints? [ERROR] RequestExceptionHandler Processing of request failed with uncau

[Tapestry Wiki] Update of "FrontPage" by trimedic37

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification. The "FrontPage" page has been changed by trimedic37. http://wiki.apache.org/tapestry/FrontPage?action=diff&rev1=265&rev2=266 --

Re: [REPORT] Tapestry -- April 2010 (Revised)

On Mon, 19 Apr 2010 17:16:09 -0300, Ulrich Stärk wrote: +1 +1 -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, software architect and developer, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachin

Re: [REPORT] Tapestry -- April 2010 (Revised)

+1 On 19.04.2010 20:46, Howard Lewis Ship wrote: Tapestry 5.2 continues to progress at a good rate, but is still alpha. Howard has been tackling some significant infrastructure issues inside Tapestry that will eventually break the dependence on the JBoss Javassist module. Discussion has continu

Re: [REPORT] Tapestry -- April 2010 (Revised)

Tapestry 5.2 continues to progress at a good rate, but is still alpha. Howard has been tackling some significant infrastructure issues inside Tapestry that will eventually break the dependence on the JBoss Javassist module. Discussion has continued about how to reorganize the documentation to bett

Build failed in Hudson: tapestry-5.2-freestyle #79

See Changes: [hlship] TAP5-728: When using the @Validate annotation, spaces around the commas that separate contraints cause runtime exceptions [hlship] TAP5-1068: RenderSupport.addScriptLink(String) deprecated and r

[REPORT] Tapestry -- April 2010

Tapestry 5.2 continues to progress at a good rate, but is still alpha. Howard has been tackling some significant infrastructure issues inside Tapestry that will eventually break the dependence on the JBoss Javassist module. Discussion has continued about how to reorganize the documentation to bett

Git assist?

I'm still getting this error everytime I commit: ~/work/t5-project $ git svn rebase Current branch trunk is up to date. ~/work/t5-project $ git svn dcommit Committing to https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk ... M src/site/apt/guide/event.apt M tape

Hudson build is back to normal : tapestry-5.2-freestyle #74

See - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org

Re: Re-working Javascript aggregation

I'm having a tough battle with Git/Svn just to get the changes checked into SVN! The changes are somewhat widespread. It would be a challenge to backport them. On Mon, Apr 19, 2010 at 6:26 AM, Massimo Lusetti wrote: > On Mon, Apr 19, 2010 at 3:19 AM, Howard Lewis Ship wrote: > >> I'm pretty ha

Re: Re-working Javascript aggregation

On Mon, Apr 19, 2010 at 3:19 AM, Howard Lewis Ship wrote: > I'm pretty happy with how it is all coming out. > > The eventual goal will be to allow for multiple stacks; this will > allow, for example, a large library like Ext or YUI to download as a > single unit. > > Should have this in SVN tomor

Re: Re-working Javascript aggregation

Great! On a related subject, I've begun to push a tapestry5-jquery module on Github. This library depends on tapestry5-clientresources, another new module, which is basically a ClientInfrastructure service override in order to make it contribuable. I used "AssetPathStack" objects to contribute to

Re: Re-working Javascript aggregation

Wow, great work. Does this also change the machinism for combining javascript files? Specifically limiting the url length when many files are combined (to wolve problems which can appear in IE)? Thanks for all your work on Tapestry. Kind regards, Joachim Howard Lewis Ship wrote: I've been