GitHub user PuspenduBanerjee opened a pull request: https://github.com/apache/nifi/pull/514
fixes NIFI-1989 Fixes : https://issues.sonatype.org/browse/MVNCENTRAL-244 > Taking a look at the POM at http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom, the groupId and artifactId are different from the deploy path and it seems the identical artifacts are available at http://repo1.maven.org/maven2/commons-io/commons-io/1.3.2/ Having the same classes available under two different GAV coordinates may lead to a lot of problems should one decide to update the component to a new version. I see a lot of old builds could break when we delete from the old coordinates, but what about a (correct) relocation POM? Builds would continue to work and the mishap would appear on the screen. You can merge this pull request into a Git repository by running: $ git pull https://github.com/PuspenduBanerjee/nifi NIFI-1989 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/514.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 #514 ---- commit e25bdd7b2b455728fb14ab7d0cd9a2c76c271aad Author: Puspendu Banerjee <puspendu.baner...@gmail.com> Date: 2016-06-09T18:00:57Z fixes NIFI-1989 ---- --- 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. ---