[
https://issues.apache.org/jira/browse/CAMEL-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157281#comment-13157281
]
Babak Vahdat commented on CAMEL-3774:
-------------------------------------
@Willem,
as already promised I attached the generated PDF on my box
(camel-manual-2.9-SNAPSHOT.pdf) into this ticket. The odd thing I realized is
that all chapters by the second page (Table Of Contents) point to "Chapter 1".
Nevertheless it's still a proper and readable PDF.
Maybe you should check your setup regarding princexml installation, see my
previous posts regarding this by this ticket. Could you maybe paste the maven
output when you do mvn clean install on tooling/camel-manual?
Babak
> 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
>
> Attachments: camel-manual-2.9-SNAPSHOT.pdf
>
>
> 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
