Hello Adam, thank you for your response. I actually meant that this restrictive proxy I'm behind is... restrictive enough to not support certain kinds of HTTP requests, such as those made by SVN (using webdav). But you're right, I hadn't noticed the source is packed with the release. Thank you for pointing that out.
Now, for the main subject, I am indeed setting a style-sheet-name with a prefixing slash: /resources/css/skin-stp.css I placed the slash, because a while ago when running the application expanded, it worked fine, but when I packed it in a jar it wouldn't recognize the skin... Do you happen to know what might cause this behaviour? Thank you, Francisco On 8/10/07, Adam Winer <[EMAIL PROTECTED]> wrote: > > Francisco, > > I've looked at this assertion this morning, and I can't reproduce > a case where it fires on Tomcat 5.0. Can you tell what > string is failing this assertion? By any chance, are you > setting a style-sheet-name in trinidad-skins.xml that starts > with a slash? > > The source for Trinidad is available whether or not you're behind > a firewall; the SVN repository is at: > > http://svn.apache.org/repos/asf/myfaces/trinidad/ > > and each of our releases includes source, for example: > > > http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/myfaces/trinidad/trinidad-impl/1.0.1/trinidad-impl-1.0.1-sources.jar > > -- Adam > > > > On 8/10/07, Francisco Passos < [EMAIL PROTECTED]> wrote: > > Good morning. > > > > The problem reported in > > https://issues.apache.org/jira/browse/TRINIDAD-44 remains. > > I tried editing the issue to reopen it, but couldn't. > > > > This is a really annoying bug that prevents one from debugging Trinidad > > applications. > > > > Alternatively, I'd like to be able to at least comment the assertion... > but > > can't get it from maven, since I'm behind a restrictive proxy. Is there > a > > way to download the source from 1.0.1 with its dependencies and all > that's > > needed to compile? > > > > > > Thank you, > > Francisco Passos > > >
