Oracle Granted More Time in Google Patent Wars

San Francisco U.S. district court judge William Alsup, has
agreed to wait until the last pre-trial
conference to hear Oracle’s plan for a case that it could
present to a jury over the course of a three week trial. The Judge
originally claimed that Oracle’s 132 claims from seven patents were
too complicated for a jury to understand. The Judge subsequently
proposed narrowing Oracle’s claims and Google’s defences through a
three-step process to ensure “only a triable number of these items”
would be presented to the jury in October, with Oracle ultimately
selecting three claims to assert, and Google citing eight prior art
references. This effectively meant Oracle would have to drop 129
claims of patent infringement against Google.

Google’s King & Spalding lawyers responded that “Google
agrees with the court’s three-step process in its entirety,” but
Oracle’s lawyers objected. Now, Alsup has rethought this
“three-step process” proposal – although he has said that if Oracle
doesn’t streamline its claims, he will consider delaying the
litigation until the U.S Patent and Trademark Office has completely
re-examined Oracle’s patents.

Module System in Java SE 8 – Compatible with
OSGi?

David Bosschaert has posted his thoughts on the requirements for the
Module System in Java SE 8. He is optimistic about what they mean
for the future of OSGi, naming systems not being created in a
modular way to begin with, as one of the big problems when it comes
to migrating an existing system to OSGi. “Once modularization is
part of Java SE 8, moving to OSGi will be easier than it is today,”
he predicts. He also sees the new requirements as being compatible
with OSGi, as the Module System in Java SE 8 contains a specific requirement about OSGi interacting with
Java SE modules:

“It must be demonstrated by prototype to be feasible to modify
an OSGi micro-kernel such that OSGi bundles running in that kernel
can depend upon Java modules. The kernel must be able to load Java
modules directly and resolve them using its own resolver, except
for core system modules. Core system modules can only be loaded
using the module system’s reification API.”

IcedTea7 version 1.14 has been announced. This
release moves the NetX and the plugin to the IcedTea-Web project,
and features out-of-the-box JamVM support. JamVM builds can
bootstrap and are self-hosting. The next release of IcedTea7 will
be based on OpenJDK7.

TeamCity 6.5 Removes Professional Edition
Restrictions

TeamCity 6.5 has been released with a new build
trigger that watches for commits into Git and Mercurial branches.
Parameter references can now be used in all text fields of a VCS
root settings (expect password fields) and tests can now be grouped
by package on the build results page, My Changes, and Current
Problems pages. “Agent Push” has also been added, a new
experimental way to automatically install build agents, either on
the machines in your network or in the cloud. In addition, TeamCity
have removed all of the restrictions on the TeamCity Professional
Edition, save for the maximum number of build configurations. This
means TeamCity Professional Edition users now get an unlimited
number of users, the ability to use any authentication scheme, and
adjustable per-project permissions.