With the recently-released OSGi Release 5 early access documents, one of the most anticipated features of the upcoming specification – that of SNAPSHOT style versions for OSGi – has been dropped from the specification because of concerns with existing tooling. Read on to find out why.
ThoughtWorks recently published the latest update to its Technology Radar; a report produced to help technology decision makers understand emerging trends in software development techniques, tools, languages and platforms. There are some interesting observations of interest to Agile software development teams.
Today, Sonatype released Nexus 2.0, a major step forward in their artifact repository. New in this release is the addition of .Net support with NuGet, OSGi and P2 hosting in the open source version, and artifact popularity scores calculated from their frequency of access and cross references in POMs. Read on to find out more.
Simon Cropp has released an IL weaving tool that wires property changed notifications into automatically implemented properties. IL weaving is a technique in which the IL code in an assembly is rewritten to add functionality.
CloudBees releases Jenkins Enterprise which offers commercial support, extended long time releases up to a year and extra proprietary plugins useful to companies with large scale Jenkins installations.
Imagine you are doing maintenance on an application from the late 90’s that uses the classic ADO libraries. The recompiled code works fine on any Windows 7 SP1 machine, but mysteriously crashes on the Windows XP machines that have been running the program for nearly a decade. This is the problem facing lots of maintenance developers.
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.
Sonatype, the main company which drives Maven development, has joined a growing list of companies which aim to help organisations understand and audit their open source software usage, with the announcement of the Sonatype Insight software suite.
Sonatype and Oracle have joined forces to provide stability and quality to Java.net Maven artefacts. A Nexus Pro instance now hosts the artefacts at Java.net, and they are synchronised into Maven Central for widespread consumption.
At a recent Jenkins meeting, the discussion turned towards whether a reconciliation with the Hudson project was possible (after the Hudson proposal to move to Eclipse.org was released), and what would be required for that to happen. The stated requirements appear to be in conflict to moving towards either Eclipse or Apache foundations, and therefore in a reconciliation with Hudson.
As the discussion in Agile development moves from continuous integration (CI) to continuous deployment, CI servers are doing more to automate the overall build process. Atlasian, which today released Bamboo 3.1, has implemented a new feature called Tasks that the company hopes will aid developers in their continuous deployment efforts.
With the recent proposal to move Hudson to the Eclipse Foundation, there has been speculation as to whether this will lead to a coming together of Jenkins and Hudson, or even whether the code can be relicensed under the EPL. A discussion is taking place later today on the Jenkins IRC channel to discuss whether the Jenkins community wants to be part of this or not.
Oracle has created a proposal to move the Hudson project, including ownership of the trademark and domain name, to the Eclipse Foundation. In addition to the existing commercial backers (Oracle and Sonatype), other commercial supporters are keen to see Hudson move to an independent organisation and process, and will also be adding committers to the project.
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.
Late last month Google released Guice 3.0, a Java framework that implements the dependency injection (DI) design pattern. The motivation behind Guice was to make it easier for programmers to write DI code by reducing the need to write boilerplate factories. This article examines the new 3.0 features, loks at how Guice 3.0 supports Spring DI, and introduces Guice 4.1 (a.k.a. MiniGuice).