Re: Problems under 1.5 Was: [site] New Jakarta download pages
On Tue, 22 Feb 2005, Henri Yandell [EMAIL PROTECTED] wrote: The current problems are largely due to a stupid assumption on my part that Xalan would be the JDK xslt handler forever. XSLTC is considered the next generation of Xalan, or so it seems. Looking at our Gump experience, whichever versions of Xerces and XSLTC are included with JDK 1.5, they must be quite different from the Apache CVS versions (Apache Xerces doesn't fully support DOM3 yet, xml-commons is still at JAXP 1.2 level, XSLTC from CVS HEAD doesn't even build under JDK 1.5 using any released version of Ant ...) Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems under 1.5 Was: [site] New Jakarta download pages
On Wed, 23 Feb 2005, Stefan Bodewig wrote: On Tue, 22 Feb 2005, Henri Yandell [EMAIL PROTECTED] wrote: On Tue, 22 Feb 2005, Stefan Bodewig wrote: While it was using XSLTC, which is the TraX processor shipping with JDK 1.5. We now switched to Xalan-J's CVS HEAD. I give up :) How would I force it to be dependent on a particular version of Xalan? Check the jar as well as an xml-apis jar from xml-commons (or from Xalan itself) into svn, write a build.sh/.bar combo that ensures those two jars end up in the bootclasspath and force all people to use the scripts instead of Ant directly. I can't think of any other way, sorry. I assume that the JDK stuff in the classpath is going to butcher even an attempt to use Xalan directly via the java tag. The script would be as simple as , | #!/bin/sh | | ANT_OPTS=-bootclasspath path-to-xml-apis.jar:path-to-xalan.jar ant $@ ` Hmm, you'll probably need to include a matching version of Xerces as well. Painful. Geir's laughing at me right now :) Maybe there is a way to do what you trying to do with XSLT in Ant, even if it may seem less easy. At the risk of overcommitting, what exactly requires Xalan-J ATM? Maybe I can come up with something that's going to work with Ant, even if I have to write a custom task (something I'm not really afraif of). 3 problems with Xalan-XSLTC. The first is easy, changing xhtml to xml. The second is the use of the redirect extension. In XSLTC it's putting the files into cwd and not into the directory of the target file. If I dig a bit into xsltc, it might have more available to its redirect tag, or I could add a move to Ant (if I could get it to work for foo*.xml instead of **/*.xml). The third is just that XSLTC orders the attributes differently from Xalan, so every site build is going to hit lots of pages (ie bad svn diffs) if we switch back and forth between JVMs. xsltc appears to sort the attributes of a html tag differently so if we have 1 person using 1.4 and 1 using 1.5, our diffs are going to be spammed by attributes rotating back and forth. That's a problem. Also XSLTC requires far more heap memory than Xalan-J 2.x. Hadn't noticed the memory being a problem, but wasn't really looking. The speed was impressive :) Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems under 1.5 Was: [site] New Jakarta download pages
On Wed, 23 Feb 2005, Henri Yandell [EMAIL PROTECTED] wrote: I assume that the JDK stuff in the classpath is going to butcher even an attempt to use Xalan directly via the java tag. If you use bootclasspath instead of classpath it should work. The second is the use of the redirect extension. This is where I thought we might use a different solution. Use an Ant task instead of redirect extensions. The third is just that XSLTC orders the attributes differently from Xalan, so every site build is going to hit lots of pages (ie bad svn diffs) if we switch back and forth between JVMs. Yes, I've seen you mention that and looked for a way to control the behaviour of either - haven't found anything yet. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems under 1.5 Was: [site] New Jakarta download pages
On Tue, 22 Feb 2005, Stefan Bodewig wrote: While it was using XSLTC, which is the TraX processor shipping with JDK 1.5. We now switched to Xalan-J's CVS HEAD. I give up :) How would I force it to be dependent on a particular version of Xalan? Along with the problems with .cgi files and xhtml, xsltc appears to sort the attributes of a html tag differently so if we have 1 person using 1.4 and 1 using 1.5, our diffs are going to be spammed by attributes rotating back and forth. Throw in possible worries that the http:// url was causing problems under 1.4 and it seems to not be worth the trouble. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems under 1.5 Was: [site] New Jakarta download pages
On Tue, 22 Feb 2005 14:09:48 -0500, Howard Lewis Ship [EMAIL PROTECTED] wrote: I think we should not be checking in derived files. One of the reasons for that is so that anyone on the infrastructure team can quickly replace the site if it is corrupted or vandalised somehow. They should not have to go through a build process before they can do that. -- Martin Cooper I think the process should be: 1) Build and test locally 2) SVN checkin 3) Log into jakarta 4) SVN checkout 5) Build to staging area; test stage 6) Build to production; test production The build.xml needs to have targets: build -- local build (to target/site) build-stage -- to /www/jakarta-stage.apache.org ? build-prod - to /www/jakarta.apache.org The build scripts can be smart about setting file permissions etc. On Tue, 22 Feb 2005 12:42:45 -0500 (EST), Henri Yandell [EMAIL PROTECTED] wrote: On Tue, 22 Feb 2005, Stefan Bodewig wrote: While it was using XSLTC, which is the TraX processor shipping with JDK 1.5. We now switched to Xalan-J's CVS HEAD. I give up :) How would I force it to be dependent on a particular version of Xalan? Along with the problems with .cgi files and xhtml, xsltc appears to sort the attributes of a html tag differently so if we have 1 person using 1.4 and 1 using 1.5, our diffs are going to be spammed by attributes rotating back and forth. Throw in possible worries that the http:// url was causing problems under 1.4 and it seems to not be worth the trouble. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems under 1.5 Was: [site] New Jakarta download pages
Short term, I just want to get this working asap. ie) add a fixed dependency on Xalan I think. Hopefully Stefan can help there. The current problems are largely due to a stupid assumption on my part that Xalan would be the JDK xslt handler forever. Longer term, I think we shouldn't be building on personal machines. I'm hugely suspicious of the 'build to' concept. For any Jakarta site or for the releasables themselves. We should do it all in a standard build server environment. With the staging idea, I'd imagine we'd build to staging, then migrate staging to prod; rather than rebuilding to prod. Hen On Tue, 22 Feb 2005, Howard Lewis Ship wrote: I think we should not be checking in derived files. I think the process should be: 1) Build and test locally 2) SVN checkin 3) Log into jakarta 4) SVN checkout 5) Build to staging area; test stage 6) Build to production; test production The build.xml needs to have targets: build -- local build (to target/site) build-stage -- to /www/jakarta-stage.apache.org ? build-prod - to /www/jakarta.apache.org The build scripts can be smart about setting file permissions etc. On Tue, 22 Feb 2005 12:42:45 -0500 (EST), Henri Yandell [EMAIL PROTECTED] wrote: On Tue, 22 Feb 2005, Stefan Bodewig wrote: While it was using XSLTC, which is the TraX processor shipping with JDK 1.5. We now switched to Xalan-J's CVS HEAD. I give up :) How would I force it to be dependent on a particular version of Xalan? Along with the problems with .cgi files and xhtml, xsltc appears to sort the attributes of a html tag differently so if we have 1 person using 1.4 and 1 using 1.5, our diffs are going to be spammed by attributes rotating back and forth. Throw in possible worries that the http:// url was causing problems under 1.4 and it seems to not be worth the trouble. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems under 1.5 Was: [site] New Jakarta download pages
On Tue, 22 Feb 2005, Henri Yandell [EMAIL PROTECTED] wrote: On Tue, 22 Feb 2005, Stefan Bodewig wrote: While it was using XSLTC, which is the TraX processor shipping with JDK 1.5. We now switched to Xalan-J's CVS HEAD. I give up :) How would I force it to be dependent on a particular version of Xalan? Check the jar as well as an xml-apis jar from xml-commons (or from Xalan itself) into svn, write a build.sh/.bar combo that ensures those two jars end up in the bootclasspath and force all people to use the scripts instead of Ant directly. I can't think of any other way, sorry. The script would be as simple as , | #!/bin/sh | | ANT_OPTS=-bootclasspath path-to-xml-apis.jar:path-to-xalan.jar ant $@ ` Hmm, you'll probably need to include a matching version of Xerces as well. Maybe there is a way to do what you trying to do with XSLT in Ant, even if it may seem less easy. At the risk of overcommitting, what exactly requires Xalan-J ATM? Maybe I can come up with something that's going to work with Ant, even if I have to write a custom task (something I'm not really afraif of). xsltc appears to sort the attributes of a html tag differently so if we have 1 person using 1.4 and 1 using 1.5, our diffs are going to be spammed by attributes rotating back and forth. That's a problem. Also XSLTC requires far more heap memory than Xalan-J 2.x. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
