from:"JIRA"

[
https://issues.apache.org/jira/browse/RAT-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323256#comment-14323256
]

Dan Dumont commented on RAT-190:

I had specified none, so the default that was added to the pom (clean install)
was used.

I just tested this on Maven 3.2.5 and it still succeeds.

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
Assignee: Philipp Ottlinger
Attachments: complete-pom.xml, test.zip

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (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-tabpanelfocusedCommentId=14323245#comment-14323245
 ] 

Dan Dumont edited comment on RAT-190 at 2/16/15 8:32 PM:
-

I've merged your pom into my zip and I'm uploading a new version.
You'll note that I did NOT add the correct copyright to the js file, so you 
should expect an error... yet..


mvn -version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
08:51:28-0500)
Maven home: C:\apache-maven-3.0.5\bin\..
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_21\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 8, version: 6.2, arch: amd64, family: windows



[INFO]
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ test ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: C:\Users\ddumont\Desktop\test\target\test-1.0-SNAPSHOT.jar
[INFO]
[INFO] --- apache-rat-plugin:0.11:check (default) @ test ---
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: *.loadrule
[INFO] Exclude: **/.*
[INFO] Exclude: **/.*/*
[INFO] Exclude: **/*.json
[INFO] Exclude: **/*.html
[INFO] Exclude: **/*.md
[INFO] Exclude: **/*.log
[INFO] Exclude: **/*.mf
[INFO] Exclude: src/site/**
[INFO] Exclude: src/scripts/**
[INFO] Exclude: *.obsolete/**
[INFO] Exclude: **/test/**
[INFO] Exclude: sequoia-crx/**
[INFO] Exclude: shimmer-cookie-ninja/**
[INFO] 2 resources included (use -debug for more details)
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 1 licence.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ test ---
[INFO] Installing \test\target\test-1.0-SNAPSHOT.jar to 
\.m2\repository\com\mycompany\app\test\
1.0-SNAPSHOT\test-1.0-SNAPSHOT.jar
[INFO] Installing \test\pom.xml to 
\.m2\repository\com\mycompany\app\test\1.0-SNAPSHOT\test-1.0
-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2.588s
[INFO] Finished at: Mon Feb 16 15:27:37 EST 2015
[INFO] Final Memory: 11M/151M
[INFO] 


was (Author: ddumont):
I've merged your pom into my zip and I'm uploading a new version.
You'll note that I did NOT add the correct copyright to the js file, so you 
should expect an error... yet..

mvn -version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
08:51:28-0500)
Maven home: C:\apache-maven-3.0.5\bin\..
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_21\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 8, version: 6.2, arch: amd64, family: windows



[INFO]
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ test ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: C:\Users\ddumont\Desktop\test\target\test-1.0-SNAPSHOT.jar
[INFO]
[INFO] --- apache-rat-plugin:0.11:check (default) @ test ---
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: *.loadrule
[INFO] Exclude: **/.*
[INFO] Exclude: **/.*/*
[INFO] Exclude: **/*.json
[INFO] Exclude: **/*.html
[INFO] Exclude: **/*.md
[INFO] Exclude: **/*.log
[INFO] Exclude: **/*.mf
[INFO] Exclude: src/site/**
[INFO] Exclude: src/scripts/**
[INFO] Exclude: *.obsolete/**
[INFO] Exclude: **/test/**
[INFO] Exclude: sequoia-crx/**
[INFO] Exclude: shimmer-cookie-ninja/**
[INFO] 2 resources included (use -debug for more details)
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 1 licence.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ test ---
[INFO] Installing \test\target\test-1.0-SNAPSHOT.jar to 
\.m2\repository\com\mycompany\app\test\
1.0-SNAPSHOT\test-1.0-SNAPSHOT.jar
[INFO] Installing \test\pom.xml to 
\.m2\repository\com\mycompany\app\test\1.0-SNAPSHOT\test-1.0
-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2.588s
[INFO] Finished at: Mon Feb 16 15:27:37 EST 2015
[INFO] Final Memory: 11M/151M
[INFO] 

 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
Assignee: Philipp Ottlinger
 Attachments: complete-pom.xml, test.zip


 We're using rat to enforce our internal

[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-tabpanelfocusedCommentId=14323245#comment-14323245
 ] 

Dan Dumont commented on RAT-190:


I've merged your pom into my zip and I'm uploading a new version.
You'll note that I did NOT add the correct copyright to the js file, so you 
should expect an error... yet..

mvn -version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
08:51:28-0500)
Maven home: C:\apache-maven-3.0.5\bin\..
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_21\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 8, version: 6.2, arch: amd64, family: windows



[INFO]
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ test ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: C:\Users\ddumont\Desktop\test\target\test-1.0-SNAPSHOT.jar
[INFO]
[INFO] --- apache-rat-plugin:0.11:check (default) @ test ---
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: *.loadrule
[INFO] Exclude: **/.*
[INFO] Exclude: **/.*/*
[INFO] Exclude: **/*.json
[INFO] Exclude: **/*.html
[INFO] Exclude: **/*.md
[INFO] Exclude: **/*.log
[INFO] Exclude: **/*.mf
[INFO] Exclude: src/site/**
[INFO] Exclude: src/scripts/**
[INFO] Exclude: *.obsolete/**
[INFO] Exclude: **/test/**
[INFO] Exclude: sequoia-crx/**
[INFO] Exclude: shimmer-cookie-ninja/**
[INFO] 2 resources included (use -debug for more details)
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 1 licence.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ test ---
[INFO] Installing \test\target\test-1.0-SNAPSHOT.jar to 
\.m2\repository\com\mycompany\app\test\
1.0-SNAPSHOT\test-1.0-SNAPSHOT.jar
[INFO] Installing \test\pom.xml to 
\.m2\repository\com\mycompany\app\test\1.0-SNAPSHOT\test-1.0
-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2.588s
[INFO] Finished at: Mon Feb 16 15:27:37 EST 2015
[INFO] Final Memory: 11M/151M
[INFO] 

 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
Assignee: Philipp Ottlinger
 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:
 licenses
   license 
 implementation=org.apache.rat.analysis.license.SimplePatternBasedLicense
 licenseFamilyCategoryIBMCL/licenseFamilyCategory
 licenseFamilyNameIBM Copyright/licenseFamilyName
 notes/notes
 patterns
   patternCopyright IBM Corp. 2015/pattern
   patternCopyright IBM Corp. 2014, 2015/pattern
   patternCopyright IBM Corp. 2013, 2015/pattern
 /patterns
   /license
 /licenses
 licenseFamilies
   licenseFamily implementation=org.apache.rat.license.SimpleLicenseFamily
   familyNameIBM Copyright/familyName
 /licenseFamily
 /licenseFamilies
 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] [Updated] (RAT-190) False negatives(?) in apache rat license checking


 [ 
https://issues.apache.org/jira/browse/RAT-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Dumont updated RAT-190:
---
Attachment: (was: test.zip)

 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
Assignee: Philipp Ottlinger
 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:
 licenses
   license 
 implementation=org.apache.rat.analysis.license.SimplePatternBasedLicense
 licenseFamilyCategoryIBMCL/licenseFamilyCategory
 licenseFamilyNameIBM Copyright/licenseFamilyName
 notes/notes
 patterns
   patternCopyright IBM Corp. 2015/pattern
   patternCopyright IBM Corp. 2014, 2015/pattern
   patternCopyright IBM Corp. 2013, 2015/pattern
 /patterns
   /license
 /licenses
 licenseFamilies
   licenseFamily implementation=org.apache.rat.license.SimpleLicenseFamily
   familyNameIBM Copyright/familyName
 /licenseFamily
 /licenseFamilies
 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-tabpanelfocusedCommentId=14323251#comment-14323251
]

Philipp Ottlinger commented on RAT-190:
---

What mvn goal are you running?

Please add this information - thanks.

False negatives(?) in apache rat license checking
-

--
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-tabpanelfocusedCommentId=14323260#comment-14323260
 ] 

Dan Dumont commented on RAT-190:


Here's some debug (-X) output if it helps

{code}
[INFO]
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ test ---
[DEBUG] org.apache.maven.plugins:maven-jar-plugin:jar:2.3.2:
[DEBUG]org.apache.maven:maven-plugin-api:jar:2.0.6:compile
[DEBUG]org.apache.maven:maven-project:jar:2.0.6:compile
[DEBUG]   org.apache.maven:maven-settings:jar:2.0.6:compile
[DEBUG]   org.apache.maven:maven-profile:jar:2.0.6:compile
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0.6:compile
[DEBUG]  org.apache.maven:maven-repository-metadata:jar:2.0.6:compile
[DEBUG]   org.apache.maven:maven-plugin-registry:jar:2.0.6:compile
[DEBUG]   
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
[DEBUG]  junit:junit:jar:3.8.1:compile
[DEBUG]  classworlds:classworlds:jar:1.1-alpha-2:compile
[DEBUG]org.apache.maven:maven-model:jar:2.0.6:runtime
[DEBUG]org.apache.maven:maven-artifact:jar:2.0.6:compile
[DEBUG]org.apache.maven:maven-archiver:jar:2.4.2:compile
[DEBUG]   org.codehaus.plexus:plexus-interpolation:jar:1.13:compile
[DEBUG]org.codehaus.plexus:plexus-archiver:jar:2.0.1:compile
[DEBUG]   org.codehaus.plexus:plexus-io:jar:2.0.1:compile
[DEBUG]commons-lang:commons-lang:jar:2.1:compile
[DEBUG]org.codehaus.plexus:plexus-utils:jar:3.0:compile
[DEBUG] Created new class realm 
pluginorg.apache.maven.plugins:maven-jar-plugin:2.3.2
[DEBUG] Importing foreign packages into class realm 
pluginorg.apache.maven.plugins:maven-jar-plugin:2.3.2
[DEBUG]   Imported:   maven.api
[DEBUG] Populating class realm 
pluginorg.apache.maven.plugins:maven-jar-plugin:2.3.2
[DEBUG]   Included: org.apache.maven.plugins:maven-jar-plugin:jar:2.3.2
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.apache.maven:maven-archiver:jar:2.4.2
[DEBUG]   Included: org.codehaus.plexus:plexus-interpolation:jar:1.13
[DEBUG]   Included: org.codehaus.plexus:plexus-archiver:jar:2.0.1
[DEBUG]   Included: org.codehaus.plexus:plexus-io:jar:2.0.1
[DEBUG]   Included: commons-lang:commons-lang:jar:2.1
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:3.0
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG]   Excluded: 
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
[DEBUG] Configuring mojo org.apache.maven.plugins:maven-jar-plugin:2.3.2:jar 
from plugin realm ClassRealm[pluginorg.apache.maven.plugi
ns:maven-jar-plugin:2.3.2, parent: sun.misc.Launcher$AppClassLoader@ba679e]
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-jar-plugin:2.3.2:jar' 
with basic configurator --
[DEBUG]   (f) classesDirectory = \test\target\classes
[DEBUG]   (f) defaultManifestFile = \test\target\classes\META-INF\MANIFEST.MF
[DEBUG]   (f) finalName = test-1.0-SNAPSHOT
[DEBUG]   (f) forceCreation = false
[DEBUG]   (f) outputDirectory = \test\target
[DEBUG]   (f) project = MavenProject: com.mycompany.app:test:1.0-SNAPSHOT @ 
\test\pom.xml
[DEBUG]   (f) useDefaultManifestFile = false
[DEBUG] -- end configuration --
[WARNING] JAR will be empty - no content was marked for inclusion!
[DEBUG] isUp2date: false (Destination \test\target\test-1.0-SNAPSHOT.jar not 
found.)
[INFO] Building jar: \test\target\test-1.0-SNAPSHOT.jar
[DEBUG] adding directory META-INF/
[DEBUG] adding entry META-INF/MANIFEST.MF
[DEBUG] adding directory META-INF/maven/
[DEBUG] adding directory META-INF/maven/com.mycompany.app/
[DEBUG] adding directory META-INF/maven/com.mycompany.app/test/
[DEBUG] adding entry META-INF/maven/com.mycompany.app/test/pom.xml
[DEBUG] adding entry META-INF/maven/com.mycompany.app/test/pom.properties
[INFO]
[INFO] --- apache-rat-plugin:0.11:check (default) @ test ---
[DEBUG] org.apache.rat:apache-rat-plugin:jar:0.11:
[DEBUG]org.apache.rat:apache-rat-core:jar:0.11:compile
[DEBUG]   commons-collections:commons-collections:jar:3.2.1:compile
[DEBUG]   commons-lang:commons-lang:jar:2.6:compile
[DEBUG]   commons-io:commons-io:jar:2.2:compile
[DEBUG]   org.apache.commons:commons-compress:jar:1.5:compile
[DEBUG]   commons-cli:commons-cli:jar:1.2:compile
[DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile
[DEBUG

[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-tabpanelfocusedCommentId=14323329#comment-14323329
]

Philipp Ottlinger commented on RAT-190:
---

Ok - now we've got the culprit :-)

Since RAT is agnostic of file encodings or environment settings it relies on
the underlying operating system/JDK settings and the encoding of the file
itself - I find this behaviour consistent with other command-line tools .
what would you prefer - some output like:
{code}
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e.
build is platform dependent!
or
[WARNING] File encoding has not been set, using platform encoding cp1292, i.e.
build is platform dependent!
{code}

Would that be helpful?

False negatives(?) in apache rat license checking
-

--
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-tabpanelfocusedCommentId=14323338#comment-14323338
]

Dan Dumont commented on RAT-190:

Well. The warnings are great.

But there's no valid license in the file, and when RAT scans it, it's passed if
the encodings are different.
Even a warning here doesn't make sense to me... the plugin is supposed to
audit my release, if it can't scan a file it should fail on it because it can't
do the audit.

False negatives(?) in apache rat license checking
-

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (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-tabpanelfocusedCommentId=14323338#comment-14323338
 ] 

Dan Dumont edited comment on RAT-190 at 2/16/15 9:40 PM:
-

But there's no valid license in the file, and when RAT scans it, it's passed if 
the encodings are different.
Even a warning here doesn't make sense to me...   the plugin is supposed to 
audit my release, if it can't scan a file it should fail on it because it can't 
do the audit.


was (Author: ddumont):
Well.   The warnings are great.

But there's no valid license in the file, and when RAT scans it, it's passed if 
the encodings are different.
Even a warning here doesn't make sense to me...   the plugin is supposed to 
audit my release, if it can't scan a file it should fail on it because it can't 
do the audit.

 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
Assignee: Philipp Ottlinger
 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:
 licenses
   license 
 implementation=org.apache.rat.analysis.license.SimplePatternBasedLicense
 licenseFamilyCategoryIBMCL/licenseFamilyCategory
 licenseFamilyNameIBM Copyright/licenseFamilyName
 notes/notes
 patterns
   patternCopyright IBM Corp. 2015/pattern
   patternCopyright IBM Corp. 2014, 2015/pattern
   patternCopyright IBM Corp. 2013, 2015/pattern
 /patterns
   /license
 /licenses
 licenseFamilies
   licenseFamily implementation=org.apache.rat.license.SimpleLicenseFamily
   familyNameIBM Copyright/familyName
 /licenseFamily
 /licenseFamilies
 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] [Comment Edited] (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-tabpanelfocusedCommentId=14323260#comment-14323260
 ] 

Dan Dumont edited comment on RAT-190 at 2/16/15 8:46 PM:
-

Here's some debug (-X) output if it helps

{code}
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
08:51:28-0500)
Maven home: C:\apache-maven-3.0.5\bin\..
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_21\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 8, version: 6.2, arch: amd64, family: windows
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from 
C:\apache-maven-3.0.5\bin\..\conf\settings.xml
[DEBUG] Reading user settings from C:\Users\ddumont\.m2\settings.xml
[DEBUG] Using local repository at C:\Users\ddumont\.m2\repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for 
C:\Users\ddumont\.m2\repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project com.mycompany.app:test:jar:1.0-SNAPSHOT: 
(none)
[DEBUG] Looking up lifecyle mappings for packaging jar from 
ClassRealm[plexus.core, parent: null]
[DEBUG] === REACTOR BUILD PLAN 
[DEBUG] Project: com.mycompany.app:test:jar:1.0-SNAPSHOT
[DEBUG] Tasks:   [clean, install]
[DEBUG] Style:   Regular
[DEBUG] ===
[INFO] 
[INFO] 
[INFO] Building test 1.0-SNAPSHOT
[INFO] 
[DEBUG] Lifecycle default - [validate, initialize, generate-sources, 
process-sources, generate-resources, process-resources, compile, 
process-classes, generate-test-sources, process-test-sources, 
generate-test-resources, process-test-resources, test-compile, 
process-test-classes, test, prepare-package, package, pre-integration-test, 
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources, 
process-sources, generate-resources, process-resources, compile, 
process-classes, generate-test-sources, process-test-sources, 
generate-test-resources, process-test-resources, test-compile, 
process-test-classes, test, prepare-package, package, pre-integration-test, 
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources, 
process-sources, generate-resources, process-resources, compile, 
process-classes, generate-test-sources, process-test-sources, 
generate-test-resources, process-test-resources, test-compile, 
process-test-classes, test, prepare-package, package, pre-integration-test, 
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources, 
process-sources, generate-resources, process-resources, compile, 
process-classes, generate-test-sources, process-test-sources, 
generate-test-resources, process-test-resources, test-compile, 
process-test-classes, test, prepare-package, package, pre-integration-test, 
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources, 
process-sources, generate-resources, process-resources, compile, 
process-classes, generate-test-sources, process-test-sources, 
generate-test-resources, process-test-resources, test-compile, 
process-test-classes, test, prepare-package, package, pre-integration-test, 
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default - [validate, initialize, generate-sources, 
process-sources, generate-resources, process-resources, compile, 
process-classes, generate-test-sources, process-test-sources, 
generate-test-resources, process-test-resources, test-compile, 
process-test-classes, test, prepare-package, package, pre-integration-test, 
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean - [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site - [pre-site, site, post-site, site-deploy]
[DEBUG

[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-tabpanelfocusedCommentId=14323286#comment-14323286
]

Dan Dumont commented on RAT-190:

I also tried deleting my ~/.m2/repository and running a build with a modern
maven. Same result.

False negatives(?) in apache rat license checking
-

--
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-tabpanelfocusedCommentId=14323318#comment-14323318
 ] 

Philipp Ottlinger commented on RAT-190:
---

I'm not sure if that changes anything, but checked the file itself - the JS 
seems to be UTF-8. I'm not sure if your operating system handles it correctly 
during RAT-parsing. Here's the output of file:
{code}
$ file MailComposeView.js 
MailComposeView.js: UTF-8 Unicode text, with CRLF line terminators
{code}

I meant to change the mvn encoding settings; I assume that the pom's encoding 
has nothing to do with the maven encoding if mvn itself is running. Can you 
manage to get UTF-8 when calling this:
{code}
$ mvn --version

Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 
2014-12-14T18:29:23+01:00)
Maven home: /home/user/software/maven
Java version: 1.8.0_31, vendor: Oracle Corporation
Java home: /home/user/jdk1.8.0_31/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: linux, version: 3.13.0-46-generic, arch: amd64, family: unix
{code}
You had this CP-something encoding as platform encoding.

Please also try out if 
{code}
mvn --U -Dfile.encoding=UTF-8
{code}
changes anything.


 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
Assignee: Philipp Ottlinger
 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:
 licenses
   license 
 implementation=org.apache.rat.analysis.license.SimplePatternBasedLicense
 licenseFamilyCategoryIBMCL/licenseFamilyCategory
 licenseFamilyNameIBM Copyright/licenseFamilyName
 notes/notes
 patterns
   patternCopyright IBM Corp. 2015/pattern
   patternCopyright IBM Corp. 2014, 2015/pattern
   patternCopyright IBM Corp. 2013, 2015/pattern
 /patterns
   /license
 /licenses
 licenseFamilies
   licenseFamily implementation=org.apache.rat.license.SimpleLicenseFamily
   familyNameIBM Copyright/familyName
 /licenseFamily
 /licenseFamilies
 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-tabpanelfocusedCommentId=14323274#comment-14323274
 ] 

Philipp Ottlinger commented on RAT-190:
---

Thanks for the last output - your dependency tree looks rather old, my mvn 
invokes a much newer maven-jar-plugin. Not sure if that has to do with the 
problems you experience. Since all builds on Jenkins are green I do not suspect 
a general problem:

My invocation yields
{code}
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ test ---
[DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=0, 
ConflictMarker.markTime=0, ConflictMarker.nodeCount=74, 
ConflictIdSorter.graphTime=0, ConflictIdSorter.topsortTime=0, 
ConflictIdSorter.conflictIdCount=28, ConflictIdSorter.conflictIdCycleCount=0, 
ConflictResolver.totalTime=2, ConflictResolver.conflictItemCount=70, 
DefaultDependencyCollector.collectTime=17, 
DefaultDependencyCollector.transformTime=2}
[DEBUG] org.apache.maven.plugins:maven-jar-plugin:jar:2.4:
[DEBUG]org.apache.maven:maven-plugin-api:jar:2.0.6:compile
[DEBUG]org.apache.maven:maven-project:jar:2.0.6:compile
[DEBUG]   org.apache.maven:maven-settings:jar:2.0.6:compile
[DEBUG]   org.apache.maven:maven-profile:jar:2.0.6:compile
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0.6:compile
[DEBUG]  org.apache.maven:maven-repository-metadata:jar:2.0.6:compile
[DEBUG]   org.apache.maven:maven-plugin-registry:jar:2.0.6:compile
[DEBUG]   
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
[DEBUG]  junit:junit:jar:3.8.1:compile
[DEBUG]  classworlds:classworlds:jar:1.1-alpha-2:compile
[DEBUG]org.apache.maven:maven-model:jar:2.0.6:runtime
[DEBUG]org.apache.maven:maven-artifact:jar:2.0.6:compile
[DEBUG]org.apache.maven:maven-archiver:jar:2.5:compile
[DEBUG]   org.apache.maven:maven-core:jar:2.0.6:compile
[DEBUG]  
org.apache.maven:maven-plugin-parameter-documenter:jar:2.0.6:compile
[DEBUG]  
org.apache.maven.reporting:maven-reporting-api:jar:2.0.6:compile
[DEBUG] 
org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-7:compile
[DEBUG]  org.apache.maven:maven-error-diagnostics:jar:2.0.6:compile
[DEBUG]  commons-cli:commons-cli:jar:1.0:compile
[DEBUG]  org.apache.maven:maven-plugin-descriptor:jar:2.0.6:compile
[DEBUG]  
org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4:compile
[DEBUG]  org.apache.maven:maven-monitor:jar:2.0.6:compile
[DEBUG]   org.codehaus.plexus:plexus-interpolation:jar:1.15:compile
[DEBUG]org.codehaus.plexus:plexus-archiver:jar:2.1:compile
[DEBUG]   org.codehaus.plexus:plexus-io:jar:2.0.2:compile
[DEBUG]commons-lang:commons-lang:jar:2.1:compile
[DEBUG]org.codehaus.plexus:plexus-utils:jar:3.0:compile
[DEBUG] Created new class realm 
pluginorg.apache.maven.plugins:maven-jar-plugin:2.4
[DEBUG] Importing foreign packages into class realm 
pluginorg.apache.maven.plugins:maven-jar-plugin:2.4
[DEBUG]   Imported:   maven.api
[DEBUG] Populating class realm 
pluginorg.apache.maven.plugins:maven-jar-plugin:2.4
[DEBUG]   Included: org.apache.maven.plugins:maven-jar-plugin:jar:2.4
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.apache.maven:maven-archiver:jar:2.5
[DEBUG]   Included: org.apache.maven.reporting:maven-reporting-api:jar:2.0.6
[DEBUG]   Included: org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-7
[DEBUG]   Included: commons-cli:commons-cli:jar:1.0
[DEBUG]   Included: org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4
[DEBUG]   Included: org.codehaus.plexus:plexus-interpolation:jar:1.15
[DEBUG]   Included: org.codehaus.plexus:plexus-archiver:jar:2.1
[DEBUG]   Included: org.codehaus.plexus:plexus-io:jar:2.0.2
[DEBUG]   Included: commons-lang:commons-lang:jar:2.1
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:3.0
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG]   Excluded: 
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG]   Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-core:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-parameter-documenter:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-error-diagnostics:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-descriptor:jar

[jira] [Commented] (RAT-189) Excludes should support ** style paths

2015-01-13 Thread Jochen Wiedmann (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14275717#comment-14275717
 ] 

Jochen Wiedmann commented on RAT-189:
-

IMO, this should already be the case for the Maven Plugins, and the Ant Tasks, 
because both are using standard functionality of the respective parent (Maven, 
or Ant, respectively). Are you referring to the CLI?


 Excludes should support ** style paths
 --

 Key: RAT-189
 URL: https://issues.apache.org/jira/browse/RAT-189
 Project: Apache Rat
  Issue Type: New Feature
Reporter: Alex O'Ree

 It would be nice with the excludes/include path comparison supported ** and * 
 wildcards. It would make things much easier for filtering certains types of 
 files



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (RAT-189) Excludes should support ** style paths

2015-01-14 Thread Jochen Wiedmann (JIRA)


 [ 
https://issues.apache.org/jira/browse/RAT-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jochen Wiedmann closed RAT-189.
---

 Excludes should support ** style paths
 --

 Key: RAT-189
 URL: https://issues.apache.org/jira/browse/RAT-189
 Project: Apache Rat
  Issue Type: New Feature
Reporter: Alex O'Ree
Assignee: Jochen Wiedmann

 It would be nice with the excludes/include path comparison supported ** and * 
 wildcards. It would make things much easier for filtering certains types of 
 files



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (RAT-189) Excludes should support ** style paths

2015-01-14 Thread Jochen Wiedmann (JIRA)


 [ 
https://issues.apache.org/jira/browse/RAT-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jochen Wiedmann resolved RAT-189.
-
Resolution: Invalid
  Assignee: Jochen Wiedmann

 Excludes should support ** style paths
 --

 Key: RAT-189
 URL: https://issues.apache.org/jira/browse/RAT-189
 Project: Apache Rat
  Issue Type: New Feature
Reporter: Alex O'Ree
Assignee: Jochen Wiedmann

 It would be nice with the excludes/include path comparison supported ** and * 
 wildcards. It would make things much easier for filtering certains types of 
 files



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (RAT-158) SAXParser warnings

2015-02-15 Thread Philipp Ottlinger (JIRA)


 [ 
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
 Attachments: RAT-158.patch


 I have rat configured as such
 {code} plugin
  groupIdorg.apache.rat/groupId
  artifactIdapache-rat-plugin/artifactId
  inheritedfalse/inherited
  executions
execution
  phaseverify/phase
  goals
goalcheck/goal
  /goals
/execution
  /executions
  configuration
excludes
  exclude**/conf/**/exclude
/excludes
  /configuration
/plugin
 {code}
 And with every build where it triggers, I see 
 {code}
 Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 
 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
 recognized.
 Warning:  org.apache.xerces.parsers.SAXParser: Feature 
 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
 Warning:  org.apache.xerces.parsers.SAXParser: Property 
 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
 recognized.
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RAT-196) Let the parent do it's work and define only things which are really needed.

2015-03-15 Thread Philipp Ottlinger (JIRA)


 [ 
https://issues.apache.org/jira/browse/RAT-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philipp Ottlinger updated RAT-196:
--
Priority: Minor  (was: Critical)

 Let the parent do it's work and define only things which are really needed.
 ---

 Key: RAT-196
 URL: https://issues.apache.org/jira/browse/RAT-196
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor
 Fix For: 0.12

 Attachments: RAT-196.patch


 Currently there are defined many things which are already defined by 
 inheritance through the parent this makes the pom files larger than they need 
 to be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (RAT-196) Let the parent do it's work and define only things which are really needed.

2015-03-15 Thread Philipp Ottlinger (JIRA)


 [ 
https://issues.apache.org/jira/browse/RAT-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philipp Ottlinger resolved RAT-196.
---
Resolution: Fixed

Thanks :-) - 
committed as revision [1666840|http://svn.apache.org/r1666840].

 Let the parent do it's work and define only things which are really needed.
 ---

 Key: RAT-196
 URL: https://issues.apache.org/jira/browse/RAT-196
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Assignee: Philipp Ottlinger
Priority: Minor
 Fix For: 0.12

 Attachments: RAT-196.patch


 Currently there are defined many things which are already defined by 
 inheritance through the parent this makes the pom files larger than they need 
 to be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (RAT-196) Let the parent do it's work and define only things which are really needed.


[ 
https://issues.apache.org/jira/browse/RAT-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14359295#comment-14359295
 ] 

Karl Heinz Marbaise edited comment on RAT-196 at 3/12/15 8:09 PM:
--

Attached patch to improve the pom files. Created against current trunk.


was (Author: khmarbaise):
Attached patch to improve the pom files. Created against 
[r1666284|http://svn.apache.org/r1666284]

 Let the parent do it's work and define only things which are really needed.
 ---

 Key: RAT-196
 URL: https://issues.apache.org/jira/browse/RAT-196
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Critical
 Fix For: 0.12

 Attachments: RAT-196.patch


 Currently there are defined many things which are already defined by 
 inheritance through the header this makes the pom files larger than they need 
 to be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (RAT-196) Let the parent do it's work and define only things which are really needed.


[ 
https://issues.apache.org/jira/browse/RAT-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14359295#comment-14359295
 ] 

Karl Heinz Marbaise edited comment on RAT-196 at 3/12/15 8:08 PM:
--

Attached patch to improve the pom files. Created against 
[r1666284|http://svn.apache.org/r1666284]


was (Author: khmarbaise):
Attached patch to improve the pom files.

 Let the parent do it's work and define only things which are really needed.
 ---

 Key: RAT-196
 URL: https://issues.apache.org/jira/browse/RAT-196
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Critical
 Fix For: 0.12

 Attachments: RAT-196.patch


 Currently there are defined many things which are already defined by 
 inheritance through the header this makes the pom files larger than they need 
 to be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RAT-196) Let the parent do it's work and define only things which are really needed.


 [ 
https://issues.apache.org/jira/browse/RAT-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated RAT-196:

Attachment: RAT-196.patch

Attached patch to improve the pom files.

 Let the parent do it's work and define only things which are really needed.
 ---

 Key: RAT-196
 URL: https://issues.apache.org/jira/browse/RAT-196
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Critical
 Fix For: 0.12

 Attachments: RAT-196.patch


 Currently there are defined many things which are already defined by 
 inheritance through the header this makes the pom files larger than they need 
 to be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RAT-196) Let the parent do it's work and define only things which are really needed.


 [ 
https://issues.apache.org/jira/browse/RAT-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated RAT-196:

Description: Currently there are defined many things which are already 
defined by inheritance through the parent this makes the pom files larger than 
they need to be.  (was: Currently there are defined many things which are 
already defined by inheritance through the header this makes the pom files 
larger than they need to be.)

 Let the parent do it's work and define only things which are really needed.
 ---

 Key: RAT-196
 URL: https://issues.apache.org/jira/browse/RAT-196
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Critical
 Fix For: 0.12

 Attachments: RAT-196.patch


 Currently there are defined many things which are already defined by 
 inheritance through the parent this makes the pom files larger than they need 
 to be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (RAT-197) Exclude the new .mvn/ folder from rat checked

2015-03-25 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created RAT-197:
---

 Summary: Exclude the new .mvn/ folder from rat checked
 Key: RAT-197
 URL: https://issues.apache.org/jira/browse/RAT-197
 Project: Apache Rat
  Issue Type: Improvement
Reporter: Karl Heinz Marbaise
 Fix For: 0.12


Starting with Maven 3.3.1 a new folder .mvn has been introduced which contains 
extensions.xml, jvm.config and maven.config. The jvm.config and maven.config do 
not support any kind of comment.
So best would be to exclude those folder completely from rat checks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-197) Exclude the new .mvn/ folder from rat checked

2015-03-25 Thread Jochen Wiedmann (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14379988#comment-14379988
 ] 

Jochen Wiedmann commented on RAT-197:
-

The best way to do this will most likely be to upgrade the proper Plexus 
components that provides the default set.


 Exclude the new .mvn/ folder from rat checked
 -

 Key: RAT-197
 URL: https://issues.apache.org/jira/browse/RAT-197
 Project: Apache Rat
  Issue Type: Improvement
Reporter: Karl Heinz Marbaise
 Fix For: 0.12


 Starting with Maven 3.3.1 a new folder .mvn has been introduced which 
 contains extensions.xml, jvm.config and maven.config. The jvm.config and 
 maven.config do not support any kind of comment.
 So best would be to exclude those folder completely from rat checks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RAT-197) Exclude the new .mvn/ folder from rat checked

2015-03-25 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/RAT-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated RAT-197:

Attachment: RAT-197.patch

 Exclude the new .mvn/ folder from rat checked
 -

 Key: RAT-197
 URL: https://issues.apache.org/jira/browse/RAT-197
 Project: Apache Rat
  Issue Type: Improvement
Reporter: Karl Heinz Marbaise
 Fix For: 0.12

 Attachments: RAT-197.patch


 Starting with Maven 3.3.1 a new folder .mvn has been introduced which 
 contains extensions.xml, jvm.config and maven.config. The jvm.config and 
 maven.config do not support any kind of comment.
 So best would be to exclude those folder completely from rat checks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (RAT-198) Upgrade plexus-utils to 3.0.20

2015-03-25 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created RAT-198:
---

 Summary: Upgrade plexus-utils to 3.0.20
 Key: RAT-198
 URL: https://issues.apache.org/jira/browse/RAT-198
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor
 Fix For: 0.12






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-198) Upgrade plexus-utils to 3.0.20

2015-03-26 Thread Jochen Wiedmann (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381764#comment-14381764
 ] 

Jochen Wiedmann commented on RAT-198:
-

Then: What are the advantages (if any) of the upgrade?


 Upgrade plexus-utils to 3.0.20
 --

 Key: RAT-198
 URL: https://issues.apache.org/jira/browse/RAT-198
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor
 Fix For: 0.12

 Attachments: RAT-198.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (RAT-197) Exclude the new .mvn/ folder from rat checked

2015-03-26 Thread Philipp Ottlinger (JIRA)


 [ 
https://issues.apache.org/jira/browse/RAT-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philipp Ottlinger resolved RAT-197.
---
Resolution: Fixed
  Assignee: Philipp Ottlinger

Thanks for the patch, applied in rev [1669332|http://svn.apache.org/r1669332]

 Exclude the new .mvn/ folder from rat checked
 -

 Key: RAT-197
 URL: https://issues.apache.org/jira/browse/RAT-197
 Project: Apache Rat
  Issue Type: Improvement
Reporter: Karl Heinz Marbaise
Assignee: Philipp Ottlinger
 Fix For: 0.12

 Attachments: RAT-197.patch


 Starting with Maven 3.3.1 a new folder .mvn has been introduced which 
 contains extensions.xml, jvm.config and maven.config. The jvm.config and 
 maven.config do not support any kind of comment.
 So best would be to exclude those folder completely from rat checks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-198) Upgrade plexus-utils to 3.0.20

2015-03-26 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381762#comment-14381762
 ] 

Karl Heinz Marbaise commented on RAT-198:
-

Absolutely no relationship.

 Upgrade plexus-utils to 3.0.20
 --

 Key: RAT-198
 URL: https://issues.apache.org/jira/browse/RAT-198
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor
 Fix For: 0.12

 Attachments: RAT-198.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-197) Exclude the new .mvn/ folder from rat checked

2015-03-26 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381763#comment-14381763
 ] 

Karl Heinz Marbaise commented on RAT-197:
-

The plexus component has no relationship to this, cause .mvn folder is 
identified by the mvn/mvn.cmd script and must be cause the jvm parameters 
couldn't be set there.

 Exclude the new .mvn/ folder from rat checked
 -

 Key: RAT-197
 URL: https://issues.apache.org/jira/browse/RAT-197
 Project: Apache Rat
  Issue Type: Improvement
Reporter: Karl Heinz Marbaise
 Fix For: 0.12

 Attachments: RAT-197.patch


 Starting with Maven 3.3.1 a new folder .mvn has been introduced which 
 contains extensions.xml, jvm.config and maven.config. The jvm.config and 
 maven.config do not support any kind of comment.
 So best would be to exclude those folder completely from rat checks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (RAT-198) Upgrade plexus-utils to 3.0.20

2015-03-26 Thread Philipp Ottlinger (JIRA)


 [ 
https://issues.apache.org/jira/browse/RAT-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philipp Ottlinger resolved RAT-198.
---
Resolution: Fixed
  Assignee: Philipp Ottlinger

Thanks, committed as [rev1669330|http://svn.apache.org/r1669330].

 Upgrade plexus-utils to 3.0.20
 --

 Key: RAT-198
 URL: https://issues.apache.org/jira/browse/RAT-198
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Assignee: Philipp Ottlinger
Priority: Minor
 Fix For: 0.12

 Attachments: RAT-198.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (RAT-195) Merge GSOC from branch onto head

2015-02-23 Thread Philipp Ottlinger (JIRA)


 [ 
https://issues.apache.org/jira/browse/RAT-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philipp Ottlinger reassigned RAT-195:
-

Assignee: Philipp Ottlinger

 Merge GSOC from branch onto head
 

 Key: RAT-195
 URL: https://issues.apache.org/jira/browse/RAT-195
 Project: Apache Rat
  Issue Type: Improvement
Affects Versions: 0.12
Reporter: Philipp Ottlinger
Assignee: Philipp Ottlinger

 Since there haven't been any objections (mailthread: 2014-07-31 22:18) I will 
 start to merge changes from GSOC into head - 
 source branch is 
 {code}
 http://svn.apache.org/viewvc/creadur/rat/branches/gsoc/
 {code}
 Target is:
 {code}
 http://svn.apache.org/viewvc/creadur/rat/trunk/
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (RAT-195) Merge GSOC from branch onto head

2015-02-23 Thread Philipp Ottlinger (JIRA)

Philipp Ottlinger created RAT-195:
-

 Summary: Merge GSOC from branch onto head
 Key: RAT-195
 URL: https://issues.apache.org/jira/browse/RAT-195
 Project: Apache Rat
  Issue Type: Improvement
Affects Versions: 0.12
Reporter: Philipp Ottlinger


Since there haven't been any objections (mailthread: 2014-07-31 22:18) I will 
start to merge changes from GSOC into head - 
source branch is 
{code}
http://svn.apache.org/viewvc/creadur/rat/branches/gsoc/
{code}
Target is:
{code}
http://svn.apache.org/viewvc/creadur/rat/trunk/
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RAT-195) Merge GSOC from branch onto head/TRUNK

2015-02-23 Thread Philipp Ottlinger (JIRA)


 [ 
https://issues.apache.org/jira/browse/RAT-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philipp Ottlinger updated RAT-195:
--
Summary: Merge GSOC from branch onto head/TRUNK  (was: Merge GSOC from 
branch onto head)

 Merge GSOC from branch onto head/TRUNK
 --

 Key: RAT-195
 URL: https://issues.apache.org/jira/browse/RAT-195
 Project: Apache Rat
  Issue Type: Improvement
Affects Versions: 0.12
Reporter: Philipp Ottlinger
Assignee: Philipp Ottlinger

 Since there haven't been any objections (mailthread: 2014-07-31 22:18) I will 
 start to merge changes from GSOC into head - 
 source branch is 
 {code}
 http://svn.apache.org/viewvc/creadur/rat/branches/gsoc/
 {code}
 Target is:
 {code}
 http://svn.apache.org/viewvc/creadur/rat/trunk/
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-199) Support for m2e in Eclipse

2015-03-27 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384510#comment-14384510
 ] 

Karl Heinz Marbaise commented on RAT-199:
-

No no...The mapping file can be put into 
{{src/main/resources/META-INF/m2e/lifecycle-mapping-metadata.xml}} and will be 
packaged with  plugin and use the plexus build api:

{code}
dependency
groupIdorg.sonatype.plexus/groupId
artifactIdplexus-build-api/artifactId
version0.0.7/version
/dependency
{code}
And of course it's needed to do some things within the code...add supplemental 
steps to trigger Eclipse...

 Support for m2e in Eclipse
 --

 Key: RAT-199
 URL: https://issues.apache.org/jira/browse/RAT-199
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor

 I would like to see support for m2e in Eclipse.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-199) Support for m2e in Eclipse

2015-03-27 Thread Jochen Wiedmann (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384466#comment-14384466
 ] 

Jochen Wiedmann commented on RAT-199:
-

What do you expect? An M2E connector that advises M2E how to handle the 
maven-rat-plugin? Or, what else?


 Support for m2e in Eclipse
 --

 Key: RAT-199
 URL: https://issues.apache.org/jira/browse/RAT-199
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor

 I would like to see support for m2e in Eclipse.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-199) Support for m2e in Eclipse

2015-03-27 Thread Jochen Wiedmann (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384490#comment-14384490
 ] 

Jochen Wiedmann commented on RAT-199:
-

As I guessed, you'd like to see a connector. Unfortunately, that doesn't 
require Maven k now how (which I have), but Eclipse (or perhaps even M2E) know 
how.


 Support for m2e in Eclipse
 --

 Key: RAT-199
 URL: https://issues.apache.org/jira/browse/RAT-199
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor

 I would like to see support for m2e in Eclipse.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-199) Support for m2e in Eclipse

2015-03-27 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384477#comment-14384477
 ] 

Karl Heinz Marbaise commented on RAT-199:
-

May be i wasn't clear enough...I would like create support in Eclipse to 
prevent messages about not being covered by life cycle and some handling of 
this within the maven-rat-plugin..the simplest step of this is to provide a 
life cycle mapper for Eclipse:
{code}
?xml version=1.0 encoding=UTF-8?
lifecycleMappingMetadata
  pluginExecutions
pluginExecution
  pluginExecutionFilter
goals
  goalcheck/goal
/goals
  /pluginExecutionFilter
  action
execute
  runOnIncrementaltrue/runOnIncremental
  runOnConfigurationtrue/runOnConfiguration
/execute
  /action
/pluginExecution
  /pluginExecutions
/lifecycleMappingMetadata
{code}
But i know that's not enough...


 Support for m2e in Eclipse
 --

 Key: RAT-199
 URL: https://issues.apache.org/jira/browse/RAT-199
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor

 I would like to see support for m2e in Eclipse.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (RAT-199) Support for m2e in Eclipse

2015-03-27 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created RAT-199:
---

 Summary: Support for m2e in Eclipse
 Key: RAT-199
 URL: https://issues.apache.org/jira/browse/RAT-199
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor


I would like to see support for m2e in Eclipse.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-198) Upgrade plexus-utils to 3.0.20

2015-03-26 Thread Jochen Wiedmann (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381466#comment-14381466
 ] 

Jochen Wiedmann commented on RAT-198:
-

Is this related to RAT-197 (see my comment in that issue)?


 Upgrade plexus-utils to 3.0.20
 --

 Key: RAT-198
 URL: https://issues.apache.org/jira/browse/RAT-198
 Project: Apache Rat
  Issue Type: Improvement
  Components: maven
Affects Versions: 0.12
Reporter: Karl Heinz Marbaise
Priority: Minor
 Fix For: 0.12

 Attachments: RAT-198.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-189) Excludes should support ** style paths

2015-01-13 Thread Philipp Ottlinger (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276016#comment-14276016
 ] 

Philipp Ottlinger commented on RAT-189:
---

Please provide more context - some other projects already use the wildcard 
annotation such as 
https://github.com/apache/mahout/blob/master/pom.xml

{code}
 excludes
exclude**/*.conf/exclude
exclude**/*.iml/exclude
exclude**/*.md/exclude
exclude**/*.props/exclude
exclude**/gen/**/exclude
exclude**/resources/**/exclude
exclude**/images/**/exclude
exclude**/target/**/exclude
exclude**/testdata/**/exclude
exclude**/.idea/**/exclude
exclude**/package-info.java/exclude
exclude**/.git/**/exclude
exclude**/.classpath/exclude
exclude**/.project/exclude
exclude**/.settings/**/exclude
exclude**/*.patch/exclude
  /excludes 
{code}

Is that what you are referring to?

 Excludes should support ** style paths
 --

 Key: RAT-189
 URL: https://issues.apache.org/jira/browse/RAT-189
 Project: Apache Rat
  Issue Type: New Feature
Reporter: Alex O'Ree

 It would be nice with the excludes/include path comparison supported ** and * 
 wildcards. It would make things much easier for filtering certains types of 
 files



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-189) Excludes should support ** style paths

2015-01-13 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/RAT-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14276200#comment-14276200
 ] 

Alex O'Ree commented on RAT-189:


Yes I tried something similar to that (applied to the parent pom) and was 
unable to get the exclusions to work in either the parent pom for the child 
projects. 

Now that I've seen the sample, I was able to get it to work. I had the syntax 
wrong. One action to take out of this is to update the web site's example for 
poms to have some additional details. I didn't see anywhere that wildcards were 
supported or how to specific exclusions via pom. Thanks for the quick response 

 Excludes should support ** style paths
 --

 Key: RAT-189
 URL: https://issues.apache.org/jira/browse/RAT-189
 Project: Apache Rat
  Issue Type: New Feature
Reporter: Alex O'Ree

 It would be nice with the excludes/include path comparison supported ** and * 
 wildcards. It would make things much easier for filtering certains types of 
 files



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RAT-171) Allow exclude patterns to be read from a file or files

[
https://issues.apache.org/jira/browse/RAT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Philipp Ottlinger updated RAT-171:
--
Description:
The apache-rat-plugin ignores by default the .gitignore files. However, for
every file/pattern added to those files, an explicit exclusion must be set in
the plugin's configuration.
Given that git-ignored files won't be uploaded to the SCM and shouldn't be part
of a release, it would be nice that the apache-rat-plugin automatically
considered those git-ignored files as implicit exclusions.

h3. Example usage
Either configure parsing SCM ignore files by a environment variable
{code}
mvn -U -debug -Drat.parseSCMIgnoresAsExcludes=true
{code}
or in your configuration section of apache-rat-maven plugin
{code}
parseSCMIgnoresAsExcludestrue/true

This features is enabled by default.

was:
The apache-rat-plugin ignores by default the .gitignore files. However, for
every file/pattern added to those files, an explicit exclusion must be set in
the plugin's configuration.
Given that git-ignored files won't be uploaded to the SCM and shouldn't be part
of a release, it would be nice that the apache-rat-plugin automatically
considered those git-ignored files as implicit exclusions.

As if now this feature is not enabled by default.

Allow exclude patterns to be read from a file or files
--

Key: RAT-171
URL: https://issues.apache.org/jira/browse/RAT-171
Project: Apache Rat
Issue Type: New Feature
Affects Versions: 0.11
Reporter: Ignasi Barrera
Assignee: Philipp Ottlinger
Attachments: RAT-171.patch

The apache-rat-plugin ignores by default the .gitignore files. However, for
every file/pattern added to those files, an explicit exclusion must be set in
the plugin's configuration.
Given that git-ignored files won't be uploaded to the SCM and shouldn't be
part of a release, it would be nice that the apache-rat-plugin automatically
considered those git-ignored files as implicit exclusions.
h3. Example usage
Either configure parsing SCM ignore files by a environment variable
{code}
mvn -U -debug -Drat.parseSCMIgnoresAsExcludes=true
{code}
or in your configuration section of apache-rat-maven plugin
{code}
parseSCMIgnoresAsExcludestrue/true
This features is enabled by default.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RAT-171) Allow exclude patterns to be read from a file or files

[
https://issues.apache.org/jira/browse/RAT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Philipp Ottlinger updated RAT-171:
--
Description:
h3. Context
The apache-rat-plugin ignores by default the .gitignore files. However, for
every file/pattern added to those files, an explicit exclusion must be set in
the plugin's configuration.
Given that git-ignored files won't be uploaded to the SCM and shouldn't be part
of a release, it would be nice that the apache-rat-plugin automatically
considered those git-ignored files as implicit exclusions.

h3. Implemented for
Currently implemented for the following soure code management systems:
* SVN
* Git
* Bazaar
* Mercurial and
* CVS.

h3. Example usage
You can configure parsing SCM ignore files by a environment variable
{code}
mvn -U -debug -Drat.parseSCMIgnoresAsExcludes=true
{code}
or in your configuration section of apache-rat-maven plugin
{code}
parseSCMIgnoresAsExcludestrue/true

This features is enabled by default.

In case you want to speed up the build you may disable it and set it to false.

This features is enabled by default.

Allow exclude patterns to be read from a file or files
--

h3. Context
The apache-rat-plugin ignores by default the .gitignore files. However, for
every file/pattern added to those files, an explicit exclusion must be set in
the plugin's configuration.
Given that git-ignored files won't be uploaded to the SCM and shouldn't be
part of a release, it would be nice that the apache-rat-plugin automatically
considered those git-ignored files as implicit exclusions.
h3. Implemented for
Currently implemented for the following soure code management systems:
* SVN
* Git
* Bazaar
* Mercurial and
* CVS.
h3. Example usage
You can configure parsing SCM ignore files by a environment variable
{code}
mvn -U -debug -Drat.parseSCMIgnoresAsExcludes=true
{code}
or in your configuration section of apache-rat-maven plugin
{code}
parseSCMIgnoresAsExcludestrue/true
This features is enabled by default.
In case you want to speed up the build you may disable it and set it to false.

--
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-tabpanelfocusedCommentId=14492925#comment-14492925
 ] 

Philipp Ottlinger commented on RAT-161:
---

[~eje] is the ticket still relevant? I see that SPARK-1493 is fixed. Does your 
request still make sense?

To my mind it rather makes the exclusions configuration even more complex than 
it already is, which is why I'm in favour of closing your ticket.

Thanks for feedback.

 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
Priority: Minor
 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] [Updated] (RAT-171) Allow exclude patterns to be read from a file or files

[
https://issues.apache.org/jira/browse/RAT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

h3. Implemented for
Currently implemented for the following soure code management systems:
* SVN
* Git
* Bazaar
* Mercurial and
* CVS.

This features is enabled by default.

In case you want to speed up the build you may disable it and set it to
{code}
false
{code}
.

was:
h3. Context
The apache-rat-plugin ignores by default the .gitignore files. However, for
every file/pattern added to those files, an explicit exclusion must be set in
the plugin's configuration.
Given that git-ignored files won't be uploaded to the SCM and shouldn't be part
of a release, it would be nice that the apache-rat-plugin automatically
considered those git-ignored files as implicit exclusions.

h3. Implemented for
Currently implemented for the following soure code management systems:
* SVN
* Git
* Bazaar
* Mercurial and
* CVS.

This features is enabled by default.

In case you want to speed up the build you may disable it and set it to false.

Allow exclude patterns to be read from a file or files
--

Key: RAT-171
URL: https://issues.apache.org/jira/browse/RAT-171
Project: Apache Rat
Issue Type: New Feature
Affects Versions: 0.11
Reporter: Ignasi Barrera
Assignee: Philipp Ottlinger
Fix For: 0.12

Attachments: RAT-171.patch

h3. Context
The apache-rat-plugin ignores by default the .gitignore files. However, for
every file/pattern added to those files, an explicit exclusion must be set in
the plugin's configuration.
Given that git-ignored files won't be uploaded to the SCM and shouldn't be
part of a release, it would be nice that the apache-rat-plugin automatically
considered those git-ignored files as implicit exclusions.
h3. Implemented for
Currently implemented for the following soure code management systems:
* SVN
* Git
* Bazaar
* Mercurial and
* CVS.
h3. Example usage
You can configure parsing SCM ignore files by a environment variable
{code}
mvn -U -debug -Drat.parseSCMIgnoresAsExcludes=true
{code}
or in your configuration section of apache-rat-maven plugin
{code}
parseSCMIgnoresAsExcludestrue/true
{code}
This features is enabled by default.
In case you want to speed up the build you may disable it and set it to
{code}
false
{code}
.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-171) Allow exclude patterns to be read from a file or files

[
https://issues.apache.org/jira/browse/RAT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492848#comment-14492848
]

Philipp Ottlinger commented on RAT-171:
---

Thanks for your feedback - I've enabled the feature by default and added some
more documentation and an integration test that generates parsing errors to
proof the features usability on user-generated input.

Done in [1673261|http://svn.apache.org/r1673261]

Allow exclude patterns to be read from a file or files
--

Key: RAT-171
URL: https://issues.apache.org/jira/browse/RAT-171
Project: Apache Rat
Issue Type: New Feature
Affects Versions: 0.11
Reporter: Ignasi Barrera
Assignee: Philipp Ottlinger
Fix For: 0.12

Attachments: RAT-171.patch

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (RAT-171) Allow exclude patterns to be read from a file or files

[
https://issues.apache.org/jira/browse/RAT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Philipp Ottlinger resolved RAT-171.
---
Resolution: Fixed
Fix Version/s: 0.12

Allow exclude patterns to be read from a file or files
--

Key: RAT-171
URL: https://issues.apache.org/jira/browse/RAT-171
Project: Apache Rat
Issue Type: New Feature
Affects Versions: 0.11
Reporter: Ignasi Barrera
Assignee: Philipp Ottlinger
Fix For: 0.12

Attachments: RAT-171.patch

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (RAT-157) Use the *ignore file for the SCM to determine excludes


 [ 
https://issues.apache.org/jira/browse/RAT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philipp Ottlinger updated RAT-157:
--
Fix Version/s: 0.12

 Use the *ignore file for the SCM to determine excludes
 --

 Key: RAT-157
 URL: https://issues.apache.org/jira/browse/RAT-157
 Project: Apache Rat
  Issue Type: New Feature
Reporter: lucas theisen
Assignee: Philipp Ottlinger
Priority: Minor
 Fix For: 0.12


 As I understand it, RAT is used to ensure the LICENSE text is in all source 
 files.  Anything ignored by SCM is not technically a source file.  These 
 other files are usually specific to the developer environment.  And the 
 developer will already be adding such files to their own `SCMignore`.  
 Perhaps a pluggable ingore mechanism that could have an implementation per 
 SCM and would know how to parse that ignore and translate filter out all the 
 files it specifies.  Perhaps this could be an option to the the rat config 
 `useGitIgnore` or something.  What do you think?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (RAT-157) Use the *ignore file for the SCM to determine excludes


 [ 
https://issues.apache.org/jira/browse/RAT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philipp Ottlinger resolved RAT-157.
---
Resolution: Fixed
  Assignee: Philipp Ottlinger

 Use the *ignore file for the SCM to determine excludes
 --

 Key: RAT-157
 URL: https://issues.apache.org/jira/browse/RAT-157
 Project: Apache Rat
  Issue Type: New Feature
Reporter: lucas theisen
Assignee: Philipp Ottlinger
Priority: Minor

 As I understand it, RAT is used to ensure the LICENSE text is in all source 
 files.  Anything ignored by SCM is not technically a source file.  These 
 other files are usually specific to the developer environment.  And the 
 developer will already be adding such files to their own `SCMignore`.  
 Perhaps a pluggable ingore mechanism that could have an implementation per 
 SCM and would know how to parse that ignore and translate filter out all the 
 files it specifies.  Perhaps this could be an option to the the rat config 
 `useGitIgnore` or something.  What do you think?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (RAT-157) Use the *ignore file for the SCM to determine excludes