[
https://issues.apache.org/jira/browse/RAT-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325182#comment-16325182
]
Matthias Bläsing commented on RAT-242:
--------------------------------------
Philipp thank you for merging the patch. I checked the current state in the
subversion and found the new unittests failing. I tracked it down to a followup
commit in revision 1821058, that modifies
apache-rat-tasks/src/test/resources/org/example/iso-8859-1.html
and adds a license header to this file. The license header must not be there,
as the whole point of this file is to cause the rat test in the unittests to
fail and report the encoded header.
Your commit message mentions failing jenkis build. Could it be, that there is a
rat check in place, that now fails, because there are two files in the
repository that don't hold a valid license:
./apache-rat-plugin/src/test/resources/unit/it4/iso-8859-1.html
./apache-rat-tasks/src/test/resources/org/example/iso-8859-1.html
Could you point me to the jenkins build report, I'd like to have a look at it,
to finally fix this.
> Encoding of XML report
> ----------------------
>
> Key: RAT-242
> URL: https://issues.apache.org/jira/browse/RAT-242
> Project: Apache Rat
> Issue Type: Bug
> Components: reports
> Affects Versions: 0.12
> Environment: ubuntu
> Reporter: Eric Barboni
> Attachments: rat-242.patch
>
>
> Hi, we encounter an issue with encoding of a xml rat report.
> We try to parse an xml rat report generated on an iso-8859-1 file system. The
> xml has no encoding element in the prolog. If you open it with fileinpustream
> it may fail.
> last comment in this pull request
> (https://github.com/apache/incubator-netbeans/pull/70) by Matthias Bläsing
> suggest forcing to UTF-8.
> encoding may also be an option in the report task
> Regards
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
