Oracle persisted with the help of that major contributor - an Oracle employee, BTW - and while Jenkins was being created, they did not want to contribute and instead tried to create a competing effort over at the Eclipse Foundation. All but 1 major contributor (not even the main contributor and definitely not the project architect and lead) disagreed with their decision. Well, you have a keyword in there, "everyone". > I seem to recall trademark troubles with Oracle, which led to everyone forking and starting Jenkins. On a digressive topic - it was fun migrating our legacy application server stack from Oracle Java (old & poorly considered decision) to OpenJDK, thanks to their license. There are other options to run your VM, such as Multipass or VirtualBuddy. We've moved our development to KVM and Virtual Machine Manager on Linux and UTM on Mac.
If an exploit is discovered in your old VirtualBox and they've changed the license, you're out of luck.īe specially careful when installing their extension pack, as it is an evaluation license.
Their VirtualBox license FAQ gives them enough leeway to change future licenses at will. VirtualBox components come under three different licenses - GPLv2, personal use & evaluation license, and an enterprise license. I would be cautious or even distrustful of using anything from Oracle.
0 kommentar(er)
