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 Thilo Schwidurski <th...@web.de> on 2002/11/26 11:14:21 UTC

Current CVS version won't build

Hi,

I checked out xml-fop from anoncvs@cvs.apache.org:/home/cvspublic (actually
using Eclipse), and tried to build the version.
The following error messages are displayed:

------------------------------------------------
hyphenation:
  [serHyph] Processing .\hyph\cs.xml
  [serHyph] Can't load patterns from xml file .\hyph\cs.xml - Maybe
hyphenation.
dtd is missing?

[...]

package:
     [echo] Creating the jar file ./build/fop.jar
      [jar] Building jar: C:\[...]\xml-fop\build\fop.jar
BUILD SUCCESSFUL
------------------------------------------------

So obviously the jar is built and I can run it. But the resulting PDF looks
pretty weird (definitily more weird than pretty ;-). Is the current
dev-release in the cvs broken (or at least the build.xml - the
hyphenation.dtd is present)? Should I (as user) not feel encouraged to check
out from there?
Using fop-0.20.4rc would work for me, if it wasn't for
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7815.

Christian Geisert writes about a soon available 0.20.5 release that adresses
the bug. Is there any information about the date? I looked for a 0.20.5
version/branch tag in the cvs but could'nt find one.

Kind regards,
Thilo.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Thilo Schwidurski <th...@web.de>.
----- Original Message -----
From: "Thilo Schwidurski" <th...@web.de>
>
> Well, after checking out the 0.20.5 branch I still face the exact same
> problems.

And this is (most likely) the reason: my path to the build directory
constains whitespace characters (a fragment of it is the W2K "Dokumente und
Einstellungen"), so the URI constructor throws a MalformedURIException. If I
had posted my complete path instead of "\[...]\xml-fop" you probably would
have been able to tell me earlier. Dammit. So much about red herrings... :-/

The problem is, that the "Path contains invalid character: " message which
the MalformedURIException gets initialized with is not transported to the
user, but the (less specific) message "no protocol: ".

Anyway, my resolution for this problem is clear now... ;-)

Bye,
Thilo.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Thilo Schwidurski <th...@web.de>.
----- Original Message -----
From: "Jeremias Maerki" <de...@greenmail.ch>
To: <fo...@xml.apache.org>
Sent: Tuesday, November 26, 2002 4:16 PM
Subject: Re: Current CVS version won't build


>
> On 26.11.2002 16:01:57 Chris Bowditch wrote:
> > it could well be that there is a problem with hypenation. The messages I
get
> > seem to relate to just 2/3 files out of 22.
>
> As far as I can tell hyphenation works file with the maintenance branch
> in CVS. docs/examples/fo/hyphen.fo looks good.
>
> > It was just that you seemed to be putting a lot of effort into solving
this,
> > when I thought Thilo's original question was just about getting and
building
> > 0.20.5cvs. Thilo started an earlier thread in the user list on this, in
> > which Christian Geisert told him his particular problem was fixed in
> > 0.20.5cvs. Note, the last paragraph in Thilo's first message:
>
> Ok, let's wait and see what Thilo responds.

Well, after checking out the 0.20.5 branch I still face the exact same
problems. I now just attached the Xerces 2.2.1 sources to be able to debug
in. Anyway, I have to stop now but will investigate further, tomorrow.

Bye,
Thilo.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Jeremias Maerki <de...@greenmail.ch>.
On 26.11.2002 16:01:57 Chris Bowditch wrote:
> it could well be that there is a problem with hypenation. The messages I get 
> seem to relate to just 2/3 files out of 22.

As far as I can tell hyphenation works file with the maintenance branch
in CVS. docs/examples/fo/hyphen.fo looks good.

> It was just that you seemed to be putting a lot of effort into solving this, 
> when I thought Thilo's original question was just about getting and building 
> 0.20.5cvs. Thilo started an earlier thread in the user list on this, in 
> which Christian Geisert told him his particular problem was fixed in 
> 0.20.5cvs. Note, the last paragraph in Thilo's first message:

Ok, let's wait and see what Thilo responds.

> <quote>
> Christian Geisert writes about a soon available 0.20.5 release that adresses
> the bug. Is there any information about the date? I looked for a 0.20.5
> version/branch tag in the cvs but could'nt find one.
> </quote>
> 
> I dont mean to be offensive, I just hate to see people's time wasted.

No problem. Anyway, if there's a problem with the build in certain
environments I'd like to have that fixed.

> Chris
> 
> >From: Jeremias Maerki <de...@greenmail.ch>
> >Reply-To: fop-dev@xml.apache.org
> >To: fop-dev@xml.apache.org
> >Subject: Re: Current CVS version won't build
> >Date: Tue, 26 Nov 2002 15:50:58 +0100
> >
> >Actually, the hyphenation stuff is the same for the maintenance branch
> >and the trunk and does not generate any error messages during build in
> >either codebase when done on the command line. It might of course be
> >that Thilo is on the wrong branch but he will experience this particular
> >problem anyway. But thanks for speaking up because that may help him to
> >reduce the time to track down the problem with unexpected output after
> >having solved the build problem in Eclipse. I've concentrated on the
> >build problem too much.
> >
> >On 26.11.2002 15:42:09 Chris Bowditch wrote:
> > > Thilo, Jeremias,
> > >
> > > After reading Thilo's first message my understanding is that the reason 
> >for
> > > getting unexpected output in the resulting PDF is that he checked out 
> >the
> > > Trunk, and not the maintenance branch.
> > >
> > > Thilo, if you want to get 0.20.5cvs, then you need to check out using 
> >the
> > > branch label fop-0_20_2-maintain. If you didnt use a label to check out 
> >the
> > > source from CVS then you will have the Trunk code which is still under
> > > development.
> > >
> > > I think the message about hypenation when building FOP is a red herring. 
> >I
> > > also get that message when building but my output (for English anyway) 
> >is
> > > fine.


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Jeremias Maerki <de...@greenmail.ch>.
Actually, the hyphenation stuff is the same for the maintenance branch
and the trunk and does not generate any error messages during build in
either codebase when done on the command line. It might of course be
that Thilo is on the wrong branch but he will experience this particular
problem anyway. But thanks for speaking up because that may help him to
reduce the time to track down the problem with unexpected output after
having solved the build problem in Eclipse. I've concentrated on the
build problem too much.

On 26.11.2002 15:42:09 Chris Bowditch wrote:
> Thilo, Jeremias,
> 
> After reading Thilo's first message my understanding is that the reason for 
> getting unexpected output in the resulting PDF is that he checked out the 
> Trunk, and not the maintenance branch.
> 
> Thilo, if you want to get 0.20.5cvs, then you need to check out using the 
> branch label fop-0_20_2-maintain. If you didnt use a label to check out the 
> source from CVS then you will have the Trunk code which is still under 
> development.
> 
> I think the message about hypenation when building FOP is a red herring. I 
> also get that message when building but my output (for English anyway) is 
> fine.


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Thilo Schwidurski <th...@web.de>.
----- Original Message -----
From: "Jeremias Maerki" <de...@greenmail.ch>
To: <fo...@xml.apache.org>
Sent: Tuesday, November 26, 2002 1:55 PM
Subject: Re: Current CVS version won't build


>
> On 26.11.2002 13:19:54 Thilo Schwidurski wrote:
> > The pathes look like this: "c:\[...]\xml-fop\.\hyph\cs.xml"
> > It would think it is the PatternParser that has a problem with the "\.\"
> > (perhaps only under Windows?)
>
> Well, that looks ok to me. The "." should not be a problem IMO. Have you
> been able to display the stacktrace of the HyphenationException that's
> happening in that method?

[serHyph] org.apache.fop.layout.hyphenation.HyphenationException: no
protocol: hyphenation.dtd

Would be good to know where the Parser searched for the hyphenation.dtd.
I just got the eclipse project setup right for debugging. I will dig down
deeper to find out whats happening.

Bye,
Thilo.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Jeremias Maerki <de...@greenmail.ch>.
On 26.11.2002 13:19:54 Thilo Schwidurski wrote:
> The pathes look like this: "c:\[...]\xml-fop\.\hyph\cs.xml"
> It would think it is the PatternParser that has a problem with the "\.\"
> (perhaps only under Windows?)

Well, that looks ok to me. The "." should not be a problem IMO. Have you
been able to display the stacktrace of the HyphenationException that's
happening in that method?


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Thilo Schwidurski <th...@web.de>.
----- Original Message -----
From: "Thilo Schwidurski" <th...@web.de>
To: <fo...@xml.apache.org>
Sent: Tuesday, November 26, 2002 12:33 PM
Subject: Re: Current CVS version won't build


>
> ----- Original Message -----
> From: "Jeremias Maerki" <de...@greenmail.ch>
> To: <fo...@xml.apache.org>
> Sent: Tuesday, November 26, 2002 12:16 PM
> Subject: Re: Current CVS version won't build
>
>
> > Thilo,
> >
> > would you like to help me find out what the problem is?
>
>
> Sure (right after lunch;-).
>
> > If yes, could you change your local
> > org.apache.fop.tools.anttasks.SerializeHyphPattern.java so it displays
> > the absolute path instead of the relative one? That way we can find out
> > what's different in the Eclipse environment.

The pathes look like this: "c:\[...]\xml-fop\.\hyph\cs.xml"
It would think it is the PatternParser that has a problem with the "\.\"
(perhaps only under Windows?)

Bye,
Thilo.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Thilo Schwidurski <th...@web.de>.
----- Original Message -----
From: "Jeremias Maerki" <de...@greenmail.ch>
To: <fo...@xml.apache.org>
Sent: Tuesday, November 26, 2002 12:16 PM
Subject: Re: Current CVS version won't build


> Thilo,
>
> would you like to help me find out what the problem is?


Sure (right after lunch;-).

> If yes, could you change your local
> org.apache.fop.tools.anttasks.SerializeHyphPattern.java so it displays
> the absolute path instead of the relative one? That way we can find out
> what's different in the Eclipse environment.

One more info: I just found out that even building from the command line
with the fop-cvs-root set as current dir will still result in the same
reported errors (after cleaning the build).
Actually, after suspecting that eclipse and its' ant integration might be
the problem, I always builded with build.bat, yet not with the fop-cvs-root
being the current dir. The results were different in fact.

Regards,
Thilo.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Jeremias Maerki <de...@greenmail.ch>.
Thilo,

would you like to help me find out what the problem is? If yes, could
you change your local
org.apache.fop.tools.anttasks.SerializeHyphPattern.java so it displays
the absolute path instead of the relative one? That way we can find out
what's different in the Eclipse environment.

Here's a the first lines of a method from that class:

    private void buildPatternFile(File infile, File outfile) {
        System.out.println("Processing " + infile);
        HyphenationTree hTree = new HyphenationTree();
        try {
            hTree.loadPatterns(infile.toString());
            if (errorDump) {
                System.out.println("Stats: ");
                hTree.printStats();
            }
        } catch (HyphenationException ex) {
            System.err.println("Can't load patterns from xml file " + infile
                               + " - Maybe hyphenation.dtd is missing?");
            if (errorDump) {
                System.err.println(ex.toString());
            }
        }
        
If you changed the first System.out line to something like this, we will
get more info:
        System.out.println("Processing " + infile + "(" + infile.getAbsolutePath()
        + ")");
        
You could also hardcode errorDump to true.

On 26.11.2002 12:01:21 Thilo Schwidurski wrote:
> 
> ----- Original Message -----
> From: "Jeremias Maerki" <de...@greenmail.ch>
> To: <fo...@xml.apache.org>
> Sent: Tuesday, November 26, 2002 11:29 AM
> Subject: Re: Current CVS version won't build
> 
> 
> [build problems...]
> > I've just checked and I can build on the command line.
> 
> I see, I can build on the command line too. I just did'nt try it before.
> 
> > Everything looks
> > fine. Could you turn on debug info in Ant? Ant should then output the
> > stacktrace of the original problem. Maybe we can then find out what's
> > wrong. Will probably have to do with the relative paths.
> 
> That's what I think too. Debug info from ant was not very helpful because it
> does'nt report which is the current watched path AFAIR ("./hyph not found"
> or something was reported) - but I will check this again.
> 
> [...]
> > If you want to check out what has been improved/changed or want to help
> > us test, then yes, of course.
> 
> ok. good.
> 
> 
> [...]
> > Nothing's fixed yet but it will happen very soon now. CVS should work ok,
> > though.
> 
> Great, very soon is even sooner than soon. It's done when it's done, is'nt
> it? ;-)
> I am just kidding. Thanks for the quick and kind answer, Jeremias. Thanks
> for a product that I need and can use for free.


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Thilo Schwidurski <th...@web.de>.
----- Original Message -----
From: "Jeremias Maerki" <de...@greenmail.ch>
To: <fo...@xml.apache.org>
Sent: Tuesday, November 26, 2002 11:29 AM
Subject: Re: Current CVS version won't build


[build problems...]
> I've just checked and I can build on the command line.

I see, I can build on the command line too. I just did'nt try it before.

> Everything looks
> fine. Could you turn on debug info in Ant? Ant should then output the
> stacktrace of the original problem. Maybe we can then find out what's
> wrong. Will probably have to do with the relative paths.

That's what I think too. Debug info from ant was not very helpful because it
does'nt report which is the current watched path AFAIR ("./hyph not found"
or something was reported) - but I will check this again.

[...]
> If you want to check out what has been improved/changed or want to help
> us test, then yes, of course.

ok. good.


[...]
> Nothing's fixed yet but it will happen very soon now. CVS should work ok,
> though.

Great, very soon is even sooner than soon. It's done when it's done, is'nt
it? ;-)
I am just kidding. Thanks for the quick and kind answer, Jeremias. Thanks
for a product that I need and can use for free.

Kind Regards,
Thilo.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Re: Current CVS version won't build

Posted by Jeremias Maerki <de...@greenmail.ch>.
On 26.11.2002 11:14:21 Thilo Schwidurski wrote:
> Hi,
> 
> I checked out xml-fop from anoncvs@cvs.apache.org:/home/cvspublic (actually
> using Eclipse), and tried to build the version.
> The following error messages are displayed:
> 
> ------------------------------------------------
> hyphenation:
>   [serHyph] Processing .\hyph\cs.xml
>   [serHyph] Can't load patterns from xml file .\hyph\cs.xml - Maybe
> hyphenation.
> dtd is missing?
> 
> [...]
> 
> package:
>      [echo] Creating the jar file ./build/fop.jar
>       [jar] Building jar: C:\[...]\xml-fop\build\fop.jar
> BUILD SUCCESSFUL
> ------------------------------------------------

I've just checked and I can build on the command line. Everything looks
fine. Could you turn on debug info in Ant? Ant should then output the
stacktrace of the original problem. Maybe we can then find out what's
wrong. Will probably have to do with the relative paths. I'll see if I
can find out anything in the meantime.

> So obviously the jar is built and I can run it. But the resulting PDF looks
> pretty weird (definitily more weird than pretty ;-). Is the current
> dev-release in the cvs broken (or at least the build.xml - the
> hyphenation.dtd is present)? Should I (as user) not feel encouraged to check
> out from there?

If you want to check out what has been improved/changed or want to help
us test, then yes, of course.

> Using fop-0.20.4rc would work for me, if it wasn't for
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7815.
> 
> Christian Geisert writes about a soon available 0.20.5 release that adresses
> the bug. Is there any information about the date? I looked for a 0.20.5
> version/branch tag in the cvs but could'nt find one.

Nothing's fixed yet but it will happen very soon now. CVS should work ok,
though.



Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org