[ 
https://issues.apache.org/jira/browse/YETUS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615052#comment-16615052
 ] 

Sean Busbey commented on YETUS-693:
-----------------------------------

note to self: look for background on problems falling back to i.e. xmllint as 
an option.

> Add warning about requirements for XML test-patch test
> ------------------------------------------------------
>
>                 Key: YETUS-693
>                 URL: https://issues.apache.org/jira/browse/YETUS-693
>             Project: Yetus
>          Issue Type: Improvement
>          Components: Test Patch
>    Affects Versions: 0.6.0, 0.7.0, 0.8.0
>            Reporter: Sean Busbey
>            Priority: Minor
>
> When running Test-Patch with some JVM's (currently seen in Azul JDK7 over in 
> HBase) the "xml" test always votes -1
> {code}
> ...
> 15:51:42 
> ============================================================================
> 15:51:42 
> ============================================================================
> 15:51:42                           XML verification: patch
> 15:51:42 
> ============================================================================
> 15:51:42 
> ============================================================================
> 15:51:42 
> 15:51:42 
> 15:51:42 
> 15:51:42 
> 15:51:42 
> ============================================================================
> ...
> 17:24:45 |  -1  |           xml  |   0m  0s   | The patch has 1 ill-formed 
> XML file(s). 
> ...
> 17:24:45               Reason | Tests
> 17:24:45                 XML  |  Parsing Error(s): 
> 17:24:45                      |  pom.xml 
> ...
> {code}
> The actual output indicates the problem is the JDK we have doesn't support 
> javascript scripting:
> {code}
> pom.xml:
> script engine for language js can not be found
> {code}
> Maybe we could do a quick known-pass and known-fail check in setup for the 
> plugin?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to