Remove the version specifier for build-helper-maven-plugin, this will pick up the version from the parent POM, which I locally updated from 34 to 42. Then you'll run into some other error due to how this old build wants to name jars.
Gary On Sat, Oct 21, 2017 at 2:30 AM, Benedikt Ritter <brit...@apache.org> wrote: > Hi, > > when I update commons-logging to use Commons parent 42, I get build > failures: > > ~/w/a/c/commons-logging > mvn clean verify > [INFO] Scanning for projects... > [INFO] > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Building Apache Commons Logging 1.2.1-SNAPSHOT > [INFO] ------------------------------------------------------------ > ------------ > [INFO] ------------------------------------------------------------ > ------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Total time: 0.744 s > [INFO] Finished at: 2017-10-21T10:30:12+02:00 > [INFO] Final Memory: 12M/245M > [INFO] ------------------------------------------------------------ > ------------ > [ERROR] Could not find goal 'parse-version' in plugin > org.codehaus.mojo:build-helper-maven-plugin:1.0 among available goals > add-source, add-test-source, attach-artifact -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ > MojoNotFoundException > > Any idea how to fix this? > > Regards, > Benedikt > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
