In an effort to get information out to the Kenai community quickly, while trying to manage the integration of our two companies, I think we did a poor job at communicating our plans for Kenai.com to you. I would like to remedy that now. Our strategy is simple. We don't believe it makes sense to continue investing in multiple hosted development sites that are basically doing the same thing. Our plan is to shut down kenai.com and focus our efforts on java.net as the hosted development community. We are in the process of migrating java.net to the kenai technology. This means that any project currently hosted on kenai.com will be able to continue as you are on java.net. We are still working out the technical details, but the goal is to make this migration as seamless as possible for the current kenai.com projects. So in the meantime I suggest that you stay put on kenai.com and let us work through the details and get back to you later this month.
Thanks for your feedback and patience.
Before this announcement, developers were prompted to remove their projects by April 2nd. Project Kenai, which is still in beta, was launched in September 2008 for hosting Java, JRuby, and Rails applications. It also provides a collaborative infrastructure for managing netbeans.org. This decision by Oracle is a victory for NetBeans since a lot of work has gone into integrating the Project Kenai infrastructure with Sun's flagship IDE and platform. The consolidation approach to Sun projects makes sense in this case, according to Oracle, and the company may also consider this approach for other Sun projects as it continues the merger.
However, Oracle is having bigger problems than miscommunication right now. Recently they rushed to release an unscheduled security patch for their WebLogic server in order to close a vulnerability in which a remote attacker could execute OS commands without any authentication. The flaw effects WebLogic version 7 and higher. Oracle has not yet developed a patch for another vulnerability in Oracle 11gR2 that allows users to escalate their privileges to the point of gaining complete control over the database. David Litchfield, the British security expert who discovered the vulnerability, says he informed Oracle of the problem back in November.