Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins

2013-08-16 Thread Hugo Trippaers
with permissions disabled? DL -Original Message- From: SuichII, Christopher [mailto:chris.su...@netapp.com] Sent: 15 August 2013 20:13 To: dev@cloudstack.apache.org Cc: Donal Lafferty; Alex Huang Subject: Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot

Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins

2013-08-16 Thread SuichII, Christopher
: Donal Lafferty; Alex Huang Subject: Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins As I look in to this, it looks like the problem definitely comes from switching Jetty from using the target/...4.3.0/ to target/generated-webapp/ The maven-war-plugin creates

RE: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins

2013-08-16 Thread Donal Lafferty
: SuichII, Christopher [mailto:chris.su...@netapp.com] Sent: 16 August 2013 13:00 To: Donal Lafferty Cc: dev@cloudstack.apache.org; Alex Huang Subject: Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins That's interesting, Donal. I see that the scripts

RE: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins

2013-08-16 Thread Donal Lafferty
; Alex Huang Subject: Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins Heya, An easier solution could be to explicitly start the scripts with /bin/sh. No need to set executable bits anymore, this makes a lot of stuff easier when handling scripts

Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins

2013-08-15 Thread Chiradeep Vittal
Seems related to https://issues.apache.org/jira/browse/CLOUDSTACK-3650 Not sure about why the mvn repo is used. Have you tried clean install? On 8/15/13 11:05 AM, SuichII, Christopher chris.su...@netapp.com wrote: Some of you may remember a previous thread where I talked a bit about this, so

Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins

2013-08-15 Thread SuichII, Christopher
As I look in to this, it looks like the problem definitely comes from switching Jetty from using the target/...4.3.0/ to target/generated-webapp/ The maven-war-plugin creates all the war files in target/cloud-client-ui-4.3.0-SNAPSHOT/ then copies *some* of it to target/generated-webapp/ from

RE: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins

2013-08-15 Thread Donal Lafferty
-Original Message- From: SuichII, Christopher [mailto:chris.su...@netapp.com] Sent: 15 August 2013 20:13 To: dev@cloudstack.apache.org Cc: Donal Lafferty; Alex Huang Subject: Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins As I look