Hi all. 
 
 
I recently solved a couple of issues (#95, #116) that affected the setup of the demo environment.  
Hope these fixes could help. 
 
 
Cheers, 
Stefano  
 
From: Morson, Stefano 
Sent: Friday, November 18, 2016 5:13 PM 
To: kapua developer discussions 
Subject: Re: [kapua-dev] Errors building Kapua
  
 
Hi all, 
 
 
Thanks @Alon reporting the issue and @Uros for the support.  
 
 
It seems there is something wrong in the getting started procedure not in the Kapua sources. Maybe the last issue you found (kapua-commons
 ...................................... FAILURE) is due to the tentative to build for the demo without having
 the runtime env properly configured. 
 
 
 
I'll look into the code trying to reproduce the original issue, I'll give some feedback as
 soon as I have some findings. 
 
 
Stefano 
  
 
 
 
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Uroš Mesarič Kunst <Uros.Mesaric-Kunst@xxxxxxxxxxxx> 
Sent: Friday, November 18, 2016 3:57:29 PM 
To: kapua developer discussions 
Subject: Re: [kapua-dev] Errors building Kapua
  
 
I prefer setting up machine with following instructions: 
  
https://github.com/eclipse/kapua/blob/develop/dev-tools/src/main/vagrant/README.MD 
  
  
From: kapua-dev-bounces@xxxxxxxxxxx [mailto:kapua-dev-bounces@xxxxxxxxxxx]
On Behalf Of Alon Harel 
Sent: Friday, November 18, 2016 1:18 PM 
To: kapua developer discussions <kapua-dev@xxxxxxxxxxx> 
Subject: Re: [kapua-dev] Errors building Kapua 
  
Hi all, 
Running the start-demo.sh does not work for me nor for my colleagues. 
 
The script output before aborting is attached below. 
 
Is it possible that this version is broken? 
 
Alon 
[INFO] --- sql-maven-plugin:1.5:execute (create-schema) @ kapua-commons --- 
 
[INFO] ------------------------------------------------------------------------ 
 
[INFO] kapua .............................................. SUCCESS [  1.228 s] 
 
[INFO] kapua-service ...................................... SUCCESS [  0.034 s] 
 
[INFO] kapua-service-api .................................. SUCCESS [  6.928 s] 
 
[INFO] kapua-idgenerator .................................. SUCCESS [  0.012 s] 
 
[INFO] kapua-idgenerator-api .............................. SUCCESS [  0.069 s] 
 
[INFO] kapua-security ..................................... SUCCESS [  0.009 s] 
 
[INFO] kapua-security-authorization ....................... SUCCESS [  0.007 s] 
 
[INFO] kapua-security-authorization-api ................... SUCCESS [  0.228 s] 
 
[INFO] kapua-security-authentication ...................... SUCCESS [  0.009 s] 
 
[INFO] kapua-security-authentication-api .................. SUCCESS [  0.142 s] 
 
[INFO] kapua-commons ...................................... FAILURE [  4.872 s] 
 
[INFO] kapua-locator ...................................... SKIPPED 
 
[INFO] kapua-guice ........................................ SKIPPED 
 
[INFO] kapua-idgenerator-sequence ......................... SKIPPED 
 
 
 
  
On Thu, Nov 17, 2016 at 5:40 PM, Alon Harel <alonhrl.us@xxxxxxxxx> wrote: 
Hi, 
I have managed to overcome the Vagrant issue by running 'rm /opt/vagrant/embedded/bin/curl' prior running 'start-demo.sh'. 
 
However, now I get the following error: 
 
[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.ConnectException: Connection refused:
192.168.33.10:3306" [90067-192] -> [Help 1] 
 
I can see that the VM (192.168.33.10) is answering pings though. 
 
 
  
On Thu, Nov 17, 2016 at 3:39 PM, Alon Harel <alonhrl.us@xxxxxxxxx> wrote: 
Hi Kapua community, 
Creating base kapua box named  trusty64/kapua-dev-box-0.1  ... 
 
The box you requested to be removed could not be found. No 
 
boxes named 'trusty64/kapua-dev-box-0.1' could be found. 
 
/Users/alonharel/Documents/Work/kapua/dev-tools/src/main/vagrant/baseBox/kapua-box-tmp 
 
Bringing machine 'default' up with 'virtualbox' provider... 
 
==> default: Box 'ubuntu/trusty64' could not be found. Attempting to find and install... 
 
    default: Box Provider: virtualbox 
 
    default: Box Version: >= 0 
 
The box 'ubuntu/trusty64' could not be found or 
 
could not be accessed in the remote catalog. If this is a private 
 
box on HashiCorp's Atlas, please verify you're logged in via 
 
`vagrant login`. Also, please double-check the name. The expanded 
 
URL and error message are shown below: 
 
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
 
 
 
 
 |