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 tag.
If you use instead of it should work.
> The second is the use of the redirect extension.
This is where I thoug
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
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 v
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 p
Btw, made the build.xml bomb out for the moment if it's not built under
1.4.
Hen
On Tue, 22 Feb 2005, Henri Yandell 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 :)
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 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 hav
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 (t
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, xsl
