[
https://issues.apache.org/jira/browse/AVRO-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727434#comment-14727434
]
Sean Busbey commented on AVRO-1722:
-----------------------------------
{code}
+ <exclude>share/rat-excludes.txt</exclude>
{code}
with the move from ant to the maven plugin, we don't need this file or the
associated exclusion now, right?
{code}
<!-- text documentation files -->
+ <exclude>CHANGES.txt</exclude>
+ <exclude>DIST_README.txt</exclude>
+ <exclude>lang/perl/Changes</exclude>
+ <exclude>lang/c/README.maintaining_win32.txt</exclude>
+ <exclude>lang/c/docs/index.txt</exclude>
+ <exclude>lang/csharp/README</exclude>
+
<exclude>lang/java/archetypes/avro-service-archetype/src/test/integration/projects/basic/archetype.properties</exclude>
<!-- used to generate user projects -->
{code}
is there a reason we can convert these to markdown and add a commented-out
license header?
{code}
+ <!-- version control files -->
+ <!-- may not be in the root folder if using git-svn -->
+ <exclude>**/.git/**</exclude>
+ <exclude>**/.gitignore</exclude>
+ <!-- build or test files -->
+ <exclude>**/target/**</exclude>
{code}
this ought to be getting excluded already via the plugin's default exclude
filter. is it currently failing?
> Fix licensing issues
> --------------------
>
> Key: AVRO-1722
> URL: https://issues.apache.org/jira/browse/AVRO-1722
> Project: Avro
> Issue Type: Task
> Components: build
> Affects Versions: 1.8.0
> Reporter: Ryan Blue
> Assignee: Ryan Blue
> Priority: Blocker
> Fix For: 1.8.0
>
>
> The 1.8.0 release vote turned up a lot of licensing issues that need to be
> fixed. We need to do a scrub of the licensing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
