On Sunday November 13, 2005 Xalan moved from using CVS to Subversion as its
code and part version control system. Many thanks go to Henri Yandell who
did the conversion for us.
The old code at CVS repository cvs.apache.org for the "xml-xalan" project
is still there, but is now
[EMAIL PROTECTED] wrote:
I didn't realize we could actually build on Nagoya, so having something
could be really useful. The thing about that's troublesome is it wasn't
uncovered in Xerces-C's normal test process, so I'm not sure if even
automating the testing process would help. Still, it's some
cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Re: A Simple Stylesheet
failed on CVS-Xalan
01/19/2004 01:01
AM
David,
Apologies - this is *long* after your original e-mail.
I've been playing with a *very simple* system to do some autobuilding
out of CVS. Similar to gump, but much simpler. The reason for the
simpler being dependency checking is more difficult, and I want to
autobuild multiple OSe
ni/Cambridge/IBM)
Subject: A Simple Stylesheet
failed on CVS-Xalan
Hi there,
I have checked out the tagged version "Xalan-C_1_7_0" (it is not
official I know) from the apache CVS yesterday and build it against
Xerces-C 2.4. The simple stylesheet
http://www.w3.org/1999/XSL/Transform";>
fails, because a bug of Xerces-C 2.4 withi
Colin Paul Adams wrote:
What are the include files called now?
E.g. instead of -I$XALANCROOT/src, use -I$XALANCROOT/src/xalanc, or
prepend xalanc on all your include directives :
#include
Cheers,
Berin
> "david" == david n bertoni <[EMAIL PROTECTED]> writes:
david> Eveyrhing else in the build documentation should be OK.
david> You will need to update your own makefiles to use the new
david> directory name for include files.
What are the include files called now?
--
Colin Paul
> "Colin" == Colin Paul Adams <[EMAIL PROTECTED]> writes:
Colin> Preparing the directory structure for a build ... mkdir -p
Colin> /home/colin/xml-xalan/c/src/xalanc/obj mkdir -p
Colin> /home/colin/xml-xalan/c/src/xalanc/lib mkdir -p
Colin> /home/colin/xml-xalan/c/src/xalanc/
>>>>> "david" == david n bertoni <[EMAIL PROTECTED]> writes:
david> It looks like you got your code while I was in the middle
david> of checking in, which is one of the hazards with using the
david> latest CVS. Just do an update in your s
Hi Colin,
It looks like you got your code while I was in the middle of checking in,
which is one of the hazards with using the latest CVS. Just do an update
in your source tree and you should get working code. I've done Linux
builds with several versions of gcc and all looks well.
Just learnt something new :>.
Done.
Cheers,
Berin
[EMAIL PROTECTED] wrote:
Hi Berin,
Can you just do a chmod on those two repository files? That will save
multiple emails about this when people check out from CVS. The previous
versions of runConfigure and configure did have th
> "david" == david n bertoni <[EMAIL PROTECTED]> writes:
david> Hi Colin,
david> We just did a transition to a new directory stucture so we
david> can get our build/install situation cleared up, so there
david> are going to be a few glitches.
david> Yes, you should use th
Hi Berin,
Can you just do a chmod on those two repository files? That will save
multiple emails about this when people check out from CVS. The previous
versions of runConfigure and configure did have these privileges on
checkout.
I tried to do it, but I don't have the necessary permis
@xml.apache.org
|
|cc: (bcc: David N Bertoni/Cambridge/IBM)
|
| S
Colin,
We did a piece of work on the weekend to move the
source code into the xalanc directory, so that all
includes for Xalan-C will now be prefixed by the
package name. (Better for installation onto
UNIX systems.)
Files out of CVS are written as straight
text, so you need to set the
>>>>> "david" == david n bertoni <[EMAIL PROTECTED]> writes:
david> CVS information is here:
david>http://xml.apache.org/cvs.html
Right - next - how do I do a build (on linux)?
The documentation on the web-site for 1.5 clearly no longer applies
Hi Colin,
> >>>>> "david" == david n bertoni <[EMAIL PROTECTED]> writes:
>
>david> CVS information is here:
>
>david>http://xml.apache.org/cvs.html
>
> Thanks. A link from http://xml.apache.org/xalan-c would be nice - I
&
>>>>> "david" == david n bertoni <[EMAIL PROTECTED]> writes:
david> CVS information is here:
david>http://xml.apache.org/cvs.html
Thanks. A link from http://xml.apache.org/xalan-c would be nice - I
always forget.
Can I still use xeces-c 2.2.0
Hi Colin,
CVS information is here:
http://xml.apache.org/cvs.html
Note you can either use a CVS client to check out, or you can get CVS
tarballs:
http://cvs.apache.org/snapshots/
Dave
|-+--->
| | Colin Paul Ad
How do I check-out CVS?
The web-site does NOT mention it.
--
Colin Paul Adams
Preston Lancashire
[EMAIL PROTECTED] wrote:
> G'day Per,
>
> Xerces 2.3 has changed a few interfaces (I think
> due to changes to support XML 1.1).
>
> We have not yet done the updates within Xalan to
> support the new interface - have been
> concentrating on 1.5 and supporting Xerces 2.2.
>
OK, that certainly e
near future.
Cheers,
Berin
>
> From: Per Jessen <[EMAIL PROTECTED]>
> Subject: recent cvs snapshot not building?
> Date: 22/05/2003 5:30:26
> To: xalan-c-users@xml.apache.org
>
> Hi,
>
> I've just tried building the latest snapshot, xalan and xerces both
Hi,
I've just tried building the latest snapshot, xalan and xerces both.
(xml-xalan_20030521164120.tar.gz, xml-xerces_20030521164322.tar.gz),
and didn't get too far with xalan -- see below.
I haven't really looked into it, but just in case anyone's already hit the
same thing?
I tried reverting
>>>>> "David" == David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]> writes:
David> As to your problem -- I just built on Linux with the latest
David> CVS without any errors. You might try doing a clean build:
David>make clean all
Thanks -
Colin,
I've been making use of the new wrapper classes
combined with Xerces 2.1.
The namespace being used for Xerces below is
2.2 - are you getting Xerces from CVS as well?
What variant of *NIX are you compiling Xalan
against?
I've found I can use the released Xerces 2.1
with the Xal
Hi Colin,
I don't know why our mailing list is set up that way. I've asked why
several times, but never gotten any response. I agree it's very
annoying...
As to your problem -- I just built on Linux with the latest CVS without any
errors. You might try doing a clean build:
. Why isn't this the default on xalan-c-users?
David> On the other hand, the new API is very much like the old
David> one, you just substitute the new class names for the old.
David> I believe if you've pulled down the latest CVS code, you'll
Well, I just did a
other hand, the new API is very much like the old one, you just
substitute the new class names for the old. I believe if you've pulled
down the latest CVS code, you'll find the sample applications were updated
to use the new wrapper. In particular, see the ParsedSourceWrappers
sample
On 17 Jan 2003 16:06:24 +, Colin Paul Adams wrote:
>How do I build xalan-c from CVS? There isn't a trace of documentation
>that I can see.
>I changed to the c directory. Noting the presence of a build.xml, I
>tried typing:
Colin,
try this:
http://cvs.apache.org/snapshots/
AIL PROTECTED] To:
xalan-c-users@xml.apache.org
mon.co.uk> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: How do I
How do I build xalan-c from CVS? There isn't a trace of documentation
that I can see.
I changed to the c directory. Noting the presence of a build.xml, I
tried typing:
ant
That produces:
Buildfile: build.xml
prepare:
[gunzip] Expanding /home/colin/xml-xalan/c/xdocs/xml-site-style.tar.
viewing patch updates is
never fun.)
Cheers,
Berin
>
> From: David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]>
> Subject: Re: Latest CVS
> Date: 17/11/2002 5:46:16
> To: xalan-c-users@xml.apache.org
>
>
>
>
>
> Hi Berin,
>
> > P
Hi Berin,
> Part of the XML Digital Signature spec (which is basically what I'm
> playing with - people do strange things in their spare time) defines a
> function here(), which is a function that returns the Node where the
> XPath expression was defined.
>
> One of the common ways of using th
Hi Berin,
> Part of the XML Digital Signature spec (which is basically what I'm
> playing with - people do strange things in their spare time) defines a
> function here(), which is a function that returns the Node where the
> XPath expression was defined.
>
> One of the common ways of using th
to a Xalan node. The assumption is that you really wouldn't want to do
that since you already have Xalan nodes returned by the execution of the
XPath expression.
I think there was another request for this feature, so I'm pretty sure I
can make it an option. If you want to experiment, I sugg
lan nodes returned by the execution of the
XPath expression.
I think there was another request for this feature, so I'm pretty sure I
can make it an option. If you want to experiment, I suggest you modify the
wrapper layer yourself. Try this patch and see what happens:
cvs -z9 diff XercesDoc
TECTED]> wrote:
I am converting some code over to the "new" DOM implementation in Xerces,
so last night downloaded the latest (at that time) CVS tarball.
Always a dangerous thing to do.
Livin' on the edge is fun!
Worked out how to move to the new *Wrapper classes, and had
<[EMAIL PROTECTED]> wrote:
> I am converting some code over to the "new" DOM implementation in Xerces,
> so last night downloaded the latest (at that time) CVS tarball.
>
> Always a dangerous thing to do.
Livin' on the edge is fun!
> Worked out how
installed versions according to the
thread).
Cheers,
Berin
>
> From: <[EMAIL PROTECTED]>
> Subject: Latest CVS
> Date: 15/11/2002 13:01:11
> To: xalan-c-users@xml.apache.org
>
> David,
>
> I am converting some code over to the "new" DOM implementat
David,
I am converting some code over to the "new" DOM implementation in Xerces, so
last night downloaded the latest (at that time) CVS tarball.
Always a dangerous thing to do.
Worked out how to move to the new *Wrapper classes, and had a whole lot of fun
and then came u
41 matches
Mail list logo
