[jira] Updated: (MNG-2861) NullPointerException in DefaultArtifactCollector for relocated resolvedArtifacts with different version ranges and available versions.

[ http://jira.codehaus.org/browse/MNG-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-2861: --- Fix Version/s: (was: 2.0.x) 2.0.9 putting this to 2.0.9 so I remember to look again.

[jira] Updated: (MNG-2861) NullPointerException in DefaultArtifactCollector for relocated resolvedArtifacts with different version ranges and available versions.

[ http://jira.codehaus.org/browse/MNG-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-2861: -- Assignee: (was: Brett Porter) Fix Version/s: (was: Reviewed Pending Version Assignment)

[jira] Updated: (MNG-2861) NullPointerException in DefaultArtifactCollector for relocated resolvedArtifacts with different version ranges and available versions.

[ http://jira.codehaus.org/browse/MNG-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Micah Whitacre updated MNG-2861: Attachment: MNG-2861_broken.zip Your testcase worked for me as well. I found that there was a difference

[jira] Updated: (MNG-2861) NullPointerException in DefaultArtifactCollector for relocated resolvedArtifacts with different version ranges and available versions.

[ http://jira.codehaus.org/browse/MNG-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Beermann updated MNG-2861: -- Attachment: MNG-2861-maven-project.patch I think that the relocations are simply exposing a latent