Can't build on ubuntu 16.04, on master

[magatz]

After cloning the repo, and installed java:

java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)

then installed maven:
Apache Maven 3.3.9

I've got the following error running:
./jitsi-hammer.sh -BOSHuri https://www.exmple.com/http-bind/ -users 10

tee: /home/andrea/git/jitsi-hammer/.jitsi-hammer/log/output.log: No such file or directory
[INFO] Scanning for projects...
Downloading: https://repo.maven.apache.org/maven2/org/codehaus/mojo/exec-maven-plugin/1.4.0/exec-maven-plugin-1.4.0.pom
[WARNING] Failed to retrieve plugin descriptor for org.codehaus.mojo:exec-maven-plugin:1.4.0: Plugin org.codehaus.mojo:exec-maven-plugin:1.4.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:exec-maven-plugin:jar:1.4.0
Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/2.4/maven-jar-plugin-2.4.pom
[WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-jar-plugin:2.4: Plugin org.apache.maven.plugins:maven-jar-plugin:2.4 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-jar-plugin:jar:2.4
Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.18.1/maven-surefire-plugin-2.18.1.pom
[WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-surefire-plugin:2.18.1: Plugin org.apache.maven.plugins:maven-surefire-plugin:2.18.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-surefire-plugin:jar:2.18.1

resulting in:

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.867 s
[INFO] Finished at: 2016-08-18T13:39:07+00:00
[INFO] Final Memory: 11M/171M
[INFO] ------------------------------------------------------------------------
[ERROR] No plugin found for prefix 'exec' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/root/.m2/repository), central (https://repo.maven.apache.org/maven2)] -> [Help 1]

Had to rollback to pre-maven commit to build the project (commit: 98300d9)

[gurvinderdadyala]

@magatz I am facing the same issue, Did you find any solution.

[magatz]

Not yet, and i'm quite disappointed ...

On Tue, Sep 27, 2016 at 2:26 PM, Gurvinder Dadyala <[email protected]

wrote:

@magatz https://github.com/magatz I am facing the same issue, Did you
find any solution.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#17 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAs2KWIwtUE-PfsMEDEE9npsJzNvCOm5ks5quQt1gaJpZM4JoMMo
.

[image: Andrea Magatti on about.me]

Andrea Magatti
about.me/amagatti
http://about.me/amagatti

[gurvinderdadyala]

@magatz Thank you for the confirmation.

[danielg4]

This fixes the immediate problems but doesn't seem to make it work:
issue17.patch.txt
Connection parameters to meet.jit.si are invalid.

[lhammond]

I'm having the same issue

[gpolitis]

The hammer is a testing tool and as such sometimes it's used to test environments that have invalid certificates. So the jitsi-hammer.sh script modifies the cert keystore so that BOSH connections against the server under test don't fail. As you all have observed, this has the negative side effect of breaking maven dependencies fetching. You may want to try to change the goal from java to exec here https://github.com/jitsi/jitsi-hammer/blob/master/jitsi-hammer.sh#L52. This will make sure that maven is running with an unmodified keystore while the hammer runs with the modified one.

[msheiny]

Looks like if you just run mvn exec:java once without arguments it will pull in the necessary dependencies before the certificate keystore is mangled. Then you can continue to run the script without mvn errors (at least I was).

[gpolitis]

You can try this PR #24