Re: Problem with tapestry-yuicompressor in Tomcat

2012-03-07 Thread Jochen Frey
I can't speak to this authoritatively, but I know for a fact that it's a problem for us. J On Mar 7, 2012, at 11:13 PM, Yohan Yudanara wrote: > Hi.. > > I'm sorry to waking an old thread. > > This outstanding bug with title "Sometimes YUICompressor can fail with > java.util.EmptyStackExceptio

Re: Problem with tapestry-yuicompressor in Tomcat

2012-03-07 Thread Yohan Yudanara
Hi.. I'm sorry to waking an old thread. This outstanding bug with title "Sometimes YUICompressor can fail with java.util.EmptyStackException", which has blocker severity, has been filed in JIRA since 26 Oct 2011. This is the link: https://issues.apache.org/jira/browse/TAP5-1729 I don't understan

Re: Problem with tapestry-yuicompressor in Tomcat

2012-03-01 Thread Paul Stanton
I found a solution too: ;) On 2/03/2012 1:34 AM, antalk wrote: I had the same issue and found a solution: https://issues.apache.org/jira/browse/TAP5-1729?focusedCommentId=13220036&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13220036 -- View this message in

Re: Problem with tapestry-yuicompressor in Tomcat

2012-03-01 Thread antalk
I had the same issue and found a solution: https://issues.apache.org/jira/browse/TAP5-1729?focusedCommentId=13220036&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13220036 -- View this message in context: http://tapestry.1045711.n5.nabble.com/Problem-with-tapestry

Re: Problem with tapestry-yuicompressor in Tomcat

2011-10-27 Thread Denis Stepanov
Maybe the solution would be to use JarJar to repackage the Rhino, just like Google Guice uses it for including libs like ASM, commons etc. see: http://code.google.com/p/google-guice/source/browse/pom.xml#201 Denis On 27.10.2011, at 2:16, Howard Lewis Ship wrote: > The Liferay folks repackaged

Re: Problem with tapestry-yuicompressor in Tomcat

2011-10-26 Thread Howard Lewis Ship
The Liferay folks repackaged the Rhino and YUICompressor classes into new package names to avoid conflicts. I wish that they had a public Maven repo we could pull those from. On Wed, Oct 26, 2011 at 4:55 PM, Lenny Primak wrote: > I don't think this is a tapestry issue at all.  I think it's a gene

Re: Problem with tapestry-yuicompressor in Tomcat

2011-10-26 Thread Lenny Primak
I don't think this is a tapestry issue at all. I think it's a general YUIcompressor issue, and I don't know what can Tapestry do to fix this. On Oct 26, 2011, at 5:40 PM, Howard Lewis Ship wrote: > https://issues.apache.org/jira/browse/TAP5-1729 > > I don't have a good fix for this as of yet.

Re: Problem with tapestry-yuicompressor in Tomcat

2011-10-26 Thread Howard Lewis Ship
https://issues.apache.org/jira/browse/TAP5-1729 I don't have a good fix for this as of yet. On Sat, Oct 22, 2011 at 10:46 AM, Lenny Primak wrote: > I had the problem under Glassfish as well. > There is a conflict between Rhino JS and yuicompressor libraries. > I got around it by putting a combi

Re: Problem with tapestry-yuicompressor in Tomcat

2011-10-22 Thread Lenny Primak
I had the problem under Glassfish as well. There is a conflict between Rhino JS and yuicompressor libraries. I got around it by putting a combined Rhino-js and Yuicompressor library onto the CLASSPATH Here is a little maven / ant magic to generate the combind JAR (from http://code.google.com/p/fl

Re: Problem with tapestry-yuicompressor in Tomcat

2011-10-22 Thread Barry Books
Does not work for me in Tomcat either, but Jetty under Eclipse works fine. I get a 500 under Tomcat and this: [ERROR] ioc.Registry java.util.EmptyStackException [ERROR] ioc.Registry Operations trace: [ERROR] ioc.Registry [ 1] Streaming asset stack en/core.js [ERROR] ioc.Registry [ 2] Minimizing J

Re: Problem with tapestry-yuicompressor in Tomcat

2011-10-20 Thread Steve Eynon
I'm having the same problems in Jetty (and I don't really see how it could be related to the app server). My issue is that when it happens, a HTTP 500 is returned and NO JavaScript! (...equals client side errors...) If the exception was caught and the original javascript returned then regardless if