Failure when running "mvn clean verify"
Closed this issue · 7 comments
Hi all,
I´m trying to follow the first steps in the book, but when running mvn clean verify, I get the following output: https://pastebin.com/dVNua0sP
This happens on Windows 10 and also Ubuntu 18.10 LTS.
Many thanks for any hints!
Best,
Christian
Could you try with the latest version on Github?
I think I used the latest version from there, got it via git clone https://github.com/serenity-bdd/serenity-junit-starter.git
Give it another go.
Ok, did a git pull (pom.xml got an update), now I get this:
[WARNING] The POM for net.serenity-bdd.maven.plugins:serenity-maven-plugin:jar:2.0.39 is missing, no dependency information available
Downloading from central: http://jcenter.bintray.com/net/serenity-bdd/maven/plugins/serenity-maven-plugin/2.0.39/serenity-maven-plugin-2.0.39.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.029 s
[INFO] Finished at: 2019-02-06T09:40:39-05:00
[INFO] Final Memory: 10M/121M
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin net.serenity-bdd.maven.plugins:serenity-maven-plugin:2.0.39 or one of its dependencies could not be resolved: Could not find artifact net.serenity-bdd.maven.plugins:serenity-maven-plugin:jar:2.0.39 in central (http://jcenter.bintray.com) -> [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/PluginResolutionException
It looks like the jcenter url is not seeing any of the 2.0.x dependencies, so I'm not sure what is going on there (Serenity deploys automatically to JCenter). Could you try now?
It´s now working, many thanks John! :-)
Thanks for the update!