GitHub user justinleet reopened a pull request:
https://github.com/apache/incubator-metron/pull/378
METRON-596 Eliminate Maven warnings from build
Moving the maven-jar-plugin to a global variable and updating it.
Removing a duplicate dependency that had both 'provided' and 'test' scope
(dropped 'test', because it's already covered by 'provided').
Changed ```${parent.version}``` to ```${project.parent.version}```
Ran ```mvn clean install``` to test.
Does anybody know if there's a way to force Maven to break the build if new
warnings are introduced? I'm not sure we'd actually want to do it, but at the
same time I do like having these sorts of things enforced.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/justinleet/incubator-metron METRON-596
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/378.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #378
----
commit 1c3c400611a6ccd0a9b5f10649f2adde8b792126
Author: justinjleet <justinjl...@gmail.com>
Date: 2016-11-29T20:26:31Z
Updating poms to eliminate warnings
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
