On Fri, May 18, 2012 at 5:20 AM, David Nalley <da...@gnsa.us> wrote:
> On Thu, May 17, 2012 at 11:58 PM, Kevin Kluge <kevin.kl...@citrix.com> wrote:
>> David, I had assumed that we could just get this library released under AL2 
>> and bundle the jar with CloudStack.   It'd be great if distros picked it up 
>> but that seems more difficult and longer term than a re-license, given our 
>> ability to influence the license of this particular piece of software.  (My 
>> understanding is that Citrix wrote all that code, and it could be released 
>> under multiple licenses if needed, which would presumably not upset the 
>> Xen/XenServer community.)
>>
>> -kevin
>
> Ahh - I was unaware that this was a solely Citrix-written piece of
> software, unlike the rest of Xen* - If we can get it relicensed,
> that's better, perhaps we can get our changes upstreamed at the same
> time.

Hi all,

I just checked the XenServer API bindings for Java, and it seems that
we've dual-licensed them under the LGPLv2 and Apache v2.0 licenses.
Are there different XenServer API bindings for Java that are licensed
differently, that I'm not aware of?

These bindings are autogenerated, which is why there is no source
repository for them. The license on the API bindings generation code
is GPLv2, so I don't see any reason why we couldn't publish the source
repo for these bindings.

David, if you have API bindings changes you need made, I can put you
in contact with the team that owns the bindings generation code, and
we can try to get those changes upstreamed there. Also, I would be
interested in publishing the various language bindings as packages for
deb and rpm based distros. We've already pushed the xenapi-python
bindings to Debian and Ubuntu, so it would make sense to add the Java
and C bindings.

Mike

Reply via email to