[
https://issues.apache.org/jira/browse/CAMEL-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157162#comment-13157162
]
Babak Vahdat commented on CAMEL-3774:
-------------------------------------
Hi Willem,
My maven setup is:
{code}
D:\Data\eclipse-workspace\camel-trunk\tooling\camel-manual>mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: P:\My Documents\dev\env\apache-maven-3.0.3\bin\..
Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_29\jre
Default locale: de_CH, platform encoding: Cp1252
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
{code}
And when I do mvn clean install on tooling/camel-manual, I get the following
output:
{code}
[INFO] Downloading: http://camel.apache.org/book-in-one-page.html
[INFO] Stored:
D:\Data\eclipse-workspace\camel-trunk\tooling\camel-manual\target/site/manual/camel-manual-2.9-SNAPSHOT.html
[INFO] Converting to PDF with prince...
[INFO] About to execute PrinceXml (see www.princexml.com)
[INFO] prince
D:\Data\eclipse-workspace\camel-trunk\tooling\camel-manual\target/site/manual/camel-manual-2.9-SNAPSHOT.html
D:\Data\eclipse-workspace\camel-trunk\tooling\camel-manual\target/site/manual/camel-manual-2.9-SNAPSHOT.pdf
[INFO]
[INFO] --- build-helper-maven-plugin:1.5:attach-artifact (attach-artifacts) @
camel-manual ---
[INFO]
[INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @
camel-manual ---
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ camel-manual
---
[INFO] Installing
D:\Data\eclipse-workspace\camel-trunk\tooling\camel-manual\pom.xml to
D:\Data\Maven\repo\org\apache\camel\camel-manual\2.9-SNAPSHOT\camel-manual-2.9-SNAPSHOT.pom
[INFO] Installing
D:\Data\eclipse-workspace\camel-trunk\tooling\camel-manual\target\site\manual\camel-manual-2.9-SNAPSHOT.pdf
to
D:\Data\Maven\repo\org\apache\camel\camel-manual\2.9-SNAPSHOT\camel-manual-2.9-SNAPSHOT.pdf
{code}
Which produces a proper readable PDF :-(
Please note that I edited my previous post on this ticket with some more
informations about princexml. Could you check it please?
On windows before I do mvn clean install inside terminal I put prince.exe into
the Windows PATH variable, that's:
{code}
PATH=%PATH%;P:\My Documents\dev\env\prince\Engine\bin
{code}
On Unix / Mac (I assume) it would be something like
{code}
export PATH=$PATH:<path_to_your_princexml_installation>/Engine/bin
{code}
After setting the PATH properly then I do mvn clean install, which as said
before creates the PDF propery.
> camel-manual generation fails during release process
> ----------------------------------------------------
>
> Key: CAMEL-3774
> URL: https://issues.apache.org/jira/browse/CAMEL-3774
> Project: Camel
> Issue Type: Task
> Affects Versions: 2.6.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: Future
>
>
> It works during a regular mvn install, but it fails during release:prepare.
> The bug is somewhere in the maven-html-to-pdf plugin. I hope a mock release
> using mvn -X will reveal the problem, but would take a frustrating amount of
> time. For now the available info is the output:
> {code}
> [INFO] [INFO] [html-to-pdf:compile {execution: default}]
> [INFO] [INFO] Downloading: http://camel.apache.org/book-in-one-page.html
> [INFO] ERROR: 'NOT_FOUND_ERR: An attempt is made to reference a node in a
> context where it does not exist.'
> [INFO] [ERROR] Download or validation of
> 'http://camel.apache.org/book-in-one-page.html' failed:
> org.apache.camel.CamelException: Failed to convert the HTML to tidy Markup
> [INFO] [INFO] Stored dummy file:
> /w1/apache/release/camel270/tooling/camel-manual/target/site/manual/camel-manual-2.7.0.html
> since download of http://camel.apache.org/book-in-one-page.html failed.
> {code}
> The error points to a DOM related issue, but since the downloaded manual gets
> overwritten with the dummy file, I have no idea if the download got
> interrupted, or in what way the source gets corrupted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
