Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of Prachi.Damle@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Prachi Damle <Prachi.Damle@citrix.com>
To: Chip Childers <chip.childers@sungard.com>
CC: Hugo Trippaers <HTrippaers@schubergphilis.com>,
	"cloudstack-dev@incubator.apache.org" <cloudstack-dev@incubator.apache.org>
Date: Wed, 5 Sep 2012 15:33:47 -0700
Subject: RE: RPM build fixed (maven-waf branch)
Thread-Topic: RPM build fixed (maven-waf branch)
Thread-Index: Ac2LsxON9Tsc7kJhR86HvSGsGbon4AAA0w/g
Message-ID: 
 <7A92FF96DF135843B4B608FB576BFC3E012D9EF86309@SJCPMAILBOX01.citrite.net>
References: <6DE00C9FDF08A34683DF71786C70EBF029B51B2A@SBPOMB402.sbp.lan>
 <97F4356AEA71904482CD192135C038F9010D96961164@BANPMAILBOX01.citrite.net>
 <6DE00C9FDF08A34683DF71786C70EBF029B51DA2@SBPOMB402.sbp.lan>
 <CA+96GG4ofEUBo1F5E2mH6eUuGftBJj65rTQ7ihtMZgWA6uQutQ@mail.gmail.com>
 <B0AA34D4-6924-4292-9500-14AC0A5D298E@schubergphilis.com>
 <CA+96GG6Dfi0HSdBVmzqcFGXz7O7BYJYpcvohkrbd9U1xGnQM5Q@mail.gmail.com>
 <7A92FF96DF135843B4B608FB576BFC3E012D9EF86289@SJCPMAILBOX01.citrite.net>
 <B1BEF5B2-3358-4850-9A37-061B611A7518@schubergphilis.com>
 <7A92FF96DF135843B4B608FB576BFC3E012D9EF862CF@SJCPMAILBOX01.citrite.net>
 <-13185240499532514@unknownmsgid>
In-Reply-To: <-13185240499532514@unknownmsgid>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Nope. But the file seems to have been generated using the AWS wsdl... I gue=
ss if we can use the generated code, we could use this as well?

-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]=20
Sent: Wednesday, September 05, 2012 3:09 PM
To: Prachi Damle
Cc: Hugo Trippaers; cloudstack-dev@incubator.apache.org
Subject: Re: RPM build fixed (maven-waf branch)

Prachi,

Do you remember / know specifically where the services file came from?

- chip

Sent from my iPhone.

On Sep 5, 2012, at 5:49 PM, Prachi Damle <Prachi.Damle@citrix.com> wrote:

> Hugo / Chip,
>
> I tested and found that we need to include the services.xml file in aar f=
ile generated by build - without that axis2 cannot deploy the aar files whe=
n you start cloudstack.
> We can remove the AmazonEC2.wsdl file safely.
>
> Are there any issues with having services.xml file in source tree?
>
>   [java] org.apache.axis2.deployment.DeploymentException: The services.xm=
l fie cannot be found for the service: C:\tomcat\apache-tomcat-6.0.29\webap=
ps7080\asapi\WEB-INF\services\cloud-ec2.aar
>    [java]     at org.apache.axis2.deployment.repository.util.ArchiveReade=
r.proessServiceGroup(ArchiveReader.java:150)
>
>
> Hugo, the test procedure I use is:
> - remove files and build
> - deploy CloudStack
> - create user and generate keys
> - enable ec2 in CloudStack
>
> For client:
> - register the user's certificate and set up EC2 tools environment
> - use ec2 tools to test commands against CloudStack ec2 api.
>
> Thanks,
> -Prachi
>
> -----Original Message-----
> From: Hugo Trippaers [mailto:HTrippaers@schubergphilis.com]
> Sent: Wednesday, September 05, 2012 2:08 PM
> To: Prachi Damle
> Cc: Chip Childers; cloudstack-dev@incubator.apache.org
> Subject: Re: RPM build fixed (maven-waf branch)
>
> Prachi,
>
> Would it be possible to describe the test procedure? Maybe we can add it =
to Jenkins as well.
>
> Cheers,
>
> Hugo
>
> Sent from my iPhone
>
> On 5 sep. 2012, at 23:04, "Prachi Damle" <Prachi.Damle@citrix.com> wrote:
>
>> The aar files contain the wsdl file and the services.xml file because th=
e build script includes them specifically while building the aar.
>>
>> I don't know if these are a must have files in aar. I will remove and ch=
eck if things work.
>>
>> -Prachi
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Wednesday, September 05, 2012 1:57 PM
>> To: Hugo Trippaers
>> Cc: cloudstack-dev@incubator.apache.org; Prachi Damle
>> Subject: Re: RPM build fixed (maven-waf branch)
>>
>> On Wed, Sep 5, 2012 at 4:44 PM, Hugo Trippaers <HTrippaers@schubergphili=
s.com> wrote:
>>> Chip,
>>>
>>> That makes more sense and less work :-). I think i have the maven part =
done now. The only thing i'm curious about is the mar and aar files. They s=
eem to contain the wsdl files as well. I now nothing about axis2 so no idea=
 what is needed to get awaapi to work right.
>>
>> Might need some help from the folks that have worked on it in the=20
>> past
>> ;)
>>
>> IIRC, aar files are the result of an axis build.  I don't see any of the=
m in the source tree though...  do you?
>>
>> The only mar files I see are the modules/rahas-1.5.mar and modules/rampa=
rt-1.5.mar, which I think are basically dependency files.
>> I did a quick search on maven central, and I think the ones we need are =
there:
>>
>> http://search.maven.org/#search%7Cga%7C1%7Crahas
>> http://search.maven.org/#search%7Cga%7C1%7Crampart
>>
>> Can we make them pull from the mvn central and get them out of the sourc=
e tree?
>>
>>
>>>
>>> Cheers,
>>>
>>> Hugo
>>>
>>> Sent from my iPhone
>>>
>>> On 5 sep. 2012, at 21:43, "Chip Childers" <chip.childers@sungard.com> w=
rote:
>>>
>>>> On Wed, Sep 5, 2012 at 6:40 AM, Hugo Trippaers=20
>>>> <HTrippaers@schubergphilis.com> wrote:
>>>>> Hey Rajesh,
>>>>>
>>>>> As far as I understand (and please correct me if I'm wrong) awsapi co=
nsists of three parts. The generated code for ec2, the generated code for s=
3 and "our" code. I would like to split this in three subprojects for maven=
. Two using the maven axis2 plugins to generate the classes and a third tha=
t uses the output from the first two (the .mar and .aar files) and makes th=
e webapp by adding "our" code.
>>>>>
>>>>> Does that make sense?
>>>>
>>>> Hugo,
>>>>
>>>> I think we were trying to get the WSDL files out of the source tree.
>>>> Prachi did some work on this initially, but two files still remain.
>>>> I believe that without a clear license for the WSDL files, we might=20
>>>> need to remove them from the tree.  Given that, the generated=20
>>>> classes can stay (and be licensed by ASF).  If that's the case,=20
>>>> then this really only needs to be one maven project.  Does that make s=
ense?
>>>>
>>>> The files in question are:
>>>>
>>>>  incubator-cloudstack/awsapi/resource/AmazonEC2/AmazonEC2.wsdl
>>>>  incubator-cloudstack/awsapi/resource/AmazonEC2/services.xml
>>>>
>>>> Prachi - I'm not sure that you were able to come back around to my=20
>>>> previous questions about this, but do you think we can remove them=20
>>>> as well?
>>>>
>>>> Rajesh, perhaps you know the answer?
>>>>
>>>> -chip
>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Hugo
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Rajesh Battala [mailto:rajesh.battala@citrix.com]
>>>>>> Sent: Wednesday, September 05, 2012 12:32 PM
>>>>>> To: cloudstack-dev@incubator.apache.org
>>>>>> Subject: RE: RPM build fixed (maven-waf branch)
>>>>>>
>>>>>> Hi Hugo,
>>>>>>
>>>>>> Regarding Awsapi how are you planning to go ahead ?
>>>>>>
>>>>>> Thanks
>>>>>> Rajesh Battala
>>>>>> -----Original Message-----
>>>>>> From: Hugo Trippaers [mailto:HTrippaers@schubergphilis.com]
>>>>>> Sent: Wednesday, September 05, 2012 3:43 PM
>>>>>> To: cloudstack-dev@incubator.apache.org
>>>>>> Subject: RPM build fixed (maven-waf branch)
>>>>>>
>>>>>> Heya,
>>>>>>
>>>>>> I've made a new branch 'maven-waf' containing the stuff needed to=20
>>>>>> build RPM's using the maven and waf.  I've fixed the issues that=20
>>>>>> prevented building from a clean tree directly, so it should be=20
>>>>>> complete now. With the exeption of awsapi, see my earlier mail on th=
at one.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Hugo
>>>>>
>>>>>
>>>
>