Hi, Do vmware libraries really need to be removed and re-added manually? Could ASF not acquire permission from Vmware to redistribute their freely available sdk for this project? This 4.0 would be the first big ASF release and you want to cripple vmware support?
+1 to keep vmware support for 4.0 as it is Regards Tamas Monos DDI +44(0)2034687012 Chief Technical Office +44(0)2034687000 Veber: The Hosting Specialists Fax +44(0)871 522 7057 http://www.veber.co.uk Follow us on Twitter: www.twitter.com/veberhost Follow us on Facebook: www.facebook.com/veberhost -----Original Message----- From: David Nalley [mailto:da...@gnsa.us] Sent: 09 August 2012 17:58 To: cloudstack-dev@incubator.apache.org Subject: Re: [DISCUSS] VMware support was: Re: vijava - some additional thoughts On Thu, Aug 9, 2012 at 12:44 PM, Will Chan <will.c...@citrix.com> wrote: > I prefer the same option "remove VMware SDK from the build" idea as well. I > wouldn't even go as far as adding in other libraries. If people want to use > VMWare, I am hoping we can just give them additional instructions on how to > do that. I am not opposed to dropping VMware support from the default build for 4.0, but continuing forward with after that when there are (at least potentially) two alternatives that would permit us to provide VMware support in the default build and convenience binaries strikes me as a disservice to our users. --David
