You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Matthew L. Avizinis" <ml...@gleim.com> on 2001/05/22 20:27:10 UTC
compiling FOP 0_19_0-CVS snapshot
Hello all,
I am a software developer at my company here in Gainesville, FL which
produces accounting and aviation test preparation books and software. I am
currently working on an XML project to put all of our content into a
universal database which can then be transformed to whatever format is
needed, e.g. pdf, html, dBase, etc.
I am using FOP as part of the project and have been following its
development for a couple months now. Occasionally, I have been compiling
the cvs snapshots in an NT environment to keep track of new and/or improved
features. Up until now the fop project has compiled without a hitch. When
SVG was included, several java exceptions occurred all related to the same
thing. I am not a Java expert by any stretch of the imagination (I more
often work with Delphi), but apparently the file names, when called during
the build, are case sensitive. I don't know whether this is the case with
Linux or Unix, but, in NT anyhow, renaming the \svg\ files HKern.java,
SVG.java, TRef.java, TSpan.java, and VKern.java to Hkern.java, Svg.java,
Tref.java, Tspan.java, and Vkern.java respectively removes the errors. The
error was something to the effect that these classes should be defined in
files named as I've suggested. Perhaps this could be changed at the cvs
end.
thanks,
Matthew L. Avizinis
Gleim Publications, Inc.
4201 NW 95th Blvd.
Gainesville, FL 32606
(352)-375-0772 ext. 101
www.gleim.com
RE: compiling FOP 0_19_0-CVS snapshot
Posted by Keiron Liddle <ke...@aftexsw.com>.
On Wed, 23 May 2001 17:50:24 Matthew L. Avizinis wrote:
> I am only using the snapshot tar file of the cvs,
> xml-fop_20010522115910.tar.gz, and in that file they are in the
> xml-fop\src\org\apache\fop\svg folder. In another message I have
> outlined
> what I see to be the possible problem--it seems to be caused by the xsl
> translator, elements.xsl. Although the file is not renamed when built,
> the
> class is renamed, thus causing the compile problem.
> thanks for the interest,
In that case the snapshot build thing is broken.
Could whoever knows about it please fix it!
Either the cvs update is faulty or the build does not do a clean build
first.
The files are not renamed, the files should not exist and are created from
the svgelements.xml.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: compiling FOP 0_19_0-CVS snapshot
Posted by "Matthew L. Avizinis" <ml...@gleim.com>.
I am only using the snapshot tar file of the cvs,
xml-fop_20010522115910.tar.gz, and in that file they are in the
xml-fop\src\org\apache\fop\svg folder. In another message I have outlined
what I see to be the possible problem--it seems to be caused by the xsl
translator, elements.xsl. Although the file is not renamed when built, the
class is renamed, thus causing the compile problem.
thanks for the interest,
matt a
| -----Original Message-----
| From: Keiron Liddle [mailto:keiron@fztig938.bank.dresdner.net]On Behalf
| Of Keiron Liddle
| Sent: Wednesday, May 23, 2001 5:56 AM
| To: fop-dev@xml.apache.org
| Subject: Re: compiling FOP 0_19_0-CVS snapshot
|
|
|
| On Tue, 22 May 2001 20:27:10 Matthew L. Avizinis wrote:
| > I am using FOP as part of the project and have been following its
| > development for a couple months now. Occasionally, I have been
| compiling
| > the cvs snapshots in an NT environment to keep track of new and/or
| > improved
| > features. Up until now the fop project has compiled without a hitch.
| > When
| > SVG was included, several java exceptions occurred all related to the
| > same
| > thing. I am not a Java expert by any stretch of the imagination (I more
| > often work with Delphi), but apparently the file names, when called
| > during
| > the build, are case sensitive. I don't know whether this is the case
| > with
| > Linux or Unix, but, in NT anyhow, renaming the \svg\ files HKern.java,
| > SVG.java, TRef.java, TSpan.java, and VKern.java to Hkern.java, Svg.java,
| > Tref.java, Tspan.java, and Vkern.java respectively removes the errors.
| > The
| > error was something to the effect that these classes should be
| defined in
| > files named as I've suggested. Perhaps this could be changed at the cvs
| > end.
|
| It sounds like you have not done a proper cvs update. The files SVG.java,
| HKern.java etc. no longer live in /svg/. They are generated during the
| build process and have the correct names.
|
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
| For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: compiling FOP 0_19_0-CVS snapshot
Posted by Keiron Liddle <ke...@aftexsw.com>.
On Tue, 22 May 2001 20:27:10 Matthew L. Avizinis wrote:
> I am using FOP as part of the project and have been following its
> development for a couple months now. Occasionally, I have been compiling
> the cvs snapshots in an NT environment to keep track of new and/or
> improved
> features. Up until now the fop project has compiled without a hitch.
> When
> SVG was included, several java exceptions occurred all related to the
> same
> thing. I am not a Java expert by any stretch of the imagination (I more
> often work with Delphi), but apparently the file names, when called
> during
> the build, are case sensitive. I don't know whether this is the case
> with
> Linux or Unix, but, in NT anyhow, renaming the \svg\ files HKern.java,
> SVG.java, TRef.java, TSpan.java, and VKern.java to Hkern.java, Svg.java,
> Tref.java, Tspan.java, and Vkern.java respectively removes the errors.
> The
> error was something to the effect that these classes should be defined in
> files named as I've suggested. Perhaps this could be changed at the cvs
> end.
It sounds like you have not done a proper cvs update. The files SVG.java,
HKern.java etc. no longer live in /svg/. They are generated during the
build process and have the correct names.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: compiling FOP 0_19_0-CVS snapshot
Posted by "Matthew L. Avizinis" <ml...@gleim.com>.
|
| > I don't know whether this is the case with
| > Linux or Unix, but, in NT anyhow, renaming the \svg\ files HKern.java,
| > SVG.java, TRef.java, TSpan.java, and VKern.java to Hkern.java, Svg.java,
| > Tref.java, Tspan.java, and Vkern.java respectively removes the errors.
|
| The classes are in fact called HKern, SVG and so on so their file
| names are
| in fact correct.
Yes, I have worked with Linux quite a bit and I figured it might be the case
that Java would be case sensitive.
Do I understand it correctly that the xml-fop\build\ directory is created
from the xml-fop\src\ folder and then the files in the build\src\ folder are
the ones that are actually compiled? If that is the case, then I notice
that the HKern class (and the others) are named with differing names as I
stated in the original message, even though in the original src\ folder they
are named correctly and match the file name.
So, is the problem occurring when the file is being copied from
xml-fop\src\.. to the xml-fop\build\...\src\svg directory? The class in
that folder's HKern.java is defined as:
public class Hkern extends SVGObj {
/**
* inner class for making hkern objects.
*/
and it is this file name that I changed to Hkern.java to correct the
compilation problem.
Therefore, to me, it looks like the codegen\elements.xsl file is renaming
the class by an incorrect substring translation when it MakeClassName's the
HKern.java (and other named files) file. So, although the original resource
is correctly defined, it isn't in the file actually built.
thanks,
Matthew L. Avizinis <ma...@gleim.com>
Gleim Publications, Inc.
4201 NW 95th Blvd.
Gainesville, FL 32606
(352)-375-0772 ext. 101
www.gleim.com <http://www.gleim.com>
|
|
| Alex
|
| =====
| Alex McLintock alex@OWAL.co.uk
| OpenWeb Analysts Ltd, http://www.OWAL.co.uk/
| DR WHO COMPETITION:
http://www.diversebooks.com/cgi-bin/caption/captions.cgi?date=200104
Get Your XML T-Shirt <t-shirt/> at http://www.inversity.co.uk/
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: compiling FOP 0_19_0-CVS snapshot
Posted by Alex McLintock <al...@yahoo.com>.
--- "Matthew L. Avizinis" <ml...@gleim.com> wrote: > Hello all,
> Occasionally, I have been compiling
> the cvs snapshots in an NT environment to keep track of new and/or improved
> features. Up until now the fop project has compiled without a hitch. When
> SVG was included, several java exceptions occurred all related to the same
> thing. I am not a Java expert by any stretch of the imagination (I more
> often work with Delphi), but apparently the file names, when called during
> the build, are case sensitive.
In Unix everything is case sensitive unless explicitly specified otherwise.
Under NT you have this "We'll remember the case, but display it with an initial
capital letter, but let you pretend it's case-insensitive."
This works fine until sometimes in Java on NT it goes back to being totally
case sensitive.
My strategy is to always use - InitialCapitalForJava.classes
and lower case for everything else.
> I don't know whether this is the case with
> Linux or Unix, but, in NT anyhow, renaming the \svg\ files HKern.java,
> SVG.java, TRef.java, TSpan.java, and VKern.java to Hkern.java, Svg.java,
> Tref.java, Tspan.java, and Vkern.java respectively removes the errors.
The classes are in fact called HKern, SVG and so on so their file names are
in fact correct.
Alex
=====
Alex McLintock alex@OWAL.co.uk
OpenWeb Analysts Ltd, http://www.OWAL.co.uk/
DR WHO COMPETITION: http://www.diversebooks.com/cgi-bin/caption/captions.cgi?date=200104
Get Your XML T-Shirt <t-shirt/> at http://www.inversity.co.uk/
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org