cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hugo Trippaers <>
Subject Re: VmWare SDK to vijava
Date Tue, 21 Jan 2014 22:43:55 GMT
Let's not repeat the previous discussion. We allready agreed that the wsdl is the way forward.
However we can't get any legal entity to say that it is ok to do so.

Hence my proposal to at least move forward even if it means to temporarily use vijava. 

I really don't care what we do, as long as we have VMware in the regular build before the
4.4 feature freeze.

If anyone of you is willing to chase VMware legal on this, please have a go at it.


Sent from my iPhone

> On 21 jan. 2014, at 19:32, Chiradeep Vittal <> wrote:
> Suboptimal for?
> Wouldn't the ACS user want the best / supported client libraries?
> Alternatively, can't we just compile the WSDL and check in the generated
> sources? Not check-in the WSDL, but the client sources.
>> On 1/21/14 7:18 AM, "David Nalley" <> wrote:
>> On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers <>
>> wrote:
>>> I bet we never got an answer. Frankly, I'd like to see us use
>>> something where the licensing is clear.  That, or we don't include the
>>> WSDL in our repo / distro.
>> Additionally, we are an open source project that is in the business of
>> producing open source software. Depending on non-free and
>> non-opensource libraries is suboptimal, but its worse when there is a
>> open source alternative.
>> --David

View raw message