[GitHub] nickwallen opened a new pull request #1343: METRON-2010 Unable to Build Metron Due to Inaccessible Repository

[GitBox <gi...@apache.org>]

nickwallen opened a new pull request #1343: METRON-2010 Unable to Build Metron Due to Inaccessible Repository
URL: https://github.com/apache/metron/pull/1343
 
 
   It appears that the repository that we have configured to pull in the dependency `multiline-string` is no longer accessible.  I am unable to build Metron because of this.
   
   * The repository at `https://raw.github.com/benelog/multiline/master/maven-repository` is no longer accessible. I am not sure how long this repository has been inaccessible.
   
   * This likely went unnoticed for some period of time because the dependency is cached in most developer environments.  Once I cleared my Maven cache, I ran into this problem.
   
   * The Multiline project's documentation indicates that the package should be pulled from the [JCenter repository](http://jcenter.bintray.com).  See the [Multiline project's documentation for Maven.](https://github.com/benelog/multiline/wiki/Maven-project-with-Eclipse#step-2--add-the-dependency-in-maven).
   
   * We already have JCenter configured as a repository for the project.  We should be able to pull the dependency from there directly.
   
   * I simply removed the inaccessible repository and everything builds as you would expect.  The `multiline-string` dependency is pulled from JCenter as you would expect.
   
   ## Testing
   
   1. Clear your Maven cache at `~/.m2/repository/`.
   
   1. Attempt to build Metron.
   
   1. If you are able to build Metron, this PR has worked.
   
   ## Pull Request Checklist
   
   - [ ] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
   - [ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
   - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
   - [ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
   - [ ] Have you included steps or a guide to how the change may be verified and tested manually?
   - [ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
   - [ ] Have you written or updated unit tests and or integration tests to verify your changes?
   - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services