[
https://issues.apache.org/jira/browse/RAT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327046#comment-14327046
]
Hervé Boutemy commented on RAT-158:
-----------------------------------
RAT can be used either as a report (apache-rat:rat) or a mojo
(apache-rat:check): in Maven project, for example, we use the mojo (check) only
to fail the build in case of non-compliance and I didn't even notice about the
report.
the proper solution starts with fixing Doxia, true: then everybody has to use
the fixed Doxia, ie maven site plugin and RAT maven plugin
And before Doxia is fixed, using the dependency exclusion workaround on any old
non-fixed Doxia version has exactly the same result than using fixed Doxia:
great, Doxia users don't absolutely require to wait for the fix, they have a
simple, now documented, workaround
1. if maven site plugin uses fixed Doxia but RAT maven plugin continue to use
non-fixed Doxia,
RAT maven plugin will continue to import (through non-fixed Doxia) Xerces
causing unwanted warnings (and this will happen both as mojo and report)
2. if RAT maven plugin uses fixed Doxia but maven site plugin continue to use
non-fixed Doxia,
since maven site plugin injects its dependencies into every reports, it will
inject non-fixed Doxia into RAT maven plugin report: there will be unwanted
warnings with RAT report (caused by maven site plugin, caused by Doxia, caused
by Xerces), but not with RAT mojo (which is independent from maven site plugin:
nothing is injected)
then BOTH maven site plugin AND RAT maven plugin must use the fixed Doxia
version (or use the Xerces exclusion wrokaround with a non-fixed Doxia)
That's why I added the maven site plugin configuration workaround in last
patch, to show the result (and I updated ASF parent pom too in MPOM-69)
I hope the full explanations are now clear for people wanting to understand why
and not only care on "it works" without precisely knowing the details
> SAXParser warnings
> ------------------
>
> Key: RAT-158
> URL: https://issues.apache.org/jira/browse/RAT-158
> Project: Apache Rat
> Issue Type: Bug
> Affects Versions: 0.10
> Environment: Apache Maven 3.0.4
> Maven home: /usr/share/maven
> Java version: 1.6.0_30, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.11.0-17-generic", arch: "amd64", family: "unix"
> Reporter: John Vines
> Priority: Minor
> Fix For: 0.12
>
> Attachments: RAT-158-2.patch, RAT-158.patch
>
>
> I have rat configured as such
> {code} <plugin>
> <groupId>org.apache.rat</groupId>
> <artifactId>apache-rat-plugin</artifactId>
> <inherited>false</inherited>
> <executions>
> <execution>
> <phase>verify</phase>
> <goals>
> <goal>check</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <excludes>
> <exclude>**/conf/**</exclude>
> </excludes>
> </configuration>
> </plugin>
> {code}
> And with every build where it triggers, I see
> {code}
> Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property
> 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
> recognized.
> Warning: org.apache.xerces.parsers.SAXParser: Feature
> 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
> Warning: org.apache.xerces.parsers.SAXParser: Property
> 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not
> recognized.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
