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
DL
From: 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
0:13
To: mailto: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 in to this, it looks like the problem definitely comes from switching
Jetty from using the target/...4.3.0/ to
ux
> Host.OS.Version=X.Y
> Host.OS.Kernel.Version=3.2.0-4-amd64
>
>
> Are you using an O/S with permissions disabled?
>
>
> DL
>
>
>
>> -Original Message-
>> From: SuichII, Christopher [mailto:chris.su...@netapp.com]
>> Sent: 15 August
e-
> From: SuichII, Christopher [mailto:chris.su...@netapp.com]
> Sent: 15 August 2013 20:13
> To:
> Cc: 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 l
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 cl
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" wrote:
>Some of you may remember a previous thread where I talked a bit about
>this, so bear with me:
>
>We ar
Some of you may remember a previous thread where I talked a bit about this, so
bear with me:
We are working on an API plugin that we would like to be hot deployable (not
committed to source and can be deployed at any time). In a previous discussion,
I was told that this had not been tested with
