I think the point here is that we do not redistribute Oracle Java JDK. We use the Java programming language to write a program (the Apache CloudStack). When we distribute the ACS' binaries, e.g. a closed version, we are also not redistributing the Java, what we do is distributing a binary that is compiled with a Java JDK.
Of course, we cannot forget the licenses for library binaries that we are redistributing with ACS' versions; but, this is not the same as redistributing Oracle Java JRE/JDK. And as far as I know we manage this properly. On Sun, Dec 25, 2016 at 11:13 PM, Tim Mackey <[email protected]> wrote: > Would be good to have a reference too. The only thing I'm aware of which > might impact us relates to any redistributed elements[1]. It would be a > question for the dev list to know if this does indeed impact the project. > > -tim > > [1] http://blog.takipi.com/running-java-on-docker-youre-breaking-the-law/ > > > On Sun, Dec 25, 2016 at 8:01 PM, Rafael Weingärtner < > [email protected]> wrote: > > > Could you share with us the reference? So we can have a bit more > > information to discuss it. > > > > I believe what they charge is for consulting, and not for the use of Java > > language per se. > > > > > > On Sun, Dec 25, 2016 at 10:57 PM, Felipe Arturo Polanco < > > [email protected]> wrote: > > > > > Hello, > > > > > > I read in the news Oracle is collecting from companies using Java > > libraries > > > in commercial uses, since Cloudstack uses Java for its operations, > should > > > we worry about it? > > > > > > > > > > > -- > > Rafael Weingärtner > > > -- Rafael Weingärtner
