I automatically assumed it's an optional component, but I don't think we actually discussed this. It's also optional in the maven compile/build I've noticed. I'm certainly not against it being part of the "main" management server, but the dependencies are not really aligned yet. So it's going to be a huge rpm if we make a single package out of it.
We should make a point of redoing the axis stuff to generate new classes and try to get the dependencies in line with the management server. But that's something for later. We could technically use the maven axis task to generate that part of the code automagically. Cheers, Hugo > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Wednesday, March 06, 2013 4:22 PM > To: cloudstack-dev@incubator.apache.org; Prasanna Santhanam > Cc: Wido den Hollander; Noa Resare; Hugo Trippaers; Pradeep Soundararajan > Subject: Re: Review Request: Adding awsapi in the require section of > cloud.spec as it resolves issue with EC2 QUERY API Feature. > > On Wed, Mar 06, 2013 at 12:23:09PM +0000, Prasanna Santhanam wrote: > > > > ----------------------------------------------------------- > > This is an automatically generated e-mail. To reply, visit: > > https://reviews.apache.org/r/9776/#review17472 > > ----------------------------------------------------------- > > > > > > But awsapi should be an optional component to install, right? > > Why? Isn't it part of the core product now, with only a global setting as > it's > flag to enable / disable the feature? > > IMO, it should be part of the default installation.
