Hey Rajesh, As far as I understand (and please correct me if I'm wrong) awsapi consists of three parts. The generated code for ec2, the generated code for s3 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 that uses the output from the first two (the .mar and .aar files) and makes the webapp by adding "our" code.
Does that make sense? Cheers, Hugo > -----Original Message----- > From: Rajesh Battala [mailto:rajesh.batt...@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:htrippa...@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 build > RPM's using the maven and waf. I've fixed the issues that prevented > building from a clean tree directly, so it should be complete now. With the > exeption of awsapi, see my earlier mail on that one. > > Cheers, > > Hugo
