[
https://issues.apache.org/jira/browse/CAMEL-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157029#comment-13157029
]
Babak Vahdat commented on CAMEL-3774:
-------------------------------------
As I've already claimed by this ticket, trying:
{code}
mvn release:prepare -DdryRun=true
{code}
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:
{code}
MAVEN_OPTS = ... -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044
{code}
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:
{code}
...
Caused by: ...
... 27 more
...
.....
Caused by: ...
... 9 more
...
{code}
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 :-(
[1] https://svn.apache.org/repos/asf/camel/trunk/KEYS
[2] http://osdir.com/ml/text.xml.xforms.chiba.devel/2005-03/msg00068.html
[3]
http://apache-tika-users.1629097.n2.nabble.com/Xerces-Xalan-x-marks-the-spot-td3791968.html
[4]
https://svn.apache.org/repos/asf/camel/trunk/components/camel-tagsoup/pom.xml
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
>
>
> 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
