|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MVERSIONS-201) Usage of parent pr... Stefan Negrea (JIRA)
- [mojo-dev] [jira] (MVERSIONS-201) Usage of pare... Daniel Hopper (JIRA)
- [mojo-dev] [jira] (MVERSIONS-201) Usage of pare... Daniel Hopper (JIRA)
- [mojo-dev] [jira] (MVERSIONS-201) Usage of pare... remi gerard (JIRA)
- [mojo-dev] [jira] (MVERSIONS-201) Usage of pare... remi gerard (JIRA)
- [mojo-dev] [jira] (MVERSIONS-201) Usage of pare... Andy Gumbrecht (JIRA)
- [mojo-dev] [jira] (MVERSIONS-201) Usage of pare... Andy Gumbrecht (JIRA)

We get similar issue.
Just to indicate some more specific case we have that throw exactly same stack trace:
_ if the failing dependency is in a non-activated profile.
_ if it is in a dependency of a plugin.
fixing versions-maven-plugin version back to 1.3.1 resolve the issue, until patch of 2.X is deployed.