Jochen Maes wrote:
do you have the J.D.K. 1.3.1 installed? Because i had the same error with
the J.D.K.1.2.2 and then i installed J.D.K.1.3.1 and everything worked...
try it...
I am running with Sun JDK 1.3.1.2 on RedHat Linux 7.2. With the same
machine and same configuration. The builds
One little thing I forgot to mention.
On Fri, 14 Dec 2001, Sam Ruby [EMAIL PROTECTED] wrote:
[about FOP's xslt task]
Finally, there is a depends attribute which can declare other files
which are referenced for the uptodate check. This can be done with
the uptodate task. This is the only
On Fri, 14 Dec 2001, Keiron Liddle [EMAIL PROTECTED] wrote:
Thanks, I have updated the build file to use the manifest under jar,
works fine.
Great!
Looking at the hostname I think that it is better left out, it may
cause computers to attempt to connect to the internet when resolving
the
Stefan Bodewig wrote:
I guess my response to your commit message hasn't made it to
fop-dev yet.
I've manually approved two more messages. Anyone on the fop-dev team want
to volunteer to become moderator? My guess is that the current moderator
has become backlogged for some reason.
There
On Fri, 14 Dec 2001, Sam Ruby [EMAIL PROTECTED] wrote:
Stefan Bodewig wrote:
I guess my response to your commit message hasn't made it to
fop-dev yet.
I've manually approved two more messages.
Thanks, shouldn't be necessary any longer, I've subscribed to fop-dev
shortly after sending my
I think I know what's going on, but I don't have all pieces together
to test it (yet) - does it work if you move the taskdef for FOP's
manifest task out of the target and make it a sibling of target?
Stefan
-
To unsubscribe,
On 2001.12.13 15:07 Sam Ruby wrote:
This is the first time I have seen such a failure - collisions on Ant
task
names. Did something change in Ant yesterday which made the properties
file take precidence over taskdefs? Is there some way that the Ant and
FOP
teams can work together to
On Thu, 13 Dec 2001, Sam Ruby [EMAIL PROTECTED] wrote:
Did something change in Ant yesterday which made the properties file
take precidence over taskdefs?
No, at least not yesterday. What has changed yesterday is that we've
added a new task named manifest, so there simply hasn't been any
A quick fix, change the package target to
target name=package depends=compile,hyphenation
echo message=Creating the jar file ${build.dir}/${name}.jar/
jar jarfile=${build.dir}/${name}.jar
basedir=${build.dest}
includes=org/**,conf/**,hyph/**
manifest
I'm currently not subscribed to fop-dev and responding to a post I've
picked up from the archives, sorry, please keep ant-dev in the CC.
Keiron Liddle [EMAIL PROTECTED] wrote:
We can update the FOP build to use the core ant manifest task and a
new ant. This is no real problem.
I don't see
--- Stefan Bodewig [EMAIL PROTECTED] wrote:
Hostname would be the only tricky part.
Can't you get it from the environment -- HOSTNAME on *nix, COMPUTERNAME on
Win* (or is COMPUTERNAME only an NT thing)?
Diane
=
([EMAIL PROTECTED])
__
Do
Thanks, I have updated the build file to use the manifest under jar, works
fine. Looking at the hostname I think that it is better left out, it may
cause computers to attempt to connect to the internet when resolving the
hostname.
I don't know much about xslt apart from - it works.
What sort
Keiron Liddle wrote:
I would like to raise an issue about this. I am not complaining, just
pointing out some things.
Remember - the point of Gump is to encourage people to communicate. Are
the fop and batik people communicating, or is the gump nags the only form
of communication for these
Hi fellow foppers,
Concerning the recent GUMP build failures, Sam Ruby wrote:
... the following change:
http://cvs.apache.org/viewcvs.cgi/xml-xalan/java/src/org/apache/xalan/templates/FuncDocument.java.diff?r1=1.23r2=1.24
..causes the following build failure:
Hi Sam,
Can you do a clean checkout? We now include (and use) the Avalon
Framework and LogKit 1.0b4. In addition, we reorganized a few things. It
should build fine if you do.
-Steve
-Original Message-
From: Sam Ruby [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 21, 2001 8:56
Steven Coffman wrote:
Can you do a clean checkout? We now include (and use) the Avalon
Framework and LogKit 1.0b4. In addition, we reorganized a few things. It
should build fine if you do.
This looks like the same problem that I tracked down on the 18th and reported here.
Namely that
Hi fop and xalan dev,
The problem here seems to be that the XSLT document function, when
called with a single argument which is a node-set (in the fop case, a
single element or attribute node) is now using the current directory as
the base URI to resolve relative URI references.
It should use
I've tried to work out what the problem with this is without success.
The information suggests there is no xalan1 and that xalan2 is present (at
least for the first bit).
I've tried using the current xalan2 cvs without any problems.
Does anyone know what the problem might be?
Could it be
On Mon, 30 Jul 2001, Keiron Liddle [EMAIL PROTECTED] wrote:
I've tried to work out what the problem with this is without
success. The information suggests there is no xalan1 and that
xalan2 is present (at least for the first bit).
I think it is that JAXP 1.1 is present (and thus the TraX
Karen Lease [EMAIL PROTECTED] wrote:
I see there are several of these. I guess they are coming from the
automatic nightly build.
Yes, I think so (not sure whether Sam is reading this list and as I'm
at least a little familiar with Gump, I thought I should jump in).
This message comes from a
Hi all,
I see there are several of these. I guess they are coming from the
automatic nightly build. The exception is being thrown by the stylesheet
itself because one of its named templates sees an unexpected situation.
Since none of the xsl or foproperties.xml files in codegen has been
touched
21 matches
Mail list logo
