JSR 337 expert group has ratified Oracle chief architect Mark Reinhold's proposal to defer Project Jigsaw to Java 9. Were the stated reasons sufficient motivation for this deferment?
Java developers across the ecosystem have been swift to react to Mark Reinhold's announcement last week that project Jigsaw, Oracle's planned modularity framework for Java, will now be delayed until Java 9.
The Eclipse Foundation has announced the winners of the annual Eclipse Community Awards on the opening day EclipseCon 2012. The awards recognize the top individuals, projects and technologies in the Eclipse ecosystem.
The OSGi Alliance has made available the Early Draft specifications for the next release of the OSGi platform. As a draft specification, specific features may differ and some may be missing or replaced. Read on for what's new.
At the OSGi Community Event, Dr Graham Charters introduced the Modularity Maturity Model, a way of scoring where projects or organisations against how their modular developments score.
Yesterday, Mark Reinhold posted the first public draft of the future of modularity in Java. As it is a draft, there are a handful of issues that still need to be agreed on - but it represents the consensus of what modularity in Java should look like. And with IBM being involved, there's more emphasis on interoperability with OSGi than there has been in the past.
The first significant release of Hudson since the Hudson/Jenkins fork has been released, with a new versioning scheme following OSGi/Semantic Versioning going forward. This includes a new JSR330 dependency injection model to make it easier to run in an OSGi runtime as well as decoupling from specific Hudson annotations.
A new project on Google Code, the Pojo Service Registry, aims to provide an OSGi-lite mechanism for Java applications, but outside of a OSGi runtime. Instead of requiring all JARs to be bundles, it scans the startup classpath and emulates a bundle layer, whilst providing the service hookups that would be wired together in a full OSGi container.
Manning have today published OSGi in Action, by Richard S Hall, Karl Pauls, Stuart McCulloch and David Savage. Written by long-term OSGi users and committers on the Apache Felix runtime, the depth of knowledge in the book comes across with subtleties and specific gotchas documented.
At EclipseCon 2011, the OSGi 4.3 specifications were announced and are available as a public final draft, to be released in the near future. Changes include adding generics to the core API, as well as a general purpose capability model to declare non-coding requirements between bundles. Read on for more information about what to expect.
Many consider the cost of migration onto OSGi expensive, but frequently this is conflated with the cost of modularity itself. Modularising a large, complex and heavily intertwined library is an expense that has no immediate benefits to the maintainers. However, if left to rot, the system will become more complex, intertwined and larger over time and the maintenance cost will increase.
Ross Mason, founder of MuleSource expressed his frustration with OSGi: "OSGi is a great specification for middleware vendors, but a terrible specification for the end user." He argues that OSGi just isn’t ready for the developer yet as it is too difficult to completely make it invisible to a developer.
Last week saw London's OSGi Community Event, in conjunction with JAX London. The conference presentations covered a wide range of environments, from Java EE migrations and cloud computing, down to embedded devices and Android.
It's been a long time since the last Bundle.update was posted, and there have been a lot of OSGi-centric updates since then. OSGi 4.2 has been released, with Equinox 3.6, Felix 3.0 and Knopflerfish 3.0 all providing support for the new platform. Recently, there have been some glimpses of the next version of OSGi, as well as increased enterprise support. Read on to find out what's been happening.