hi,
ive deleted everything under ".vagrant.d" and rerun the "../kapua-develop/dev-tools/src/main/bin/start-demo.sh" script once again :
FO] kapua-security-authentication-api .................. SUCCESS [ 0.898 s]
[INFO] kapua-commons ...................................... FAILURE [ 5.565 s]
[INFO] kapua-locator ...................................... SKIPPED
[INFO] kapua-guice ........................................ SKIPPED
[INFO] kapua-user ......................................... SKIPPED
[INFO] kapua-user-api ..................................... SKIPPED
[INFO] kapua-account ...................................... SKIPPED
[INFO] kapua-account-api .................................. SKIPPED
[INFO] kapua-test ......................................... SKIPPED
[INFO] kapua-security-shiro ............................... SKIPPED
[INFO] kapua-message ...................................... SKIPPED
[INFO] kapua-message-api .................................. SKIPPED
[INFO] kapua-datastore .................................... SKIPPED
[INFO] kapua-datastore-api ................................ SKIPPED
[INFO] kapua-message-internal ............................. SKIPPED
[INFO] kapua-datastore-internal ........................... SKIPPED
[INFO] kapua-device ....................................... SKIPPED
[INFO] kapua-device-api ................................... SKIPPED
[INFO] kapua-device-registry .............................. SKIPPED
[INFO] kapua-device-registry-api .......................... SKIPPED
[INFO] kapua-transport .................................... SKIPPED
[INFO] kapua-transport-api ................................ SKIPPED
[INFO] kapua-device-call .................................. SKIPPED
[INFO] kapua-device-call-api .............................. SKIPPED
[INFO] kapua-translator ................................... SKIPPED
[INFO] kapua-translator-api ............................... SKIPPED
[INFO] kapua-device-call-kura ............................. SKIPPED
[INFO] kapua-device-commons ............................... SKIPPED
[INFO] kapua-transport-mqtt ............................... SKIPPED
[INFO] kapua-translator-kura .............................. SKIPPED
[INFO] kapua-translator-kura-mqtt ......................... SKIPPED
[INFO] kapua-device-call-test ............................. SKIPPED
[INFO] kapua-device-configuration ......................... SKIPPED
[INFO] kapua-device-configuration-api ..................... SKIPPED
[INFO] kapua-device-configuration-internal ................ SKIPPED
[INFO] kapua-device-packages .............................. SKIPPED
[INFO] kapua-device-packages-api .......................... SKIPPED
[INFO] kapua-device-packages-internal ..................... SKIPPED
[INFO] kapua-user-internal ................................ SKIPPED
[INFO] kapua-device-registry-internal ..................... SKIPPED
[INFO] kapua-device-bundle ................................ SKIPPED
[INFO] kapua-device-bundle-api ............................ SKIPPED
[INFO] kapua-device-bundle-internal ....................... SKIPPED
[INFO] kapua-device-command ............................... SKIPPED
[INFO] kapua-device-command-api ........................... SKIPPED
[INFO] kapua-device-command-internal ...................... SKIPPED
[INFO] kapua-account-internal ............................. SKIPPED
[INFO] kapua-device-command-test .......................... SKIPPED
[INFO] kapua-transport-jms ................................ SKIPPED
[INFO] kapua-transport-test ............................... SKIPPED
[INFO] kapua-translator-kapua ............................. SKIPPED
[INFO] kapua-translator-kapua-kura ........................ SKIPPED
[INFO] kapua-translator-kura-jms .......................... SKIPPED
[INFO] kapua-broker-core .................................. SKIPPED
[INFO] kapua-console ...................................... SKIPPED
[INFO] kapua-rest-api ..................................... SKIPPED
[INFO] kapua-assembly ..................................... SKIPPED
[INFO] kapua-dev-tools .................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18.994 s
[INFO] Finished at: 2016-12-29T14:39:15+02:00
[INFO] Final Memory: 43M/577M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:sql-maven-plugin:1.5:execute (create-schema) on project kapua-commons: Connection is broken: "java.net.SocketTimeoutException: connect timed out: 192.168.33.10:3306" [90067-192] -> [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/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :kapua-commons
VM must be running to open SSH connection. Run `vagrant up`
to start the virtual machine.
[*** IVE TYPED vagrant up ***]
yuval@zmaor-kubuntu:~/Development/Wireless/IoT/Eclipse/Clouds/framework/kapua-develop/dev-tools/src/main/bin$ vagrant up
A Vagrant environment or target machine is required to run this
command. Run `vagrant init` to create a new Vagrant environment. Or,
get an ID of a target machine from `vagrant global-status` to run
this command on. A final option is to change to a directory with a
Vagrantfile and to try again.
[*** IVE TYPED vagrant init ***]
yuval@zmaor-kubuntu:~/Development/Wireless/IoT/Eclipse/Clouds/framework/kapua-develop/dev-tools/src/main/bin$ vagrant init
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
it says : "To see the full stack trace of the errors, re-run Maven with the -e switch.Re-run Maven using the -X switch to enable full debug logging."
i'm not a maven expert, what should i type in order to see the full trace ?
"mvn -e" ?
"mvn -Xe" ?
thanks