3 ms·
The issue of license violation is that someone had to claim damages. Mojang could have, but didn't - and you could argue in a court benefited greatly from this
by XorNot 12y ago
The issue of license violation is that someone had to claim damages. Mojang could have, but didn't - and you could argue in a court benefited greatly from this state of affairs (selling Minecraft licenses).
The fact that Mojang now wants to distribute GPL code without providing full source would, I suspect, stand badly against that since a claim of license violation has been made now. Generally, you can't ignore copyright by yelling "two wrongs make a right".
- shawn-furyan 12y agoWell, yeah, I agree. I'm not saying that Mojang hasn't likely been willfully ignoring the license violation, just that Bukkit seems to infringe on the letter of the official Minecraft Server license. And yeah, I don't think that that has any bearing on the copyright claim. Incidentally, the link has been changed since I began commenting. I find this assertion from the now-linked post to be odd: "Additionally, we believe that Wesley has no right to prevent the continued use of his contributions to the project – which he gave freely, knowing them to be subject to applicable open source licenses. We believe these licenses continue to bind all those who contributed to the Bukkit Project." This doesn't really address the primary charge from Wolverness, to paraphrase, that essentially the bukkit and related projects are distributing code incompatible with its license and therefore are not permitted to distribute the copyrighted code contained in the bukkit project without express permission. If the license for the code is not adhered to, then you don't have permission to distribute the copyrighted material... So one party is saying that the license was broken, and the other party responds by saying that there was a license. That's kind of a non sequitur.