Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CF3F410301 for ; Fri, 16 Aug 2013 09:47:21 +0000 (UTC) Received: (qmail 69316 invoked by uid 500); 16 Aug 2013 09:47:15 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 69255 invoked by uid 500); 16 Aug 2013 09:47:14 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 69223 invoked by uid 99); 16 Aug 2013 09:47:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Aug 2013 09:47:03 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of trippie@gmail.com designates 74.125.83.42 as permitted sender) Received: from [74.125.83.42] (HELO mail-ee0-f42.google.com) (74.125.83.42) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Aug 2013 09:46:57 +0000 Received: by mail-ee0-f42.google.com with SMTP id b45so860902eek.1 for ; Fri, 16 Aug 2013 02:46:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=NU5HZDc0EVguTp+Ebpv2HjsJsIAzJNaROsSJnpfXNJU=; b=S7qWsnwk4pTxt/FO1dMct4nk3LSMQ3dn3NIANwBBT04ErTn4LKo+sWUxyNqOqHS2HF sxEzW941hcb3qRNM7knZcOIKHlZ6Ij+3koKqxDMs/+n0OEvQiLGUZkBqVN/4ZtvGPW6/ aMzdfFR2fZzNYDJ773DGN5WcSnN3ZMOj0ViC9UmLHRb0OhRKdwtfvLURoyrgi0YPoDxW F/ysJEsoQCbHfO+U1rF2LjfF1Bs+ekQ3v2Q+meduoyr9jiCr4LWsA3kLwZOLg589JltL 12LN11Sj4HCg7YJEGJciYRP/5XCSJcwKTwSntoL+gi/KxuRPVTmDZCURxmGJPP67q/id +CdA== X-Received: by 10.14.176.8 with SMTP id a8mr1124040eem.12.1376646397086; Fri, 16 Aug 2013 02:46:37 -0700 (PDT) Received: from [100.93.198.121] ([188.207.113.211]) by mx.google.com with ESMTPSA id r48sm1363005eev.14.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 16 Aug 2013 02:46:28 -0700 (PDT) References: <7245D3B6-0EC5-4D78-97D9-91C4CD919EFB@netapp.com> <9ADDE3F979256644BED8F0D244BE51F0061419@AMSPEX01CL02.citrite.net> Mime-Version: 1.0 (1.0) In-Reply-To: <9ADDE3F979256644BED8F0D244BE51F0061419@AMSPEX01CL02.citrite.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Cc: "SuichII, Christopher" , "" , Alex Huang X-Mailer: iPhone Mail (10B329) From: Hugo Trippaers Subject: Re: Changes to cloud-client-ui jetty webAppSourceDirectory and hot deploying API Plugins Date: Fri, 16 Aug 2013 11:46:24 +0200 To: "dev@cloudstack.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org 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 h= andling scripts. Cheers, Hugo=20 Sent from my iPhone On 16 aug. 2013, at 01:12, Donal Lafferty wrote:= > Hi Christopher, >=20 > Could you take a quick look at the permissions on scripts in the ./client f= older? >=20 > I raised https://issues.apache.org/jira/browse/CLOUDSTACK-3650, because th= e Maven project that launched Jetty does not set execution permissions for s= cripts in ${project.build.directory}/${project.build= .finalName} E.g.=20 >=20 > root@mgmtserver:~/github/cshv3/client# ls -al ./target/cloud-client-ui-4.2= .0-SNAPSHOT/WEB-INF/classes/scripts/vm/hypervisor/versions.sh > -rw-r--r-- 1 root root 1636 Aug 14 15:42 ./target/cloud-client-ui-4.2.0-SN= APSHOT/WEB-INF/classes/scripts/vm/hypervisor/versions.sh >=20 > versus >=20 > root@mgmtserver:~/github/cshv3/client# ls -al ./target/generated-webapp/WE= B-INF/classes/scripts/vm/hypervisor/versions.sh > -rwxr-xr-x 1 root 1636 Aug 14 15:42 ./target/generated-webapp/WEB-INF/clas= ses/scripts/vm/hypervisor/versions.sh >=20 >=20 > I'm confused as to how other systems were able to run scripts. I can't ge= t them to run to run on Debian 7. >=20 > root@mgmtserver:~/github/cshv3/client# ./target/cloud-client-ui-4.2.0-SNAP= SHOT/WEB-INF/classes/scripts/vm/hypervisor/versions.sh > -bash: ./target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/= hypervisor/versions.sh: Permission denied >=20 > root@mgmtserver:~/github/cshv3/client# ./target/generated-webapp/WEB-INF/c= lasses/scripts/vm/hypervisor/versions.sh > Host.OS=3DUnknown Linux > Host.OS.Version=3DX.Y > Host.OS.Kernel.Version=3D3.2.0-4-amd64 >=20 >=20 > Are you using an O/S with permissions disabled? >=20 >=20 > DL >=20 >=20 >=20 >> -----Original Message----- >> From: SuichII, Christopher [mailto:Chris.Suich@netapp.com] >> Sent: 15 August 2013 20:13 >> To: >> Cc: Donal Lafferty; Alex Huang >> Subject: Re: Changes to cloud-client-ui jetty webAppSourceDirectory and h= ot >> deploying API Plugins >>=20 >> As I look in to this, it looks like the problem definitely comes from swi= tching >> Jetty from using the target/...4.3.0/ to target/generated-webapp/ >>=20 >> 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 >> client/ and then create the cloud-client-ui-4.3.0-SNAPSHOT.war. >>=20 >> I'm not all that strong with maven, so despite some digging, I can't figu= re out >> why it creates and copies WEB-INF/classes/ from client/ but not WEB-INF/l= ib/ >>=20 >> Still not sure why the mvn repo is used? Maybe it falls back to that to >> populate the classpath? >>=20 >> On Aug 15, 2013, at 2:28 PM, Chiradeep Vittal >> wrote: >>=20 >>> 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? >>>=20 >>> On 8/15/13 11:05 AM, "SuichII, Christopher" >> wrote: >>>=20 >>>> Some of you may remember a previous thread where I talked a bit about >>>> this, so bear with me: >>>>=20 >>>> 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 CloudStack, but luckily it worked with no fancy tricks. This was >>>> because I could drop our jar into >>>> client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/lib and the jar >> would automagically get picked up on the class path. >>>>=20 >>>> This changed a couple days ago. It looks like with commit >>>> 49c9fbfb70413f86642956423c4bbba2e43d8aec this was changed to use the >>>> client/target/generated-webapp/ folder instead. The issue I'm running >>>> in to is that this jetty deployment does not have a WEB-INF/lib >>>> folder - it appears to use the dependencies straight from the local >>>> maven repo instead. >>>>=20 >>>> Can someone briefly explain the reasoning behind this change? I am >>>> now unable to hot deploy our jar to a compiled build without editing >>>> client/pom.xml to add an additional folder to the tag.= >>>>=20 >>>> This raises another question I've been meaning to ask. How is the >>>> jetty folder hierarchy structured when someone downloads a release >>>> build of CloudStack? Is there a lib folder where jars like this could >>>> be dropped, or is everything packaged into a single file? >>>>=20 >>>> Thanks, >>>> Chris >=20