[jira] [Commented] (RAT-163) Gradle Rat plugin
[ https://issues.apache.org/jira/browse/RAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909763#comment-14909763 ] Jochen Wiedmann commented on RAT-163: - [~eskatos] Would you be able to provide a patch, that removes the Gradle plugin out of the "apache-rat-project", and into a separate subproject of Creadur? I think that would make more sense in the medium term. Right now, the Gradle plugin is an obstacle for the development of the Rat core, because we don't really control it. > Gradle Rat plugin > - > > Key: RAT-163 > URL: https://issues.apache.org/jira/browse/RAT-163 > Project: Apache Rat > Issue Type: New Feature >Reporter: David Chen > > A number of new Apache projects, such as Samza, are using Gradle. However, > there currently does not exist a Rat plugin for Gradle. The closest > alternative, the Gradle License Plugin > (https://github.com/hierynomus/license-gradle-plugin) is not flexible enough > compared to Rat for use cases such as defining exclusion rules. > I have created a preliminary Gradle Rat plugin as part of SAMZA-285 and would > like to clean it up and make it a proper Gradle Rat plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-208) Add support for exclude files to maven plugin
[ https://issues.apache.org/jira/browse/RAT-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909920#comment-14909920 ] Till Westmann commented on RAT-208: --- Nice. Thanks, Jochen! When do you think this will be released? > Add support for exclude files to maven plugin > - > > Key: RAT-208 > URL: https://issues.apache.org/jira/browse/RAT-208 > Project: Apache Rat > Issue Type: Improvement > Components: maven >Reporter: Till Westmann >Assignee: Jochen Wiedmann > Fix For: 0.12 > > Attachments: RAT-208.patch > > > The RAT command line supports an exclude file. It would be nice, if the same > exclude files that can be used for the command line could also be used for > the maven plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-163) Gradle Rat plugin
[ https://issues.apache.org/jira/browse/RAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933774#comment-14933774 ] Philipp Ottlinger commented on RAT-163: --- [~eskatos] thanks again for your contribution - if you could change your patch to be workable with JDK5 and not use dependencies that are built with >JDK5 the plugin would easily be integrated into the current RAT stack. > Gradle Rat plugin > - > > Key: RAT-163 > URL: https://issues.apache.org/jira/browse/RAT-163 > Project: Apache Rat > Issue Type: New Feature >Reporter: David Chen > > A number of new Apache projects, such as Samza, are using Gradle. However, > there currently does not exist a Rat plugin for Gradle. The closest > alternative, the Gradle License Plugin > (https://github.com/hierynomus/license-gradle-plugin) is not flexible enough > compared to Rat for use cases such as defining exclusion rules. > I have created a preliminary Gradle Rat plugin as part of SAMZA-285 and would > like to clean it up and make it a proper Gradle Rat plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-163) Gradle Rat plugin
[ https://issues.apache.org/jira/browse/RAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933793#comment-14933793 ] Paul Merlin commented on RAT-163: - Ok, feel free to ditch the plugin from the creadur-rat repository. I'll work on a new proposal next month, see https://github.com/eskatos/creadur-rat-gradle/issues/4 In the meantime the plugin is available under a non-asf namespace: https://plugins.gradle.org/plugin/org.nosphere.apache.rat > Gradle Rat plugin > - > > Key: RAT-163 > URL: https://issues.apache.org/jira/browse/RAT-163 > Project: Apache Rat > Issue Type: New Feature >Reporter: David Chen > > A number of new Apache projects, such as Samza, are using Gradle. However, > there currently does not exist a Rat plugin for Gradle. The closest > alternative, the Gradle License Plugin > (https://github.com/hierynomus/license-gradle-plugin) is not flexible enough > compared to Rat for use cases such as defining exclusion rules. > I have created a preliminary Gradle Rat plugin as part of SAMZA-285 and would > like to clean it up and make it a proper Gradle Rat plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-163) Gradle Rat plugin
[ https://issues.apache.org/jira/browse/RAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935143#comment-14935143 ] Jochen Wiedmann commented on RAT-163: - Regarding "Building with JDK 5", please note the following: If the Gradle Plugin is decoupled from the Rat Core, it (and its dependencies) may very easily use another Java version. So, decoupling will resolve that issue automatically. As a consequence, and assuming Pauls okay, I'll remove the Gradle Plugin now from the Rat Core. > Gradle Rat plugin > - > > Key: RAT-163 > URL: https://issues.apache.org/jira/browse/RAT-163 > Project: Apache Rat > Issue Type: New Feature >Reporter: David Chen > > A number of new Apache projects, such as Samza, are using Gradle. However, > there currently does not exist a Rat plugin for Gradle. The closest > alternative, the Gradle License Plugin > (https://github.com/hierynomus/license-gradle-plugin) is not flexible enough > compared to Rat for use cases such as defining exclusion rules. > I have created a preliminary Gradle Rat plugin as part of SAMZA-285 and would > like to clean it up and make it a proper Gradle Rat plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-163) Gradle Rat plugin
[ https://issues.apache.org/jira/browse/RAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann updated RAT-163: Assignee: Jochen Wiedmann > Gradle Rat plugin > - > > Key: RAT-163 > URL: https://issues.apache.org/jira/browse/RAT-163 > Project: Apache Rat > Issue Type: New Feature >Reporter: David Chen >Assignee: Jochen Wiedmann > > A number of new Apache projects, such as Samza, are using Gradle. However, > there currently does not exist a Rat plugin for Gradle. The closest > alternative, the Gradle License Plugin > (https://github.com/hierynomus/license-gradle-plugin) is not flexible enough > compared to Rat for use cases such as defining exclusion rules. > I have created a preliminary Gradle Rat plugin as part of SAMZA-285 and would > like to clean it up and make it a proper Gradle Rat plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-163) Gradle Rat plugin
[ https://issues.apache.org/jira/browse/RAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935166#comment-14935166 ] Paul Merlin commented on RAT-163: - > Regarding "Building with JDK 5", please note the following: If the Gradle > Plugin is decoupled from the Rat Core, it (and its dependencies) may very > easily use another Java version. > So, decoupling will resolve that issue automatically. I'll continue to maintain it outside the ASF until the RAT project can receive it (dependencies issues resolved or separate code-repository/build). > As a consequence, and assuming Pauls okay, I'll remove the Gradle Plugin now > from the Rat Core. Yup, I'm okay! :-) Bye > Gradle Rat plugin > - > > Key: RAT-163 > URL: https://issues.apache.org/jira/browse/RAT-163 > Project: Apache Rat > Issue Type: New Feature >Reporter: David Chen >Assignee: Jochen Wiedmann > > A number of new Apache projects, such as Samza, are using Gradle. However, > there currently does not exist a Rat plugin for Gradle. The closest > alternative, the Gradle License Plugin > (https://github.com/hierynomus/license-gradle-plugin) is not flexible enough > compared to Rat for use cases such as defining exclusion rules. > I have created a preliminary Gradle Rat plugin as part of SAMZA-285 and would > like to clean it up and make it a proper Gradle Rat plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-208) Add support for exclude files to maven plugin
[ https://issues.apache.org/jira/browse/RAT-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935342#comment-14935342 ] Jochen Wiedmann commented on RAT-208: - @[~tillw]: I've called for a release on dev@creadur. > Add support for exclude files to maven plugin > - > > Key: RAT-208 > URL: https://issues.apache.org/jira/browse/RAT-208 > Project: Apache Rat > Issue Type: Improvement > Components: maven >Reporter: Till Westmann >Assignee: Jochen Wiedmann > Fix For: 0.12 > > Attachments: RAT-208.patch > > > The RAT command line supports an exclude file. It would be nice, if the same > exclude files that can be used for the command line could also be used for > the maven plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-161) Support exclusion of paths: "path/to/file.ext"
[ https://issues.apache.org/jira/browse/RAT-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935449#comment-14935449 ] Sandhya Sundaresan commented on RAT-161: Erik's proposal would certainly help us in the Trafodion project. We have a high level directory sturcture on which we'd like to run RAT. We have several subdirectories and want to include only a subset of files in each of those directories. Using filename patterns without /path would make the exclusions imprecise. There may be the same file it 2 different subdirectories and both would get excluded which we don't really intend to do.We want to exclude specific files in specific directories with a regexp. Unfortunately it isn't working. > Support exclusion of paths: "path/to/file.ext" > > > Key: RAT-161 > URL: https://issues.apache.org/jira/browse/RAT-161 > Project: Apache Rat > Issue Type: New Feature > Components: reports >Reporter: Erik Erlandson >Assignee: Philipp Ottlinger >Priority: Minor > Fix For: 0.12 > > Attachments: RAT-161.2.patch > > > It would be advantageous to be able to exclude specific files, e.g. > "path/to/file.ext" > The current '-E' feature cannot do this, as the filter patterns are only > applied to individual files as directory tree is traversed, so a filter will > never see "path/to/file.ext", only "path", "to" and "file.ext" > See for example: SPARK-1493 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-208) Add support for exclude files to maven plugin
[ https://issues.apache.org/jira/browse/RAT-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935673#comment-14935673 ] Till Westmann commented on RAT-208: --- Thanks! Great turnaround time. > Add support for exclude files to maven plugin > - > > Key: RAT-208 > URL: https://issues.apache.org/jira/browse/RAT-208 > Project: Apache Rat > Issue Type: Improvement > Components: maven >Reporter: Till Westmann >Assignee: Jochen Wiedmann > Fix For: 0.12 > > Attachments: RAT-208.patch > > > The RAT command line supports an exclude file. It would be nice, if the same > exclude files that can be used for the command line could also be used for > the maven plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-190) False negatives(?) in apache rat license checking
[ https://issues.apache.org/jira/browse/RAT-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053436#comment-15053436 ] Dan Dumont commented on RAT-190: Is it possible for it to use the file encoding specified in the maven-resources-plugin? > False negatives(?) in apache rat license checking > - > > Key: RAT-190 > URL: https://issues.apache.org/jira/browse/RAT-190 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.8, 0.11 >Reporter: Dan Dumont > Attachments: complete-pom.xml, test.zip > > > We're using rat to enforce our internal copyright on all of our source files. > We're seeing it missing files that should be flagged. Here's part of our pom: > >implementation="org.apache.rat.analysis.license.SimplePatternBasedLicense"> > IBMCL > IBM Copyright > > > Copyright IBM Corp. 2015 > Copyright IBM Corp. 2014, 2015 > Copyright IBM Corp. 2013, 2015 > > > > > > IBM Copyright > > > The file in question is "included" as reported by running with debug > output... but the file's copyright is: > /* Copyright IBM Corp. 2014 All Rights Reserved.*/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-190) False negatives(?) in apache rat license checking
[ https://issues.apache.org/jira/browse/RAT-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053445#comment-15053445 ] Dan Dumont commented on RAT-190: Also, I still think it's a good idea to fail the verification if the idea is to make sure all files have a copyright header and rat can't read the file. > False negatives(?) in apache rat license checking > - > > Key: RAT-190 > URL: https://issues.apache.org/jira/browse/RAT-190 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.8, 0.11 >Reporter: Dan Dumont > Attachments: complete-pom.xml, test.zip > > > We're using rat to enforce our internal copyright on all of our source files. > We're seeing it missing files that should be flagged. Here's part of our pom: > >implementation="org.apache.rat.analysis.license.SimplePatternBasedLicense"> > IBMCL > IBM Copyright > > > Copyright IBM Corp. 2015 > Copyright IBM Corp. 2014, 2015 > Copyright IBM Corp. 2013, 2015 > > > > > > IBM Copyright > > > The file in question is "included" as reported by running with debug > output... but the file's copyright is: > /* Copyright IBM Corp. 2014 All Rights Reserved.*/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RAT-210) Adapt webpage to new corporate design
Philipp Ottlinger created RAT-210: - Summary: Adapt webpage to new corporate design Key: RAT-210 URL: https://issues.apache.org/jira/browse/RAT-210 Project: Apache Rat Issue Type: Improvement Components: maven Affects Versions: 0.11 Reporter: Philipp Ottlinger Assignee: Philipp Ottlinger Fix For: 0.12 We need to adapt creadur webpages to contain the new logo. In addition to that links should be SSL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-210) Adapt webpage to new corporate design
[
https://issues.apache.org/jira/browse/RAT-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger resolved RAT-210.
---
Resolution: Fixed
Done on trunk
{code}
Revision 1727657
{code]
https://svn.apache.org/viewvc?view=revision&revision=1727657
> Adapt webpage to new corporate design
> -
>
> Key: RAT-210
> URL: https://issues.apache.org/jira/browse/RAT-210
> Project: Apache Rat
> Issue Type: Improvement
> Components: maven
>Affects Versions: 0.11
>Reporter: Philipp Ottlinger
>Assignee: Philipp Ottlinger
> Fix For: 0.12
>
>
> We need to adapt creadur webpages to contain the new logo.
> In addition to that links should be SSL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (RAT-211) Generated rat-output.xml must be well-formed, even if BinaryGuesser fails
Konstantin Kolinko created RAT-211: -- Summary: Generated rat-output.xml must be well-formed, even if BinaryGuesser fails Key: RAT-211 URL: https://issues.apache.org/jira/browse/RAT-211 Project: Apache Rat Issue Type: Bug Reporter: Konstantin Kolinko This issue was originally reported by Infrastructure team while running RAT over Apache Tomcat source code, see thread "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" tomcat.apache.org mailing list. (1) The issue: === 1. Buildbot at ASF is configured to run RAT tool over tomcat-trunk, tomcat-8, tomcat-7 source code. 2. Tomcat has *.bmp, *.dia files in its source code (images used by Windows installer, diagrams in documentation) that RAT failed to recognize as binary. 3. RAT generated rat-output.xml file that included header-sample fragments of those *.bmp and *.dia files. Those fragments are actually binary garbage. The result is that a broken XML file was generated. 4. XSLT transformation from rat-output.xml into rat-output.html failed. I have not seen the actual error printed by XSLT processor, but I confirmed that the file is broken by downloading rat-output.xml and opening it in Firefox. Firefox reported a syntax error. Workaround: === rat-excludes.txt file in Tomcat source code was updated to exclude **/*.bmp **/*.dia References: === 1. "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" tomcat.apache.org mailing list. http://markmail.org/message/rhrm54ch5omjalt4 2. Apache Tomcat links to Buildbot resuls: http://tomcat.apache.org/ci.html#Buildbot 3. Apache Tomcat source code http://tomcat.apache.org/svn.html Notes: - RAT excludes files in Tomcat source code are at res/rat/rat-excludes.txt - I know that Buildbot uses Ant to run RAT. The Ant project file for that is not in Tomcat sources, but in Infrastructure configuration (I do not have a link). It can be seen in "shell_5 RAT Report Complete" step during build run. E.g. here: https://ci.apache.org/builders/tomcat-trunk/builds/1061 - I do not know what version of RAT is used by that build slave on Buildbot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-211) Generated rat-output.xml must be well-formed, even if BinaryGuesser fails
[ https://issues.apache.org/jira/browse/RAT-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Kolinko updated RAT-211: --- Attachment: rat-output.xml rat-output.xml file containing broken header-sample Opening the file in Firefox reports that error is at line 3, symbol 40626: Look for > Generated rat-output.xml must be well-formed, even if BinaryGuesser fails > - > > Key: RAT-211 > URL: https://issues.apache.org/jira/browse/RAT-211 > Project: Apache Rat > Issue Type: Bug >Reporter: Konstantin Kolinko > Attachments: rat-output.xml > > > This issue was originally reported by Infrastructure team while running RAT > over Apache Tomcat source code, see thread > "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" > tomcat.apache.org mailing list. (1) > The issue: > === > 1. Buildbot at ASF is configured to run RAT tool over tomcat-trunk, tomcat-8, > tomcat-7 source code. > 2. Tomcat has *.bmp, *.dia files in its source code (images used by Windows > installer, diagrams in documentation) that RAT failed to recognize as binary. > 3. RAT generated rat-output.xml file that included header-sample fragments of > those *.bmp and *.dia files. Those fragments are actually binary garbage. > The result is that a broken XML file was generated. > 4. XSLT transformation from rat-output.xml into rat-output.html failed. > I have not seen the actual error printed by XSLT processor, but I confirmed > that the file is broken by downloading rat-output.xml and opening it in > Firefox. Firefox reported a syntax error. > Workaround: > === > rat-excludes.txt file in Tomcat source code was updated to exclude > **/*.bmp > **/*.dia > References: > === > 1. "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev > "at" tomcat.apache.org mailing list. > http://markmail.org/message/rhrm54ch5omjalt4 > 2. Apache Tomcat links to Buildbot resuls: > http://tomcat.apache.org/ci.html#Buildbot > 3. Apache Tomcat source code > http://tomcat.apache.org/svn.html > Notes: > - RAT excludes files in Tomcat source code are at > res/rat/rat-excludes.txt > - I know that Buildbot uses Ant to run RAT. The Ant project file for that is > not in Tomcat sources, but in Infrastructure configuration (I do not have a > link). It can be seen in "shell_5 RAT Report Complete" step during build run. > E.g. here: > https://ci.apache.org/builders/tomcat-trunk/builds/1061 > - I do not know what version of RAT is used by that build slave on Buildbot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (RAT-211) Generated rat-output.xml must be well-formed, even if BinaryGuesser fails
[ https://issues.apache.org/jira/browse/RAT-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148505#comment-15148505 ] Konstantin Kolinko edited comment on RAT-211 at 2/16/16 12:06 PM: -- rat-output.xml file containing broken header-sample Opening the file in Firefox reports that error is at line 3, symbol 40626: Look for This file contains fragment only from *.dia files, as the rat-excludes configuration has already been updated to exclude **/*.bmp ones. was (Author: kkolinko): rat-output.xml file containing broken header-sample Opening the file in Firefox reports that error is at line 3, symbol 40626: Look for > Generated rat-output.xml must be well-formed, even if BinaryGuesser fails > - > > Key: RAT-211 > URL: https://issues.apache.org/jira/browse/RAT-211 > Project: Apache Rat > Issue Type: Bug >Reporter: Konstantin Kolinko > Attachments: rat-output.xml > > > This issue was originally reported by Infrastructure team while running RAT > over Apache Tomcat source code, see thread > "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" > tomcat.apache.org mailing list. (1) > The issue: > === > 1. Buildbot at ASF is configured to run RAT tool over tomcat-trunk, tomcat-8, > tomcat-7 source code. > 2. Tomcat has *.bmp, *.dia files in its source code (images used by Windows > installer, diagrams in documentation) that RAT failed to recognize as binary. > 3. RAT generated rat-output.xml file that included header-sample fragments of > those *.bmp and *.dia files. Those fragments are actually binary garbage. > The result is that a broken XML file was generated. > 4. XSLT transformation from rat-output.xml into rat-output.html failed. > I have not seen the actual error printed by XSLT processor, but I confirmed > that the file is broken by downloading rat-output.xml and opening it in > Firefox. Firefox reported a syntax error. > Workaround: > === > rat-excludes.txt file in Tomcat source code was updated to exclude > **/*.bmp > **/*.dia > References: > === > 1. "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev > "at" tomcat.apache.org mailing list. > http://markmail.org/message/rhrm54ch5omjalt4 > 2. Apache Tomcat links to Buildbot resuls: > http://tomcat.apache.org/ci.html#Buildbot > 3. Apache Tomcat source code > http://tomcat.apache.org/svn.html > Notes: > - RAT excludes files in Tomcat source code are at > res/rat/rat-excludes.txt > - I know that Buildbot uses Ant to run RAT. The Ant project file for that is > not in Tomcat sources, but in Infrastructure configuration (I do not have a > link). It can be seen in "shell_5 RAT Report Complete" step during build run. > E.g. here: > https://ci.apache.org/builders/tomcat-trunk/builds/1061 > - I do not know what version of RAT is used by that build slave on Buildbot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (RAT-211) Generated rat-output.xml must be well-formed, even if BinaryGuesser fails
[ https://issues.apache.org/jira/browse/RAT-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148505#comment-15148505 ] Konstantin Kolinko edited comment on RAT-211 at 2/16/16 12:07 PM: -- rat-output.xml file containing broken header-sample Opening the file in Firefox reports that error is at line 3, symbol 40626: Look for This file contains fragment only from `\*.dia` files, as the rat-excludes configuration has already been updated to exclude `\*\*/\*.bmp` ones. was (Author: kkolinko): rat-output.xml file containing broken header-sample Opening the file in Firefox reports that error is at line 3, symbol 40626: Look for This file contains fragment only from *.dia files, as the rat-excludes configuration has already been updated to exclude **/*.bmp ones. > Generated rat-output.xml must be well-formed, even if BinaryGuesser fails > - > > Key: RAT-211 > URL: https://issues.apache.org/jira/browse/RAT-211 > Project: Apache Rat > Issue Type: Bug >Reporter: Konstantin Kolinko > Attachments: rat-output.xml > > > This issue was originally reported by Infrastructure team while running RAT > over Apache Tomcat source code, see thread > "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" > tomcat.apache.org mailing list. (1) > The issue: > === > 1. Buildbot at ASF is configured to run RAT tool over tomcat-trunk, tomcat-8, > tomcat-7 source code. > 2. Tomcat has *.bmp, *.dia files in its source code (images used by Windows > installer, diagrams in documentation) that RAT failed to recognize as binary. > 3. RAT generated rat-output.xml file that included header-sample fragments of > those *.bmp and *.dia files. Those fragments are actually binary garbage. > The result is that a broken XML file was generated. > 4. XSLT transformation from rat-output.xml into rat-output.html failed. > I have not seen the actual error printed by XSLT processor, but I confirmed > that the file is broken by downloading rat-output.xml and opening it in > Firefox. Firefox reported a syntax error. > Workaround: > === > rat-excludes.txt file in Tomcat source code was updated to exclude > **/*.bmp > **/*.dia > References: > === > 1. "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev > "at" tomcat.apache.org mailing list. > http://markmail.org/message/rhrm54ch5omjalt4 > 2. Apache Tomcat links to Buildbot resuls: > http://tomcat.apache.org/ci.html#Buildbot > 3. Apache Tomcat source code > http://tomcat.apache.org/svn.html > Notes: > - RAT excludes files in Tomcat source code are at > res/rat/rat-excludes.txt > - I know that Buildbot uses Ant to run RAT. The Ant project file for that is > not in Tomcat sources, but in Infrastructure configuration (I do not have a > link). It can be seen in "shell_5 RAT Report Complete" step during build run. > E.g. here: > https://ci.apache.org/builders/tomcat-trunk/builds/1061 > - I do not know what version of RAT is used by that build slave on Buildbot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-211) Generated rat-output.xml must be well-formed, even if BinaryGuesser fails
[ https://issues.apache.org/jira/browse/RAT-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Kolinko updated RAT-211: --- Description: This issue was originally reported by Infrastructure team while running RAT over Apache Tomcat source code, see thread "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" tomcat.apache.org mailing list. (1) The issue: === 1. Buildbot at ASF is configured to run RAT tool over tomcat-trunk, tomcat-8, tomcat-7 source code. 2. Tomcat has \*.bmp, \*.dia files in its source code (images used by Windows installer, diagrams in documentation) that RAT failed to recognize as binary. 3. RAT generated rat-output.xml file that included header-sample fragments of those *.bmp and *.dia files. Those fragments are actually binary garbage. The result is that a broken XML file was generated. 4. XSLT transformation from rat-output.xml into rat-output.html failed. I have not seen the actual error printed by XSLT processor, but I confirmed that the file is broken by downloading rat-output.xml and opening it in Firefox. Firefox reported a syntax error. Workaround: === rat-excludes.txt file in Tomcat source code was updated to exclude \*\*/\*.bmp \*\*/\*.dia References: === 1. "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" tomcat.apache.org mailing list. http://markmail.org/message/rhrm54ch5omjalt4 2. Apache Tomcat links to Buildbot resuls: http://tomcat.apache.org/ci.html#Buildbot 3. Apache Tomcat source code http://tomcat.apache.org/svn.html Notes: - RAT excludes files in Tomcat source code are at res/rat/rat-excludes.txt - I know that Buildbot uses Ant to run RAT. The Ant project file for that is not in Tomcat sources, but in Infrastructure configuration (I do not have a link). It can be seen in "shell_5 RAT Report Complete" step during build run. E.g. here: https://ci.apache.org/builders/tomcat-trunk/builds/1061 - I do not know what version of RAT is used by that build slave on Buildbot. was: This issue was originally reported by Infrastructure team while running RAT over Apache Tomcat source code, see thread "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" tomcat.apache.org mailing list. (1) The issue: === 1. Buildbot at ASF is configured to run RAT tool over tomcat-trunk, tomcat-8, tomcat-7 source code. 2. Tomcat has *.bmp, *.dia files in its source code (images used by Windows installer, diagrams in documentation) that RAT failed to recognize as binary. 3. RAT generated rat-output.xml file that included header-sample fragments of those *.bmp and *.dia files. Those fragments are actually binary garbage. The result is that a broken XML file was generated. 4. XSLT transformation from rat-output.xml into rat-output.html failed. I have not seen the actual error printed by XSLT processor, but I confirmed that the file is broken by downloading rat-output.xml and opening it in Firefox. Firefox reported a syntax error. Workaround: === rat-excludes.txt file in Tomcat source code was updated to exclude **/*.bmp **/*.dia References: === 1. "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" tomcat.apache.org mailing list. http://markmail.org/message/rhrm54ch5omjalt4 2. Apache Tomcat links to Buildbot resuls: http://tomcat.apache.org/ci.html#Buildbot 3. Apache Tomcat source code http://tomcat.apache.org/svn.html Notes: - RAT excludes files in Tomcat source code are at res/rat/rat-excludes.txt - I know that Buildbot uses Ant to run RAT. The Ant project file for that is not in Tomcat sources, but in Infrastructure configuration (I do not have a link). It can be seen in "shell_5 RAT Report Complete" step during build run. E.g. here: https://ci.apache.org/builders/tomcat-trunk/builds/1061 - I do not know what version of RAT is used by that build slave on Buildbot. > Generated rat-output.xml must be well-formed, even if BinaryGuesser fails > ----- > > Key: RAT-211 > URL: https://issues.apache.org/jira/browse/RAT-211 > Project: Apache Rat > Issue Type: Bug >Reporter: Konstantin Kolinko > Attachments: rat-output.xml > > > This issue was originally reported by Infrastructure team while running RAT > over Apache Tomcat source code, see thread > "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" > tomcat.apache.org mailing list. (1) > The issue: > === > 1. Buildbot at ASF is configured to run RAT tool over tomcat-trunk, tomcat-8, > tomcat-7 source code. > 2. Tomcat has \*.bmp,
[jira] [Commented] (RAT-211) Generated rat-output.xml must be well-formed, even if BinaryGuesser fails
[ https://issues.apache.org/jira/browse/RAT-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148531#comment-15148531 ] Jochen Wiedmann commented on RAT-211: - Quoting the relevant part: Binary Trash > Generated rat-output.xml must be well-formed, even if BinaryGuesser fails > - > > Key: RAT-211 > URL: https://issues.apache.org/jira/browse/RAT-211 > Project: Apache Rat > Issue Type: Bug >Reporter: Konstantin Kolinko > Attachments: rat-output.xml > > > This issue was originally reported by Infrastructure team while running RAT > over Apache Tomcat source code, see thread > "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev "at" > tomcat.apache.org mailing list. (1) > The issue: > === > 1. Buildbot at ASF is configured to run RAT tool over tomcat-trunk, tomcat-8, > tomcat-7 source code. > 2. Tomcat has \*.bmp, \*.dia files in its source code (images used by Windows > installer, diagrams in documentation) that RAT failed to recognize as binary. > 3. RAT generated rat-output.xml file that included header-sample fragments of > those *.bmp and *.dia files. Those fragments are actually binary garbage. > The result is that a broken XML file was generated. > 4. XSLT transformation from rat-output.xml into rat-output.html failed. > I have not seen the actual error printed by XSLT processor, but I confirmed > that the file is broken by downloading rat-output.xml and opening it in > Firefox. Firefox reported a syntax error. > Workaround: > === > rat-excludes.txt file in Tomcat source code was updated to exclude > \*\*/\*.bmp > \*\*/\*.dia > References: > === > 1. "Files to exclude from buildbot rat tests" (started 2016-02-15) at dev > "at" tomcat.apache.org mailing list. > http://markmail.org/message/rhrm54ch5omjalt4 > 2. Apache Tomcat links to Buildbot resuls: > http://tomcat.apache.org/ci.html#Buildbot > 3. Apache Tomcat source code > http://tomcat.apache.org/svn.html > Notes: > - RAT excludes files in Tomcat source code are at > res/rat/rat-excludes.txt > - I know that Buildbot uses Ant to run RAT. The Ant project file for that is > not in Tomcat sources, but in Infrastructure configuration (I do not have a > link). It can be seen in "shell_5 RAT Report Complete" step during build run. > E.g. here: > https://ci.apache.org/builders/tomcat-trunk/builds/1061 > - I do not know what version of RAT is used by that build slave on Buildbot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-158) SAXParser warnings
[
https://issues.apache.org/jira/browse/RAT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159133#comment-15159133
]
Christopher Tubbs commented on RAT-158:
---
It appears that DOXIA-526 removed the xerces dependency in 1.7 (which is now
released).
RAT 0.12 should update to use doxia-core:1.7
MPOM should update to use RAT 0.12
> 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}
> org.apache.rat
> apache-rat-plugin
> false
>
>
> verify
>
>check
>
>
>
>
>
> **/conf/**
>
>
>
> {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)
[jira] [Created] (RAT-212) pom.xml license failure when url is https
Christopher Tubbs created RAT-212: - Summary: pom.xml license failure when url is https Key: RAT-212 URL: https://issues.apache.org/jira/browse/RAT-212 Project: Apache Rat Issue Type: Bug Affects Versions: 0.11 Reporter: Christopher Tubbs apache-rat-plugin:check fails when the license information in the POM has a url of "https://www.apache.org/licenses/LICENSE-2.0";, but not when it has a url of "http://www.apache.org/licenses/LICENSE-2.0"; It should probably not fail in the case of https. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-212) pom.xml license failure when url is https
[
https://issues.apache.org/jira/browse/RAT-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159506#comment-15159506
]
Christopher Tubbs commented on RAT-212:
---
Example failure:
{code:xml}
Apache License, Version 2.0
https://www.apache.org/licenses/LICENSE-2.0
repo
{code}
Example success:
{code:xml}
Apache License, Version 2.0
http://www.apache.org/licenses/LICENSE-2.0
repo
{code}
> pom.xml license failure when url is https
> -
>
> Key: RAT-212
> URL: https://issues.apache.org/jira/browse/RAT-212
> Project: Apache Rat
> Issue Type: Bug
>Affects Versions: 0.11
>Reporter: Christopher Tubbs
>
> apache-rat-plugin:check fails when the license information in the POM has a
> url of "https://www.apache.org/licenses/LICENSE-2.0";, but not when it has a
> url of "http://www.apache.org/licenses/LICENSE-2.0";
> It should probably not fail in the case of https.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (RAT-158) SAXParser warnings
[
https://issues.apache.org/jira/browse/RAT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger reassigned RAT-158:
-
Assignee: Philipp Ottlinger
> 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
>Assignee: Philipp Ottlinger
>Priority: Minor
> Fix For: 0.12
>
> Attachments: RAT-158-2.patch, RAT-158.patch
>
>
> I have rat configured as such
> {code}
> org.apache.rat
> apache-rat-plugin
> false
>
>
> verify
>
>check
>
>
>
>
>
> **/conf/**
>
>
>
> {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)
[jira] [Commented] (RAT-212) pom.xml license failure when url is https
[
https://issues.apache.org/jira/browse/RAT-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159720#comment-15159720
]
Philipp Ottlinger commented on RAT-212:
---
Thanks for your report - since RAT scans for license snippets you may use the
following workaround:
* keep https in your pom url-structure
* add a valid license header to your pom.xml such as:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
{code}
This solves the issue.
I was not aware that we perform a scan of the pom's structure. I always thought
we parse for a license snippet instead
> pom.xml license failure when url is https
> -
>
> Key: RAT-212
> URL: https://issues.apache.org/jira/browse/RAT-212
> Project: Apache Rat
> Issue Type: Bug
>Affects Versions: 0.11
>Reporter: Christopher Tubbs
>
> apache-rat-plugin:check fails when the license information in the POM has a
> url of "https://www.apache.org/licenses/LICENSE-2.0";, but not when it has a
> url of "http://www.apache.org/licenses/LICENSE-2.0";
> It should probably not fail in the case of https.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (RAT-158) SAXParser warnings
[
https://issues.apache.org/jira/browse/RAT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159749#comment-15159749
]
Philipp Ottlinger commented on RAT-158:
---
Thanks for the update - newer versions seem use a JDK that is too new for RAT
:-(
{code}
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-bytecode-version) @
apache-rat-plugin ---
[INFO] Artifact org.apache.maven.doxia:doxia-core:jar:1.7:compile contains
.class compiled with incorrect version
[INFO] Artifact org.apache.maven.doxia:doxia-logging-api:jar:1.7:compile
contains .class compiled with incorrect version
[INFO] Artifact org.apache.maven.doxia:doxia-sink-api:jar:1.7:compile contains
.class compiled with incorrect version
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion
failed with message:
Found Banned Dependency: org.apache.maven.doxia:doxia-core:jar:1.7
Found Banned Dependency: org.apache.maven.doxia:doxia-logging-api:jar:1.7
Found Banned Dependency: org.apache.maven.doxia:doxia-sink-api:jar:1.7
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
{code}
Until that decision is changed we cannot switch over to the new version.
Verified with the following changes
{code}
Index: apache-rat-plugin/pom.xml
===
--- apache-rat-plugin/pom.xml (Revision 1731969)
+++ apache-rat-plugin/pom.xml (Arbeitskopie)
@@ -33,7 +33,7 @@
${project.version}
-1.6
+1.7
1.6
Index: pom.xml
===
--- pom.xml (Revision 1731969)
+++ pom.xml (Arbeitskopie)
@@ -329,17 +329,11 @@
apache-rat-plugin
${previousRatVersion}
-
+
org.apache.maven.doxia
doxia-core
- 1.2
-
-
- xerces
- xercesImpl
-
-
+ 1.7
{code}
and
{code}
mvn clean install site:site
{code}
> 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
>Assignee: Philipp Ottlinger
>Priority: Minor
> Fix For: 0.12
>
> Attachments: RAT-158-2.patch, RAT-158.patch
>
>
> I have rat configured as such
> {code}
> org.apache.rat
> apache-rat-plugin
> false
>
>
> verify
>
>check
>
>
>
>
>
> **/conf/**
>
>
>
> {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)
[jira] [Updated] (RAT-158) SAXParser warnings
[
https://issues.apache.org/jira/browse/RAT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger updated RAT-158:
--
Assignee: (was: Philipp Ottlinger)
> 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}
> org.apache.rat
> apache-rat-plugin
> false
>
>
> verify
>
>check
>
>
>
>
>
> **/conf/**
>
>
>
> {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)
[jira] [Assigned] (RAT-158) SAXParser warnings
[
https://issues.apache.org/jira/browse/RAT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger reassigned RAT-158:
-
Assignee: Philipp Ottlinger
> 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
>Assignee: Philipp Ottlinger
>Priority: Minor
> Fix For: 0.12
>
> Attachments: RAT-158-2.patch, RAT-158.patch
>
>
> I have rat configured as such
> {code}
> org.apache.rat
> apache-rat-plugin
> false
>
>
> verify
>
>check
>
>
>
>
>
> **/conf/**
>
>
>
> {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)
[jira] [Updated] (RAT-158) SAXParser warnings
[
https://issues.apache.org/jira/browse/RAT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger updated RAT-158:
--
Assignee: (was: Philipp Ottlinger)
> 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}
> org.apache.rat
> apache-rat-plugin
> false
>
>
> verify
>
>check
>
>
>
>
>
> **/conf/**
>
>
>
> {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)
[jira] [Commented] (RAT-158) SAXParser warnings
[
https://issues.apache.org/jira/browse/RAT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159763#comment-15159763
]
Christopher Tubbs commented on RAT-158:
---
:(
> 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}
> org.apache.rat
> apache-rat-plugin
> false
>
>
> verify
>
>check
>
>
>
>
>
> **/conf/**
>
>
>
> {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)
[jira] [Commented] (RAT-212) pom.xml license failure when url is https
[ https://issues.apache.org/jira/browse/RAT-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159769#comment-15159769 ] Christopher Tubbs commented on RAT-212: --- Perhaps the parsing of the license snippet is also sensitive to http vs. https? I haven't tried. I only happened to notice this issue on an external (non-ASF) POM which uses the apache-rat-plugin. > pom.xml license failure when url is https > - > > Key: RAT-212 > URL: https://issues.apache.org/jira/browse/RAT-212 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.11 >Reporter: Christopher Tubbs > > apache-rat-plugin:check fails when the license information in the POM has a > url of "https://www.apache.org/licenses/LICENSE-2.0";, but not when it has a > url of "http://www.apache.org/licenses/LICENSE-2.0"; > It should probably not fail in the case of https. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RAT-213) Upgrade Apache Commons Collections to v3.2.2
Philipp Ottlinger created RAT-213: - Summary: Upgrade Apache Commons Collections to v3.2.2 Key: RAT-213 URL: https://issues.apache.org/jira/browse/RAT-213 Project: Apache Rat Issue Type: Bug Affects Versions: 0.11 Reporter: Philipp Ottlinger Assignee: Philipp Ottlinger Fix For: 0.12 Upgrade as requested with the Git PR. Thanks to https://github.com/gmlewis Glenn Lewis -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-213) Upgrade Apache Commons Collections to v3.2.2
[ https://issues.apache.org/jira/browse/RAT-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-213: -- Issue Type: Improvement (was: Bug) > Upgrade Apache Commons Collections to v3.2.2 > > > Key: RAT-213 > URL: https://issues.apache.org/jira/browse/RAT-213 > Project: Apache Rat > Issue Type: Improvement >Affects Versions: 0.11 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.12 > > > Upgrade as requested with the Git PR. > Thanks to https://github.com/gmlewis Glenn Lewis -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-213) Upgrade Apache Commons Collections to v3.2.2
[
https://issues.apache.org/jira/browse/RAT-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger resolved RAT-213.
---
Resolution: Fixed
{code}
URL: http://svn.apache.org/viewvc?rev=1734360&view=rev
Log:
RAT-213: Upgrade to commons-collections 3.2.2
Modified:
creadur/rat/trunk/RELEASE_NOTES.txt
creadur/rat/trunk/pom.xml
creadur/rat/trunk/src/changes/changes.xml
{code}
> Upgrade Apache Commons Collections to v3.2.2
>
>
> Key: RAT-213
> URL: https://issues.apache.org/jira/browse/RAT-213
> Project: Apache Rat
> Issue Type: Improvement
>Affects Versions: 0.11
>Reporter: Philipp Ottlinger
>Assignee: Philipp Ottlinger
> Fix For: 0.12
>
>
> Upgrade as requested with the Git PR.
> Thanks to https://github.com/gmlewis Glenn Lewis
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (RAT-213) Upgrade Apache Commons Collections to v3.2.2
[ https://issues.apache.org/jira/browse/RAT-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger closed RAT-213. - > Upgrade Apache Commons Collections to v3.2.2 > > > Key: RAT-213 > URL: https://issues.apache.org/jira/browse/RAT-213 > Project: Apache Rat > Issue Type: Improvement >Affects Versions: 0.11 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.12 > > > Upgrade as requested with the Git PR. > Thanks to https://github.com/gmlewis Glenn Lewis > h3. Context > Version 3.2.1 has a CVSS 10.0 vulnerability. That is the worst kind of > vulnerability that exists. By merely existing on the classpath, this > library causes the Java serialization parser for the entire JVM process > to go from being a state machine to a turing machine. A turing machine > with an exec() function! > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103 > https://commons.apache.org/proper/commons-collections/security-reports.html > http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-213) Upgrade Apache Commons Collections to v3.2.2
[ https://issues.apache.org/jira/browse/RAT-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-213: -- Description: Upgrade as requested with the Git PR. Thanks to https://github.com/gmlewis Glenn Lewis h3. Context Version 3.2.1 has a CVSS 10.0 vulnerability. That is the worst kind of vulnerability that exists. By merely existing on the classpath, this library causes the Java serialization parser for the entire JVM process to go from being a state machine to a turing machine. A turing machine with an exec() function! https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103 https://commons.apache.org/proper/commons-collections/security-reports.html http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/ was: Upgrade as requested with the Git PR. Thanks to https://github.com/gmlewis Glenn Lewis > Upgrade Apache Commons Collections to v3.2.2 > > > Key: RAT-213 > URL: https://issues.apache.org/jira/browse/RAT-213 > Project: Apache Rat > Issue Type: Improvement >Affects Versions: 0.11 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.12 > > > Upgrade as requested with the Git PR. > Thanks to https://github.com/gmlewis Glenn Lewis > h3. Context > Version 3.2.1 has a CVSS 10.0 vulnerability. That is the worst kind of > vulnerability that exists. By merely existing on the classpath, this > library causes the Java serialization parser for the entire JVM process > to go from being a state machine to a turing machine. A turing machine > with an exec() function! > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103 > https://commons.apache.org/proper/commons-collections/security-reports.html > http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (WHISKER-15) Upgrade Apache Commons Collections to v3.2.2
Philipp Ottlinger created WHISKER-15: Summary: Upgrade Apache Commons Collections to v3.2.2 Key: WHISKER-15 URL: https://issues.apache.org/jira/browse/WHISKER-15 Project: Apache Whisker Issue Type: Improvement Affects Versions: 0.2 Reporter: Philipp Ottlinger Assignee: Philipp Ottlinger Fix For: 0.2 Motivated by RAT-213 we should upgrade Whisker as well. Tentacles does not seem to use commons-collections as of now. h3. Context Version 3.2.1 has a CVSS 10.0 vulnerability. That is the worst kind of vulnerability that exists. By merely existing on the classpath, this library causes the Java serialization parser for the entire JVM process to go from being a state machine to a turing machine. A turing machine with an exec() function! https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103 https://commons.apache.org/proper/commons-collections/security-reports.html http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (WHISKER-15) Upgrade Apache Commons Collections to v3.2.2
[ https://issues.apache.org/jira/browse/WHISKER-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger resolved WHISKER-15. -- Resolution: Fixed URL: http://svn.apache.org/viewvc?rev=1734853&view=rev DONE > Upgrade Apache Commons Collections to v3.2.2 > > > Key: WHISKER-15 > URL: https://issues.apache.org/jira/browse/WHISKER-15 > Project: Apache Whisker > Issue Type: Improvement >Affects Versions: 0.2 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.2 > > > Motivated by RAT-213 we should upgrade Whisker as well. > Tentacles does not seem to use commons-collections as of now. > h3. Context > Version 3.2.1 has a CVSS 10.0 vulnerability. That is the worst kind of > vulnerability that exists. By merely existing on the classpath, this > library causes the Java serialization parser for the entire JVM process > to go from being a state machine to a turing machine. A turing machine > with an exec() function! > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103 > https://commons.apache.org/proper/commons-collections/security-reports.html > http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (WHISKER-15) Upgrade Apache Commons Collections to v3.2.2
[ https://issues.apache.org/jira/browse/WHISKER-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger closed WHISKER-15. Jenkins builds are ok, too. > Upgrade Apache Commons Collections to v3.2.2 > > > Key: WHISKER-15 > URL: https://issues.apache.org/jira/browse/WHISKER-15 > Project: Apache Whisker > Issue Type: Improvement >Affects Versions: 0.2 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.2 > > > Motivated by RAT-213 we should upgrade Whisker as well. > Tentacles does not seem to use commons-collections as of now. > h3. Context > Version 3.2.1 has a CVSS 10.0 vulnerability. That is the worst kind of > vulnerability that exists. By merely existing on the classpath, this > library causes the Java serialization parser for the entire JVM process > to go from being a state machine to a turing machine. A turing machine > with an exec() function! > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103 > https://commons.apache.org/proper/commons-collections/security-reports.html > http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RAT-214) Update commons-compress and apache-ant due to security problems
Philipp Ottlinger created RAT-214: - Summary: Update commons-compress and apache-ant due to security problems Key: RAT-214 URL: https://issues.apache.org/jira/browse/RAT-214 Project: Apache Rat Issue Type: Bug Affects Versions: 0.11 Reporter: Philipp Ottlinger Assignee: Philipp Ottlinger Fix For: 0.12 Try to update * commons-compress * apache-ant due to possible security problems. h3. Context Algorithmic complexity vulnerability in the sorting algorithms in bzip2 compressing stream (BZip2CompressorOutputStream) in Apache Commons Compress before 1.4.1 and Apache Ant before 1.8.4 allows remote attackers to cause a denial of service (CPU consumption) via a file with many repeating inputs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-214) Update commons-compress and apache-ant due to security problems
[ https://issues.apache.org/jira/browse/RAT-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger resolved RAT-214. --- Resolution: Fixed applied updates via URL: http://svn.apache.org/viewvc?rev=1734995&view=rev * ANT: 1.7.1 -> 1.9.6 * COMPRESS: 1.5 -> 1.10 > Update commons-compress and apache-ant due to security problems > --- > > Key: RAT-214 > URL: https://issues.apache.org/jira/browse/RAT-214 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.11 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.12 > > > Try to update > * commons-compress > * apache-ant > due to possible security problems. > h3. Context > Algorithmic complexity vulnerability in the sorting algorithms in > bzip2 compressing stream (BZip2CompressorOutputStream) in Apache Commons > Compress before 1.4.1 and Apache Ant before 1.8.4 allows remote > attackers to cause a denial of service (CPU consumption) via a file with > many repeating inputs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (RAT-214) Update commons-compress and apache-ant due to security problems
[ https://issues.apache.org/jira/browse/RAT-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger closed RAT-214. - CI builds were fine. > Update commons-compress and apache-ant due to security problems > --- > > Key: RAT-214 > URL: https://issues.apache.org/jira/browse/RAT-214 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.11 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.12 > > > Try to update > * commons-compress > * apache-ant > due to possible security problems. > h3. Context > Algorithmic complexity vulnerability in the sorting algorithms in > bzip2 compressing stream (BZip2CompressorOutputStream) in Apache Commons > Compress before 1.4.1 and Apache Ant before 1.8.4 allows remote > attackers to cause a denial of service (CPU consumption) via a file with > many repeating inputs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-215) BinaryGuesser should treat *.woff2 as binary
[
https://issues.apache.org/jira/browse/RAT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger updated RAT-215:
--
Fix Version/s: 0.12
> BinaryGuesser should treat *.woff2 as binary
>
>
> Key: RAT-215
> URL: https://issues.apache.org/jira/browse/RAT-215
> Project: Apache Rat
> Issue Type: Bug
>Affects Versions: 0.11
>Reporter: Robert Munteanu
>Assignee: Philipp Ottlinger
> Fix For: 0.12
>
>
> WOFF2 files are fonts and should not be checked for licenses.
> We recently hit this in the Apache Sling builds, where the failure output
> (trimmed) is:
> {noformat}
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.ttf
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.eot
> !?
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff2{noformat}
> I guess {{woff2}} should be added to the list of known binary formats as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (RAT-215) BinaryGuesser should treat *.woff2 as binary
[
https://issues.apache.org/jira/browse/RAT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger reassigned RAT-215:
-
Assignee: Philipp Ottlinger
> BinaryGuesser should treat *.woff2 as binary
>
>
> Key: RAT-215
> URL: https://issues.apache.org/jira/browse/RAT-215
> Project: Apache Rat
> Issue Type: Bug
>Affects Versions: 0.11
>Reporter: Robert Munteanu
>Assignee: Philipp Ottlinger
> Fix For: 0.12
>
>
> WOFF2 files are fonts and should not be checked for licenses.
> We recently hit this in the Apache Sling builds, where the failure output
> (trimmed) is:
> {noformat}
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.ttf
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.eot
> !?
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff2{noformat}
> I guess {{woff2}} should be added to the list of known binary formats as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (RAT-215) BinaryGuesser should treat *.woff2 as binary
Robert Munteanu created RAT-215:
---
Summary: BinaryGuesser should treat *.woff2 as binary
Key: RAT-215
URL: https://issues.apache.org/jira/browse/RAT-215
Project: Apache Rat
Issue Type: Bug
Affects Versions: 0.11
Reporter: Robert Munteanu
WOFF2 files are fonts and should not be checked for licenses.
We recently hit this in the Apache Sling builds, where the failure output
(trimmed) is:
{noformat}
B
/home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.ttf
B
/home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff
B
/home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.eot
!?
/home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff2{noformat}
I guess {{woff2}} should be added to the list of known binary formats as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (RAT-215) BinaryGuesser should treat *.woff2 as binary
[
https://issues.apache.org/jira/browse/RAT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger resolved RAT-215.
---
Resolution: Fixed
Thanks for your bug report - I've added the font extensions to the list of
"binary by default" files. This should speed up the scanning because the files
are not digested.
Feel free to retest with 0.12-SNAPSHOT and close the bug.
{code}
New Revision: 1735829
URL: http://svn.apache.org/viewvc?rev=1735829&view=rev
{code}
> BinaryGuesser should treat *.woff2 as binary
>
>
> Key: RAT-215
> URL: https://issues.apache.org/jira/browse/RAT-215
> Project: Apache Rat
> Issue Type: Bug
>Affects Versions: 0.11
>Reporter: Robert Munteanu
>Assignee: Philipp Ottlinger
> Fix For: 0.12
>
>
> WOFF2 files are fonts and should not be checked for licenses.
> We recently hit this in the Apache Sling builds, where the failure output
> (trimmed) is:
> {noformat}
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.ttf
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.eot
> !?
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff2{noformat}
> I guess {{woff2}} should be added to the list of known binary formats as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (RAT-215) BinaryGuesser should treat *.woff2 as binary
[
https://issues.apache.org/jira/browse/RAT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206114#comment-15206114
]
Robert Munteanu commented on RAT-215:
-
I was unable to verify the problem only appears on builds.apache.org, and the
SNAPSHOT version does not appear to be deployed on repository.apache.org .
I tried a few {{-Dfile.encoding}} values but that did not help. Can you either
suggest what file encodings to try to reproduce the problem with the 0.11.0
version or deploy a snapshot with the fix to repository.apache.org ? Thanks
> BinaryGuesser should treat *.woff2 as binary
>
>
> Key: RAT-215
> URL: https://issues.apache.org/jira/browse/RAT-215
> Project: Apache Rat
> Issue Type: Bug
>Affects Versions: 0.11
>Reporter: Robert Munteanu
>Assignee: Philipp Ottlinger
> Fix For: 0.12
>
>
> WOFF2 files are fonts and should not be checked for licenses.
> We recently hit this in the Apache Sling builds, where the failure output
> (trimmed) is:
> {noformat}
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.ttf
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff
> B
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.eot
> !?
> /home/jenkins/jenkins-slave/workspace/sling-samples-1.7/trunk/slingshot/src/main/resources/SLING-INF/content/slingshot/resources/fonts/glyphicons-halflings-regular.woff2{noformat}
> I guess {{woff2}} should be added to the list of known binary formats as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (WHISKER-16) Publish Cli tool
Evan Hughes created WHISKER-16: -- Summary: Publish Cli tool Key: WHISKER-16 URL: https://issues.apache.org/jira/browse/WHISKER-16 Project: Apache Whisker Issue Type: Wish Reporter: Evan Hughes Priority: Minor Just wondering if the developers would be able to publish the cli version of whisker. ~ Evan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (WHISKER-16) Publish Cli tool
[ https://issues.apache.org/jira/browse/WHISKER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264497#comment-15264497 ] Philipp Ottlinger commented on WHISKER-16: -- [~wisebaldone] do you just need a release version of whisker or some more features in the CLI version of the current SNAPSHOT? Thanks. > Publish Cli tool > > > Key: WHISKER-16 > URL: https://issues.apache.org/jira/browse/WHISKER-16 > Project: Apache Whisker > Issue Type: Wish >Reporter: Evan Hughes >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > Just wondering if the developers would be able to publish the cli version of > whisker. > ~ Evan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (WHISKER-16) Publish Cli tool
[ https://issues.apache.org/jira/browse/WHISKER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265096#comment-15265096 ] Evan Hughes commented on WHISKER-16: Release version, I hadn't been able to find somewhere to download the pre-built jar like I can for RAT. Essentially so I can make a build extension for the bazel build tool like I've done for RAT https://github.com/apache/incubator-wave/blob/wavy/rat.bzl . > Publish Cli tool > > > Key: WHISKER-16 > URL: https://issues.apache.org/jira/browse/WHISKER-16 > Project: Apache Whisker > Issue Type: Wish >Reporter: Evan Hughes >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > Just wondering if the developers would be able to publish the cli version of > whisker. > ~ Evan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (WHISKER-16) Publish Cli tool
[ https://issues.apache.org/jira/browse/WHISKER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265474#comment-15265474 ] Philipp Ottlinger commented on WHISKER-16: -- mmmh - I just checked and verified the build jobs. Whisker is built in the same way as RAT, which has SNAPSHOT versions available. > Publish Cli tool > > > Key: WHISKER-16 > URL: https://issues.apache.org/jira/browse/WHISKER-16 > Project: Apache Whisker > Issue Type: Wish >Reporter: Evan Hughes >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > Just wondering if the developers would be able to publish the cli version of > whisker. > ~ Evan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (WHISKER-16) Publish Cli tool
[ https://issues.apache.org/jira/browse/WHISKER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265474#comment-15265474 ] Philipp Ottlinger edited comment on WHISKER-16 at 4/30/16 8:32 PM: --- mmmh - I just checked and verified the build jobs. Whisker is built in the same way as RAT, which has SNAPSHOT versions available. Are you using the correct SNAPSHOT repository? https://repository.apache.org/content/groups/snapshots-group/org/apache/creadur/whisker/apache-whisker-cli/0.2-SNAPSHOT/ Example configuration can be found here: https://tomcat.apache.org/maven-plugin-2.0-beta-1/snapshot-test.html Is that of any help to you? was (Author: hugo.hirsch): mmmh - I just checked and verified the build jobs. Whisker is built in the same way as RAT, which has SNAPSHOT versions available. > Publish Cli tool > > > Key: WHISKER-16 > URL: https://issues.apache.org/jira/browse/WHISKER-16 > Project: Apache Whisker > Issue Type: Wish >Reporter: Evan Hughes >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > Just wondering if the developers would be able to publish the cli version of > whisker. > ~ Evan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (WHISKER-16) Publish Cli tool
[ https://issues.apache.org/jira/browse/WHISKER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265763#comment-15265763 ] Evan Hughes commented on WHISKER-16: ahh yes thankyou very much > Publish Cli tool > > > Key: WHISKER-16 > URL: https://issues.apache.org/jira/browse/WHISKER-16 > Project: Apache Whisker > Issue Type: Wish >Reporter: Evan Hughes >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > Just wondering if the developers would be able to publish the cli version of > whisker. > ~ Evan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (WHISKER-16) Publish Cli tool
[ https://issues.apache.org/jira/browse/WHISKER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Hughes resolved WHISKER-16. Resolution: Fixed > Publish Cli tool > > > Key: WHISKER-16 > URL: https://issues.apache.org/jira/browse/WHISKER-16 > Project: Apache Whisker > Issue Type: Wish >Reporter: Evan Hughes >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > Just wondering if the developers would be able to publish the cli version of > whisker. > ~ Evan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (WHISKER-16) Publish Cli tool
[ https://issues.apache.org/jira/browse/WHISKER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265781#comment-15265781 ] Evan Hughes commented on WHISKER-16: On a side note is the CLI able to gen NOTICE files, seems to only make LICENSE. > Publish Cli tool > > > Key: WHISKER-16 > URL: https://issues.apache.org/jira/browse/WHISKER-16 > Project: Apache Whisker > Issue Type: Wish >Reporter: Evan Hughes >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > Just wondering if the developers would be able to publish the cli version of > whisker. > ~ Evan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-212) pom.xml license failure when url is https
[ https://issues.apache.org/jira/browse/RAT-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381217#comment-15381217 ] Philipp Ottlinger commented on RAT-212: --- [~ctubbsii] if you get an okay from the legal team that a https-variant of the header is still licence-compliant we could easily add a workaround for your issue. > pom.xml license failure when url is https > - > > Key: RAT-212 > URL: https://issues.apache.org/jira/browse/RAT-212 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.11 >Reporter: Christopher Tubbs > > apache-rat-plugin:check fails when the license information in the POM has a > url of "https://www.apache.org/licenses/LICENSE-2.0";, but not when it has a > url of "http://www.apache.org/licenses/LICENSE-2.0"; > It should probably not fail in the case of https. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-212) pom.xml license failure when url is https
[ https://issues.apache.org/jira/browse/RAT-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381322#comment-15381322 ] Christopher Tubbs commented on RAT-212: --- No problem, LEGAL-265 is the blocking issue. > pom.xml license failure when url is https > - > > Key: RAT-212 > URL: https://issues.apache.org/jira/browse/RAT-212 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.11 >Reporter: Christopher Tubbs > > apache-rat-plugin:check fails when the license information in the POM has a > url of "https://www.apache.org/licenses/LICENSE-2.0";, but not when it has a > url of "http://www.apache.org/licenses/LICENSE-2.0"; > It should probably not fail in the case of https. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
Philipp Ottlinger created RAT-216: - Summary: Update versions in pom after release of 0.12 and update dependencies Key: RAT-216 URL: https://issues.apache.org/jira/browse/RAT-216 Project: Apache Rat Issue Type: Task Affects Versions: 0.13 Reporter: Philipp Ottlinger Assignee: Philipp Ottlinger Fix For: 0.13 After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. Apart from that the following dependencies can be updated according to the JDK-compliance: * commons-cli * commons-compress * hamcrest * ant * ant-testutil -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426364#comment-15426364 ] Jochen Wiedmann commented on RAT-216: - Could you be more specific on the expected versions for the dependencies? > Update versions in pom after release of 0.12 and update dependencies > > > Key: RAT-216 > URL: https://issues.apache.org/jira/browse/RAT-216 > Project: Apache Rat > Issue Type: Task >Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > Apart from that the following dependencies can be updated according to the > JDK-compliance: > * commons-cli > * commons-compress > * hamcrest > * ant > * ant-testutil -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-216: -- Description: After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. * (/) migrate all poms to 0.13-SNAPSHOT * (/) update lastRATVersion to 0.12 (/) Apart from that the following dependencies can be updated according to the JDK-compliance: * commons-cli: 1.3.1 (from 1.2) * commons-compress: 1.11 (from 1.10) * hamcrest-library: 1.3 (from 1.2.1) * ant: 1.9.7 (from 1.9.6) * ant-testutil: 1.9.7 (from 1.9.6) * maven-javadoc-plugin: 2.10.4 (from 2.10.3) We are unable to update to the latest ASF parent pom since it brings in incompatible (newer) dependency versions that clash with our compiler settings. was: After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. Apart from that the following dependencies can be updated according to the JDK-compliance: * commons-cli * commons-compress * hamcrest * ant * ant-testutil > Update versions in pom after release of 0.12 and update dependencies > > > Key: RAT-216 > URL: https://issues.apache.org/jira/browse/RAT-216 > Project: Apache Rat > Issue Type: Task >Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > * (/) migrate all poms to 0.13-SNAPSHOT > * (/) update lastRATVersion to 0.12 > (/) Apart from that the following dependencies can be updated according to > the JDK-compliance: > * commons-cli: 1.3.1 (from 1.2) > * commons-compress: 1.11 (from 1.10) > * hamcrest-library: 1.3 (from 1.2.1) > * ant: 1.9.7 (from 1.9.6) > * ant-testutil: 1.9.7 (from 1.9.6) > * maven-javadoc-plugin: 2.10.4 (from 2.10.3) > We are unable to update to the latest ASF parent pom since it brings in > incompatible (newer) dependency versions that clash with our compiler > settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger resolved RAT-216. --- Resolution: Fixed DONE, builds go through: https://builds.apache.org/view/A-D/view/Creadur/job/Creadur-Rat/318/console > Update versions in pom after release of 0.12 and update dependencies > > > Key: RAT-216 > URL: https://issues.apache.org/jira/browse/RAT-216 > Project: Apache Rat > Issue Type: Task >Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > * (/) migrate all poms to 0.13-SNAPSHOT > * (/) update lastRATVersion to 0.12 > (/) Apart from that the following dependencies can be updated according to > the JDK-compliance: > * commons-cli: 1.3.1 (from 1.2) > * commons-compress: 1.11 (from 1.10) > * hamcrest-library: 1.3 (from 1.2.1) > * ant: 1.9.7 (from 1.9.6) > * ant-testutil: 1.9.7 (from 1.9.6) > * maven-javadoc-plugin: 2.10.4 (from 2.10.3) > We are unable to update to the latest ASF parent pom since it brings in > incompatible (newer) dependency versions that clash with our compiler > settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430253#comment-15430253 ] Jochen Wiedmann commented on RAT-216: - Please clarify that statement: We are unable to update to the latest ASF parent pom since it brings in incompatible (newer) dependency versions that clash with our compiler settings. AFAICT, the parent pom cannot bring any dependencies into a project, apart from specifying versions in dependencyManagement. Besides, the child can always overrule its parent. > Update versions in pom after release of 0.12 and update dependencies > > > Key: RAT-216 > URL: https://issues.apache.org/jira/browse/RAT-216 > Project: Apache Rat > Issue Type: Task >Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > * (/) migrate all poms to 0.13-SNAPSHOT > * (/) update lastRATVersion to 0.12 > (/) Apart from that the following dependencies can be updated according to > the JDK-compliance: > * commons-cli: 1.3.1 (from 1.2) > * commons-compress: 1.11 (from 1.10) > * hamcrest-library: 1.3 (from 1.2.1) > * ant: 1.9.7 (from 1.9.6) > * ant-testutil: 1.9.7 (from 1.9.6) > * maven-javadoc-plugin: 2.10.4 (from 2.10.3) > We are unable to update to the latest ASF parent pom since it brings in > incompatible (newer) dependency versions that clash with our compiler > settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-58) Create API module
[ https://issues.apache.org/jira/browse/RAT-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved RAT-58. Resolution: Fixed Assignee: Jochen Wiedmann Fix Version/s: 0.12 > Create API module > - > > Key: RAT-58 > URL: https://issues.apache.org/jira/browse/RAT-58 > Project: Apache Rat > Issue Type: Improvement >Affects Versions: 0.7 >Reporter: Robert Burrell Donkin >Assignee: Jochen Wiedmann > Fix For: 0.12 > > > Create an api module -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger reopened RAT-216: --- > Update versions in pom after release of 0.12 and update dependencies > > > Key: RAT-216 > URL: https://issues.apache.org/jira/browse/RAT-216 > Project: Apache Rat > Issue Type: Task >Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > * (/) migrate all poms to 0.13-SNAPSHOT > * (/) update lastRATVersion to 0.12 > (/) Apart from that the following dependencies can be updated according to > the JDK-compliance: > * commons-cli: 1.3.1 (from 1.2) > * commons-compress: 1.11 (from 1.10) > * hamcrest-library: 1.3 (from 1.2.1) > * ant: 1.9.7 (from 1.9.6) > * ant-testutil: 1.9.7 (from 1.9.6) > * maven-javadoc-plugin: 2.10.4 (from 2.10.3) > We are unable to update to the latest ASF parent pom since it brings in > incompatible (newer) dependency versions that clash with our compiler > settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-216: -- Description: After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. * (/) migrate all poms to 0.13-SNAPSHOT * (/) update lastRATVersion to 0.12 * (/) 20160825 UPDATE: update to latest ASF parent-pom 19 (from 17), needs update of maven-enforcer-rules to avoid NPE (1.0-beta-5 from 1.0-beta-2). (/) Apart from that the following dependencies can be updated according to the JDK-compliance: * commons-cli: 1.3.1 (from 1.2) * commons-compress: 1.11 (from 1.10) * hamcrest-library: 1.3 (from 1.2.1) * ant: 1.9.7 (from 1.9.6) * ant-testutil: 1.9.7 (from 1.9.6) * maven-javadoc-plugin: 2.10.4 (from 2.10.3) was: After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. * (/) migrate all poms to 0.13-SNAPSHOT * (/) update lastRATVersion to 0.12 (/) Apart from that the following dependencies can be updated according to the JDK-compliance: * commons-cli: 1.3.1 (from 1.2) * commons-compress: 1.11 (from 1.10) * hamcrest-library: 1.3 (from 1.2.1) * ant: 1.9.7 (from 1.9.6) * ant-testutil: 1.9.7 (from 1.9.6) * maven-javadoc-plugin: 2.10.4 (from 2.10.3) We are unable to update to the latest ASF parent pom since it brings in incompatible (newer) dependency versions that clash with our compiler settings. > Update versions in pom after release of 0.12 and update dependencies > > > Key: RAT-216 > URL: https://issues.apache.org/jira/browse/RAT-216 > Project: Apache Rat > Issue Type: Task >Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > * (/) migrate all poms to 0.13-SNAPSHOT > * (/) update lastRATVersion to 0.12 > * (/) 20160825 UPDATE: update to latest ASF parent-pom 19 (from 17), needs > update of maven-enforcer-rules to avoid NPE (1.0-beta-5 from 1.0-beta-2). > (/) Apart from that the following dependencies can be updated according to > the JDK-compliance: > * commons-cli: 1.3.1 (from 1.2) > * commons-compress: 1.11 (from 1.10) > * hamcrest-library: 1.3 (from 1.2.1) > * ant: 1.9.7 (from 1.9.6) > * ant-testutil: 1.9.7 (from 1.9.6) > * maven-javadoc-plugin: 2.10.4 (from 2.10.3) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437697#comment-15437697 ] Philipp Ottlinger commented on RAT-216: --- http://svn.apache.org/viewvc?rev=1757755&view=rev fixes NPE with new ASF parent pom. > Update versions in pom after release of 0.12 and update dependencies > > > Key: RAT-216 > URL: https://issues.apache.org/jira/browse/RAT-216 > Project: Apache Rat > Issue Type: Task >Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > * (/) migrate all poms to 0.13-SNAPSHOT > * (/) update lastRATVersion to 0.12 > * (/) 20160825 UPDATE: update to latest ASF parent-pom 19 (from 17), needs > update of maven-enforcer-rules to avoid NPE (1.0-beta-5 from 1.0-beta-2). > (/) Apart from that the following dependencies can be updated according to > the JDK-compliance: > * commons-cli: 1.3.1 (from 1.2) > * commons-compress: 1.11 (from 1.10) > * hamcrest-library: 1.3 (from 1.2.1) > * ant: 1.9.7 (from 1.9.6) > * ant-testutil: 1.9.7 (from 1.9.6) > * maven-javadoc-plugin: 2.10.4 (from 2.10.3) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger resolved RAT-216. --- Resolution: Fixed Builds went through ok :-) > Update versions in pom after release of 0.12 and update dependencies > > > Key: RAT-216 > URL: https://issues.apache.org/jira/browse/RAT-216 > Project: Apache Rat > Issue Type: Task >Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > * (/) migrate all poms to 0.13-SNAPSHOT > * (/) update lastRATVersion to 0.12 > * (/) 20160825 UPDATE: update to latest ASF parent-pom 19 (from 17), needs > update of maven-enforcer-rules to avoid NPE (1.0-beta-5 from 1.0-beta-2). > (/) Apart from that the following dependencies can be updated according to > the JDK-compliance: > * commons-cli: 1.3.1 (from 1.2) > * commons-compress: 1.11 (from 1.10) > * hamcrest-library: 1.3 (from 1.2.1) > * ant: 1.9.7 (from 1.9.6) > * ant-testutil: 1.9.7 (from 1.9.6) > * maven-javadoc-plugin: 2.10.4 (from 2.10.3) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-216) Update versions in pom after release of 0.12 and update dependencies
[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438795#comment-15438795 ] Jochen Wiedmann commented on RAT-216: - Thanks for fixing that! On Thu, Aug 25, 2016 at 11:18 PM, Philipp Ottlinger (JIRA) -- The next time you hear: "Don't reinvent the wheel!" http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg > Update versions in pom after release of 0.12 and update dependencies > > > Key: RAT-216 > URL: https://issues.apache.org/jira/browse/RAT-216 > Project: Apache Rat > Issue Type: Task >Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > * (/) migrate all poms to 0.13-SNAPSHOT > * (/) update lastRATVersion to 0.12 > * (/) 20160825 UPDATE: update to latest ASF parent-pom 19 (from 17), needs > update of maven-enforcer-rules to avoid NPE (1.0-beta-5 from 1.0-beta-2). > (/) Apart from that the following dependencies can be updated according to > the JDK-compliance: > * commons-cli: 1.3.1 (from 1.2) > * commons-compress: 1.11 (from 1.10) > * hamcrest-library: 1.3 (from 1.2.1) > * ant: 1.9.7 (from 1.9.6) > * ant-testutil: 1.9.7 (from 1.9.6) > * maven-javadoc-plugin: 2.10.4 (from 2.10.3) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-219) RAT project uses groupId: org.apache.rat instead of org.apache.creadur.rat
[
https://issues.apache.org/jira/browse/RAT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15480190#comment-15480190
]
Philipp Ottlinger commented on RAT-219:
---
WDYT - could the rootpom be in package {code}org.apache.creadur{code}?
This would make sense if we were to use a big rootpom for all creadur artifacts.
> RAT project uses groupId: org.apache.rat instead of org.apache.creadur.rat
> --
>
> Key: RAT-219
> URL: https://issues.apache.org/jira/browse/RAT-219
> Project: Apache Rat
> Issue Type: Improvement
>Affects Versions: 0.12
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 0.13
>
>
> This should be done before 1.0.0 to make it consistent with the other
> projects (Whiskers/Tentacles).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (RAT-221) Change the URL in JIRA which points to creadur.apache.org instead
[ https://issues.apache.org/jira/browse/RAT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger reassigned RAT-221: - Assignee: Philipp Ottlinger > Change the URL in JIRA which points to creadur.apache.org instead > - > > Key: RAT-221 > URL: https://issues.apache.org/jira/browse/RAT-221 > Project: Apache Rat > Issue Type: Improvement > Components: docs >Reporter: Karl Heinz Marbaise >Assignee: Philipp Ottlinger >Priority: Trivial > Fix For: 0.13 > > > The URL given in JIRA headline is wrongly pointing to creadur.apache.org > instead of creadur.apache.org/rat/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-221) Change the URL in JIRA which points to creadur.apache.org instead
[ https://issues.apache.org/jira/browse/RAT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger resolved RAT-221. --- Resolution: Fixed Fix Version/s: 0.13 Thanks for the hint, fixed in JiraAdmin/project properties. > Change the URL in JIRA which points to creadur.apache.org instead > - > > Key: RAT-221 > URL: https://issues.apache.org/jira/browse/RAT-221 > Project: Apache Rat > Issue Type: Improvement > Components: docs >Reporter: Karl Heinz Marbaise >Assignee: Philipp Ottlinger >Priority: Trivial > Fix For: 0.13 > > > The URL given in JIRA headline is wrongly pointing to creadur.apache.org > instead of creadur.apache.org/rat/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-219) RAT project uses groupId: org.apache.rat instead of org.apache.creadur.rat
[ https://issues.apache.org/jira/browse/RAT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved RAT-219. - Resolution: Won't Fix Assignee: Jochen Wiedmann As far as I am concerned, not changing the groupId has been an intentional, although informal decision, when Rat went TLP, in order to avoid compatibility issues. OTOH, Rat is basically a build time tool. I am unaware of any users, that use it at runtime. In fact, nowadays, I am even unaware of any users of the Ant tasks, or the CLI. So, I wouldn't block any change, if you'd do it in Git. Nevertheless, I am resolving this issue, so that it is out of scope. > RAT project uses groupId: org.apache.rat instead of org.apache.creadur.rat > -- > > Key: RAT-219 > URL: https://issues.apache.org/jira/browse/RAT-219 > Project: Apache Rat > Issue Type: Improvement >Affects Versions: 0.12 >Reporter: Karl Heinz Marbaise >Assignee: Jochen Wiedmann >Priority: Critical > Fix For: 0.13 > > > This should be done before 1.0.0 to make it consistent with the other > projects (Whiskers/Tentacles). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-220) JDK version 1.6
[ https://issues.apache.org/jira/browse/RAT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15481387#comment-15481387 ] Jochen Wiedmann commented on RAT-220: - Maven is at 1.8, Eclipse is at 1.7. How about skipping 1.6, and going to 1.7? I think java.nio might have a lot to offer for Rat. Whiskers, and Tentacles, can follow, if they want, or not. (I think there is no reason for concerns, as none is a dependency of the others.) Jochen > JDK version 1.6 > --- > > Key: RAT-220 > URL: https://issues.apache.org/jira/browse/RAT-220 > Project: Apache Rat > Issue Type: Improvement >Reporter: Karl Heinz Marbaise > > Currently the RAT project defines as Java compatibility 1.5 but Tentacles > defines 1.6 and Whiskers as well 1.6 so it would be a good idea to go to 1.6 > as minimumIf someone needs to work with 1.5 toolchain can be used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (RAT-220) JDK version 1.6
[ https://issues.apache.org/jira/browse/RAT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann reassigned RAT-220: --- Assignee: Jochen Wiedmann > JDK version 1.6 > --- > > Key: RAT-220 > URL: https://issues.apache.org/jira/browse/RAT-220 > Project: Apache Rat > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Assignee: Jochen Wiedmann > > Currently the RAT project defines as Java compatibility 1.5 but Tentacles > defines 1.6 and Whiskers as well 1.6 so it would be a good idea to go to 1.6 > as minimumIf someone needs to work with 1.5 toolchain can be used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-220) JDK version 1.6
[ https://issues.apache.org/jira/browse/RAT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15481405#comment-15481405 ] Jochen Wiedmann commented on RAT-220: - Okay, you're right. But, my point is, that we have no need to stay behind the build time tools, that our users typically depend on, so we might proceed with 1.7, anyways. > JDK version 1.6 > --- > > Key: RAT-220 > URL: https://issues.apache.org/jira/browse/RAT-220 > Project: Apache Rat > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Assignee: Jochen Wiedmann > > Currently the RAT project defines as Java compatibility 1.5 but Tentacles > defines 1.6 and Whiskers as well 1.6 so it would be a good idea to go to 1.6 > as minimumIf someone needs to work with 1.5 toolchain can be used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-220) JDK version 1.6
[ https://issues.apache.org/jira/browse/RAT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15481510#comment-15481510 ] Jochen Wiedmann commented on RAT-220: - Well, what is the paint point? Who's bothered, right now? > JDK version 1.6 > --- > > Key: RAT-220 > URL: https://issues.apache.org/jira/browse/RAT-220 > Project: Apache Rat > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Assignee: Jochen Wiedmann > > Currently the RAT project defines as Java compatibility 1.5 but Tentacles > defines 1.6 and Whiskers as well 1.6 so it would be a good idea to go to 1.6 > as minimumIf someone needs to work with 1.5 toolchain can be used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RAT-222) Download script of SNAPSHOT site refers to yet unavailable artifact but should show releases only
Philipp Ottlinger created RAT-222:
-
Summary: Download script of SNAPSHOT site refers to yet
unavailable artifact but should show releases only
Key: RAT-222
URL: https://issues.apache.org/jira/browse/RAT-222
Project: Apache Rat
Issue Type: Bug
Affects Versions: 0.12, 0.13
Environment: http://creadur.apache.org/rat/download_rat.cgi
Reporter: Attila Simon
Fix For: 0.13
h2. Mailthread
The current site shows an unavailable artifact in the download section:
{code}
https://archive.apache.org/dist/creadur/ -> lists 0.12 as latest
http://creadur.apache.org -> tells that RAT latest release is 0.12 on
2016.06.10
http://creadur.staging.apache.org/rat/download_rat.cgi -> tells 0.12 (also
available in maven)
http://creadur.apache.org/rat/download_rat.cgi -> tells 0.13 (maven fails
to resolve)
{code}
h2. Context
Due to the problems with the 0.12 site release we currently deployed the
0.13-SNAPSHOT, which is not yet available as a release artifact.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (RAT-158) SAXParser warnings
[
https://issues.apache.org/jira/browse/RAT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger updated RAT-158:
--
Fix Version/s: (was: 0.12)
0.13
> 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.13
>
> Attachments: RAT-158-2.patch, RAT-158.patch
>
>
> I have rat configured as such
> {code}
> org.apache.rat
> apache-rat-plugin
> false
>
>
> verify
>
>check
>
>
>
>
>
> **/conf/**
>
>
>
> {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)
[jira] [Created] (RAT-223) Add support for Golang and Perl module files
Eric Friedrich created RAT-223: -- Summary: Add support for Golang and Perl module files Key: RAT-223 URL: https://issues.apache.org/jira/browse/RAT-223 Project: Apache Rat Issue Type: Improvement Reporter: Eric Friedrich Priority: Minor RAT can now audit .go and .pm files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RAT-223) Add support for Golang and Perl module files
[ https://issues.apache.org/jira/browse/RAT-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646066#comment-15646066 ] Eric Friedrich commented on RAT-223: https://github.com/apache/creadur-rat/pull/4 > Add support for Golang and Perl module files > > > Key: RAT-223 > URL: https://issues.apache.org/jira/browse/RAT-223 > Project: Apache Rat > Issue Type: Improvement >Reporter: Eric Friedrich >Priority: Minor > > RAT can now audit .go and .pm files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-223) Add support for Golang and Perl module files
[ https://issues.apache.org/jira/browse/RAT-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-223: -- Fix Version/s: 0.13 > Add support for Golang and Perl module files > > > Key: RAT-223 > URL: https://issues.apache.org/jira/browse/RAT-223 > Project: Apache Rat > Issue Type: Improvement >Affects Versions: 0.12 >Reporter: Eric Friedrich >Priority: Minor > Fix For: 0.13 > > > RAT can now audit .go and .pm files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RAT-223) Add support for Golang and Perl module files
[ https://issues.apache.org/jira/browse/RAT-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-223: -- Affects Version/s: 0.12 > Add support for Golang and Perl module files > > > Key: RAT-223 > URL: https://issues.apache.org/jira/browse/RAT-223 > Project: Apache Rat > Issue Type: Improvement >Affects Versions: 0.12 >Reporter: Eric Friedrich >Priority: Minor > Fix For: 0.13 > > > RAT can now audit .go and .pm files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (RAT-223) Add support for Golang and Perl module files
[ https://issues.apache.org/jira/browse/RAT-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger reassigned RAT-223: - Assignee: Philipp Ottlinger > Add support for Golang and Perl module files > > > Key: RAT-223 > URL: https://issues.apache.org/jira/browse/RAT-223 > Project: Apache Rat > Issue Type: Improvement >Affects Versions: 0.12 >Reporter: Eric Friedrich >Assignee: Philipp Ottlinger >Priority: Minor > Fix For: 0.13 > > > RAT can now audit .go and .pm files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-223) Add support for Golang and Perl module files
[ https://issues.apache.org/jira/browse/RAT-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger resolved RAT-223. --- Resolution: Fixed Integrated as http://svn.apache.org/viewvc?view=revision&revision=1768796 [~friede] Please verify with a newly build SNAPSHOT of 0.13 and close this issue if it works as you intended it to be. Thanks again for your contribution and help :-) > Add support for Golang and Perl module files > > > Key: RAT-223 > URL: https://issues.apache.org/jira/browse/RAT-223 > Project: Apache Rat > Issue Type: Improvement >Affects Versions: 0.12 >Reporter: Eric Friedrich >Assignee: Philipp Ottlinger >Priority: Minor > Fix For: 0.13 > > > RAT can now audit .go and .pm files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RAT-224) apache-rat-plugin custom license example doesn't work
John Patrick created RAT-224: Summary: apache-rat-plugin custom license example doesn't work Key: RAT-224 URL: https://issues.apache.org/jira/browse/RAT-224 Project: Apache Rat Issue Type: Bug Affects Versions: 0.12 Environment: website Reporter: John Patrick the example custom license doesn't work -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (RAT-224) apache-rat-plugin custom license example doesn't work
[ https://issues.apache.org/jira/browse/RAT-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger reassigned RAT-224: - Assignee: Philipp Ottlinger > apache-rat-plugin custom license example doesn't work > - > > Key: RAT-224 > URL: https://issues.apache.org/jira/browse/RAT-224 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.12 > Environment: website >Reporter: John Patrick >Assignee: Philipp Ottlinger > > the example custom license doesn't work -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RAT-224) apache-rat-plugin custom license example doesn't work
[ https://issues.apache.org/jira/browse/RAT-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger resolved RAT-224. --- Resolution: Fixed Fix Version/s: 0.13 Added the given PR https://github.com/apache/creadur-rat/pull/5/files http://svn.apache.org/viewvc?rev=1770594&view=rev Thanks for spotting the mistake! Please verify and close this issue :-) > apache-rat-plugin custom license example doesn't work > - > > Key: RAT-224 > URL: https://issues.apache.org/jira/browse/RAT-224 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.12 > Environment: website >Reporter: John Patrick >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > the example custom license doesn't work -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (RAT-222) Download script of SNAPSHOT site refers to yet unavailable artifact but should show releases only
[
https://issues.apache.org/jira/browse/RAT-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger reassigned RAT-222:
-
Assignee: Philipp Ottlinger
> Download script of SNAPSHOT site refers to yet unavailable artifact but
> should show releases only
> -
>
> Key: RAT-222
> URL: https://issues.apache.org/jira/browse/RAT-222
> Project: Apache Rat
> Issue Type: Bug
>Affects Versions: 0.12, 0.13
> Environment: http://creadur.apache.org/rat/download_rat.cgi
>Reporter: Attila Simon
>Assignee: Philipp Ottlinger
> Fix For: 0.13
>
>
> h2. Mailthread
> The current site shows an unavailable artifact in the download section:
> {code}
> https://archive.apache.org/dist/creadur/ -> lists 0.12 as latest
> http://creadur.apache.org -> tells that RAT latest release is 0.12 on
> 2016.06.10
> http://creadur.staging.apache.org/rat/download_rat.cgi -> tells 0.12 (also
> available in maven)
> http://creadur.apache.org/rat/download_rat.cgi -> tells 0.13 (maven fails
> to resolve)
> {code}
> h2. Context
> Due to the problems with the 0.12 site release we currently deployed the
> 0.13-SNAPSHOT, which is not yet available as a release artifact.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (RAT-222) Download script of SNAPSHOT site refers to yet unavailable artifact but should show releases only
[
https://issues.apache.org/jira/browse/RAT-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger resolved RAT-222.
---
Resolution: Fixed
Thanks for reporting this issue - I've fixed the webpage and adapted the
templates to contain a special section referencing to the latest RAT release
and the current SNAPSHOT.
http://svn.apache.org/viewvc?rev=1770753&view=rev
> Download script of SNAPSHOT site refers to yet unavailable artifact but
> should show releases only
> -
>
> Key: RAT-222
> URL: https://issues.apache.org/jira/browse/RAT-222
> Project: Apache Rat
> Issue Type: Bug
>Affects Versions: 0.12, 0.13
> Environment: http://creadur.apache.org/rat/download_rat.cgi
>Reporter: Attila Simon
>Assignee: Philipp Ottlinger
> Fix For: 0.13
>
>
> h2. Mailthread
> The current site shows an unavailable artifact in the download section:
> {code}
> https://archive.apache.org/dist/creadur/ -> lists 0.12 as latest
> http://creadur.apache.org -> tells that RAT latest release is 0.12 on
> 2016.06.10
> http://creadur.staging.apache.org/rat/download_rat.cgi -> tells 0.12 (also
> available in maven)
> http://creadur.apache.org/rat/download_rat.cgi -> tells 0.13 (maven fails
> to resolve)
> {code}
> h2. Context
> Due to the problems with the 0.12 site release we currently deployed the
> 0.13-SNAPSHOT, which is not yet available as a release artifact.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (RAT-225) Maven RAT excludes do not work under windows
Pascal Schumacher created RAT-225:
-
Summary: Maven RAT excludes do not work under windows
Key: RAT-225
URL: https://issues.apache.org/jira/browse/RAT-225
Project: Apache Rat
Issue Type: Bug
Components: maven
Affects Versions: 0.12
Environment: windows 10
Reporter: Pascal Schumacher
{code}mvn apache-rat:check{code} fails for projects like commons-lang and
commons-compress.
Commons lang uses this plugin configuration:
{code}
org.apache.rat
apache-rat-plugin
site-content/**
src/site/resources/.htaccess
src/site/resources/download_lang.cgi
src/site/resources/release-notes/RELEASE-NOTES-*.txt
src/test/resources/lang-708-input.txt
{code}
see https://github.com/apache/commons-lang/blob/master/pom.xml#L733
{code}mvn apache-rat:check{code} fails and rat.txt contains:
{code}!? src/site/resources/.htaccess
!? src/site/resources/release-notes/RELEASE-NOTES-1.0.1.txt{code}
I guess this is because I'm using Windows.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (RAT-225) Maven RAT excludes do not work under windows
[
https://issues.apache.org/jira/browse/RAT-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher closed RAT-225.
-
Resolution: Invalid
Thank you very much! :)
Sorry for wasting your time with an invalid bug report. :(
> Maven RAT excludes do not work under windows
>
>
> Key: RAT-225
> URL: https://issues.apache.org/jira/browse/RAT-225
> Project: Apache Rat
> Issue Type: Bug
> Components: maven
>Affects Versions: 0.12
> Environment: windows 10
>Reporter: Pascal Schumacher
> Attachments: apache-rat.patch
>
>
> {code}mvn apache-rat:check{code} fails for projects like commons-lang and
> commons-compress.
> Commons lang uses this plugin configuration:
> {code}
> org.apache.rat
> apache-rat-plugin
>
>
> site-content/**
> src/site/resources/.htaccess
> src/site/resources/download_lang.cgi
>
> src/site/resources/release-notes/RELEASE-NOTES-*.txt
> src/test/resources/lang-708-input.txt
>
>
> {code}
> see https://github.com/apache/commons-lang/blob/master/pom.xml#L733
> {code}mvn apache-rat:check{code} fails and rat.txt contains:
> {code}!? src/site/resources/.htaccess
> !? src/site/resources/release-notes/RELEASE-NOTES-1.0.1.txt{code}
> I guess this is because I'm using Windows.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (RAT-225) Maven RAT excludes do not work under windows
[
https://issues.apache.org/jira/browse/RAT-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758944#comment-15758944
]
Pascal Schumacher commented on RAT-225:
---
Sure.
> Maven RAT excludes do not work under windows
>
>
> Key: RAT-225
> URL: https://issues.apache.org/jira/browse/RAT-225
> Project: Apache Rat
> Issue Type: Bug
> Components: maven
>Affects Versions: 0.12
> Environment: windows 10
>Reporter: Pascal Schumacher
> Attachments: apache-rat.patch
>
>
> {code}mvn apache-rat:check{code} fails for projects like commons-lang and
> commons-compress.
> Commons lang uses this plugin configuration:
> {code}
> org.apache.rat
> apache-rat-plugin
>
>
> site-content/**
> src/site/resources/.htaccess
> src/site/resources/download_lang.cgi
>
> src/site/resources/release-notes/RELEASE-NOTES-*.txt
> src/test/resources/lang-708-input.txt
>
>
> {code}
> see https://github.com/apache/commons-lang/blob/master/pom.xml#L733
> {code}mvn apache-rat:check{code} fails and rat.txt contains:
> {code}!? src/site/resources/.htaccess
> !? src/site/resources/release-notes/RELEASE-NOTES-1.0.1.txt{code}
> I guess this is because I'm using Windows.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (RAT-226) Update to latest compatible Apache ant
Philipp Ottlinger created RAT-226: - Summary: Update to latest compatible Apache ant Key: RAT-226 URL: https://issues.apache.org/jira/browse/RAT-226 Project: Apache Rat Issue Type: Improvement Components: antlib Affects Versions: 0.12 Reporter: Philipp Ottlinger Assignee: Philipp Ottlinger Fix For: 0.13 Update to latest compatible ANT 1.9.9 following the release announcement from 2017-02-06. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RAT-227) Change all links in maven-generated site to https for security reasons
Philipp Ottlinger created RAT-227: - Summary: Change all links in maven-generated site to https for security reasons Key: RAT-227 URL: https://issues.apache.org/jira/browse/RAT-227 Project: Apache Rat Issue Type: Improvement Components: site Affects Versions: 0.12 Reporter: Philipp Ottlinger Fix For: 0.13 The site contains many http links including the link to the source repository. Change all to https. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RAT-227) Change all links in maven-generated site to https for security reasons
[ https://issues.apache.org/jira/browse/RAT-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-227: -- Description: The site contains many http links including the link to the source repository. Change all to https. Do the same with all links in pom.xml since they are extracted during site generation. was:The site contains many http links including the link to the source repository. Change all to https. > Change all links in maven-generated site to https for security reasons > -- > > Key: RAT-227 > URL: https://issues.apache.org/jira/browse/RAT-227 > Project: Apache Rat > Issue Type: Improvement > Components: site >Affects Versions: 0.12 >Reporter: Philipp Ottlinger > Fix For: 0.13 > > > The site contains many http links including the link to the source > repository. Change all to https. > Do the same with all links in pom.xml since they are extracted during site > generation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RAT-228) Test failures in antunit does not break the maven build / ANT does not seem to recognize additional licenses
Philipp Ottlinger created RAT-228:
-
Summary: Test failures in antunit does not break the maven build /
ANT does not seem to recognize additional licenses
Key: RAT-228
URL: https://issues.apache.org/jira/browse/RAT-228
Project: Apache Rat
Issue Type: Bug
Components: antlib
Affects Versions: 0.12
Reporter: Philipp Ottlinger
Fix For: 0.13
When I was working on RAT-226 I realized that there's a test failure within the
apache-rat-tasks submodule:
{code}
cd apache-rat-tasks
mvn clean test
[INFO] --- maven-antrun-plugin:1.7:run (default) @ apache-rat-tasks ---
[INFO] Executing tasks
main:
allTests:
[au:antunit] Build File:
/home/user/ws/rat-trunk/apache-rat-tasks/src/test/resources/antunit/report-bad-configurations.xml
[au:antunit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0,291 sec
[au:antunit] Target: testNoStylesheet took 0,003 sec
[au:antunit] Target: testNoResources took 0,001 sec
[au:antunit] Target: testSubstringMatcherRequiresFamilyName took 0,087 sec
[au:antunit] Target: testFullTextMatcherRequiresFamilyName took 0,024 sec
[au:antunit] Target: testUnusedStylesheet took 0,042 sec
[au:antunit] Target: testFullTextMatcherRequiresText took 0,019 sec
[au:antunit] Target: testSubstringMatcherRequiresFamilyCategory took 0,023 sec
[au:antunit] Target: testSubstringMatcherRequiresPattern took 0,026 sec
[au:antunit] Target: testNoLicenseMatchers took 0,001 sec
[au:antunit] Target: testFullTextMatcherRequiresFamilyCategory took 0,016 sec
[mkdir] Created dir:
/home/user/ws/rat-trunk/apache-rat-tasks/target/testoutput/dest
allTests:
[au:antunit] Build File:
/home/user/ws/rat-trunk/apache-rat-tasks/src/test/resources/antunit/report-normal-operation.xml
[au:antunit] Tests run: 11, Failures: 0, Errors: 6, Time elapsed: 1,293 sec
[au:antunit] Target: testFullTextMatcherNotApprovedSentToFile caused an ERROR
[au:antunit]at line 209, column 55
[au:antunit]Message: The following error occurred while executing this line:
[au:antunit]
/home/user/ws/rat-trunk/apache-rat-tasks/src/test/resources/antunit/report-normal-operation.xml:282:
expected report to contain '!YASL1
/home/user/ws/rat-trunk/apache-rat-tasks/src/test/resources/antunit/report-normal-operation.xml'
but was '
[au:antunit] *
[au:antunit] Summary
[au:antunit] ---
[au:antunit] Generated at: 2017-02-06T23:12:54+01:00
[au:antunit]
[au:antunit] Notes: 0
[au:antunit] Binaries: 0
[au:antunit] Archives: 0
[au:antunit] Standards: 1
[au:antunit]
[au:antunit] Apache Licensed: 0
[au:antunit] Generated Documents: 0
[au:antunit]
[au:antunit] JavaDocs are generated, thus a license header is optional.
[au:antunit] Generated files do not require license headers.
[au:antunit]
[au:antunit] 1 Unknown Licenses
[au:antunit]
[au:antunit] *
[au:antunit]
[au:antunit] Files with unapproved licenses:
[au:antunit]
[au:antunit]
/home/user/ws/rat-trunk/apache-rat-tasks/src/test/resources/antunit/report-normal-operation.xml
[au:antunit]
[au:antunit] *
[au:antunit]
[au:antunit] *
[au:antunit] Files with Apache License headers will be marked AL
[au:antunit] Binary files (which do not require any license headers) will be
marked B
[au:antunit] Compressed archives will be marked A
[au:antunit] Notices, licenses etc. will be marked N
[au:antunit] !?
/home/user/ws/rat-trunk/apache-rat-tasks/src/test/resources/antunit/report-normal-operation.xml
[au:antunit]
[au:antunit] *
[au:antunit]
[au:antunit] Printing headers for text files without a valid license header...
[au:antunit]
[au:antunit] =
[au:antunit] == File:
/home/user/ws/rat-trunk/apache-rat-tasks/src/test/resources/antunit/report-normal-operation.xml
[au:antunit] =
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit]
[au:antunit] '
[au:antunit]took 0,101 sec
[au:antunit] Target: testFullTextMatcherSentToFileNoMatch took 0,094 sec
[au:antunit] Target: testFullTextMatcherApprovedSentToFile caused an ERROR
[au:antunit]at line 227, column 55
[au:antunit]Message: The following error occurred while executing this line:
[au:antunit]
/home/user/ws/rat-trunk/apache-rat-tasks/src/test/resources/antunit/report-normal-operation.xml:282:
e
[jira] [Created] (RAT-229) Mp3 files are not treated as binary
Maxim Solodovnik created RAT-229: Summary: Mp3 files are not treated as binary Key: RAT-229 URL: https://issues.apache.org/jira/browse/RAT-229 Project: Apache Rat Issue Type: Bug Affects Versions: 0.12 Reporter: Maxim Solodovnik Mp3 file are not treated as binary and being printed as apache incompatible to the report -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RAT-229) Mp3 files are not treated as binary
[ https://issues.apache.org/jira/browse/RAT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902330#comment-15902330 ] Maxim Solodovnik commented on RAT-229: -- Example report: https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.2.x/ws/openmeetings-web/target/rat.txt > Mp3 files are not treated as binary > --- > > Key: RAT-229 > URL: https://issues.apache.org/jira/browse/RAT-229 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.12 >Reporter: Maxim Solodovnik > > Mp3 file are not treated as binary and being printed as apache incompatible > to the report -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (RAT-229) Mp3 files are not treated as binary
[ https://issues.apache.org/jira/browse/RAT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik updated RAT-229: - Comment: was deleted (was: Example report: https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.2.x/ws/openmeetings-web/target/rat.txt) > Mp3 files are not treated as binary > --- > > Key: RAT-229 > URL: https://issues.apache.org/jira/browse/RAT-229 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.12 >Reporter: Maxim Solodovnik > > Mp3 file are not treated as binary and being printed as apache incompatible > to the report -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RAT-229) Mp3 files are not treated as binary
[ https://issues.apache.org/jira/browse/RAT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik updated RAT-229: - Attachment: rat.txt Jenkins workspace will be clean-up on next build, so attach it here > Mp3 files are not treated as binary > --- > > Key: RAT-229 > URL: https://issues.apache.org/jira/browse/RAT-229 > Project: Apache Rat > Issue Type: Bug >Affects Versions: 0.12 >Reporter: Maxim Solodovnik > Attachments: rat.txt > > > Mp3 file are not treated as binary and being printed as apache incompatible > to the report -- This message was sent by Atlassian JIRA (v6.3.15#6346)
