[
https://issues.apache.org/jira/browse/RYA-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176753#comment-15176753
]
ASF GitHub Bot commented on RYA-7:
----------------------------------
Github user joshelser commented on the pull request:
https://github.com/apache/incubator-rya/pull/25#issuecomment-191501007
Looks like that was the bad license headers I found. Thanks for grabbing
those.
If you want to get Rya into a good place going forward, I'd recommend also
getting `mvn apache-rat:check` to run without errors. I stepped through it
(just removing the offending files) -- I only came across test files and
META-INF/service definitions (both of which are somewhat expected). For the
containing maven module, just add a pluginConfiguration entry in the pom.xml
adding exclusions for the files. After this (or maybe after the first release
-- so we have someone's eyes on it other than just mine), we can check off the
other copyright box.
> Various pom cleanups for the Apache move
> ----------------------------------------
>
> Key: RYA-7
> URL: https://issues.apache.org/jira/browse/RYA-7
> Project: Rya
> Issue Type: Task
> Reporter: Josh Elser
> Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>
> In working on RYA-5, I noticed a few things in the pom that I believe should
> be taken care of before a release.
> * Make the apache pom the parent (see https://maven.apache.org/pom/asf/)
> * Depend on Apache releases for Hadoop and ZooKeeper (and groovy?)
> * Make sure we're depending on the most recent bug-fix release for
> dependencies (e.g. upgrade from 1.6.2 to 1.6.4 for Accumulo)
> * Change groupId from {{mvn.rya}} to {{org.apache.rya}} for consistency with
> other Maven-based ASF projects
> * Set proper names for each maven module (instead of groupid.artifact). This
> isn't as critical to change for a release, but just is an easy thing to
> improve.
> * Fix SCM block in parent pom (points to incorrect repository).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
