camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Babak Vahdat (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-3774) camel-manual generation fails during release process
Date Fri, 25 Nov 2011 08:40:40 GMT


Babak Vahdat commented on CAMEL-3774:

As I've already claimed by this ticket, trying:

mvn release:prepare -DdryRun=true 

failes beforehand by me @ maven-gpg-plugin because of the missing public key of mine in [1].
So that I can't even reproduce the issue on my box. I think even better than "mvn -X ..."
one could attach (remotely through IDE) to the maven process with something like:

MAVEN_OPTS = ... -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044

And then one could follow the exception chain completely down to the root cause where it's
thrown. However "mvn -X ..." on the other hand would dump something like:

 Caused by: ...
         ... 27 more
 Caused by: ...
         ... 9 more

into the console which wouldn't really give a clue where/why it has been thrown. Having the
exact point where it's thrown would then give us a good clue for further investigation. Regarding
the puzzle why "mvn install" works but not "mvn release" I suspect that the classpath setup
through maven are different in those cases, one with Xerces and/or Xalan and one without,
which seem to have some issues see [2] & [3] and also the comments in [4].

In worst case I think we should move towards something else other than Tagsoup. The ones I'm
aware of are:

- NekoHTML
- HtmlCleaner
- jTidy

I'll try to reproduce the behaviour using some of my own Apps but without much hope :-(


> camel-manual generation fails during release process
> ----------------------------------------------------
>                 Key: CAMEL-3774
>                 URL:
>             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
> {code}
> [INFO] [INFO] [html-to-pdf:compile {execution: default}]
> [INFO] [INFO] Downloading:
> [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 ''
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 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:!default.jspa
For more information on JIRA, see:


View raw message