A bit of self promotion ahead, my company, Simula
Labs, is listed as 4th in this Ten
Leading Open Source Innovators report, over other companies like
In the conclusions
you can read how last year trend with big companies like Oracle, Sun
or IBM pushing for open source it’s going to continue this 2007.
I’ll be at EclipseCON
March 5th-8th in Santa Clara, CA. You can meet me for
first hand info about Maven, OSGi, and Eclipse integration, just
leave a comment or ask for me at the SimulaLabs
booth, or look for me near the bar ;)
It’s gonna be a fun trip for me, I’m gonna drive from Los Angeles
up the coastline the weekend before
and down the weekend after, and hopefully drive around San Francisco
and Napa or Sonoma.
See you there!
Now, time to work in 2.0.6 and 2.1 ;)
The Apache Maven team would like to announce the release of Maven 2.0.5.
Maven 2.0.5 is available for download.
is a software project management and comprehension tool. Based on the
concept of a project object model (POM), Maven can manage a project’s
build, reporting and documentation from a central place.
The core release is independent of the plugins available. Further releases of plugins will be made separately. See Plugin List for more information.
We hope you enjoy using Maven! If you have any questions, please consult:
For news and information, see:
2.0.5 Release Notes
Changes in this release: Issue Tracker Release Notes
Changes that may affect existing builds
- Maven now behaves in a defined way when matching the nearest
dependency when two exist at the same depth in the dependency graph, by
matching the first encountered. Previously, it was undefined. This may
result in some builds having a different dependency graph, which could
cause failures if all compilation dependencies are not specified
completely in the POM. While not currently enforced, projects should
always list the dependencies it needs to compile, even if they are
- The handling of build extensions has changed. This technique causes
less pollution to the global classloader, allowing them to be used more
widely for extensions to Maven’s core. This may affect builds that used
them to expose extra classes to various plugins. While in most
scenarios these builds will continue to work, in these situations the <dependencies> element of <plugin> should be used instead.
It has been a long time since last entry, lots of things happened
since, I’ll try to post more often… promise!
What I’m working on right now is OSGi and Maven integration. Goal:
to generate automatically OSGi compliant jars from Maven projects and
vice versa, and make the Maven Repository also a OSGi bundle
You can take a look at the Maven
repository that contains Eclipse OSGi bundles, with poms
generated from the manifest information and the Felix
Maven bundle plugin that I’m improving to make everything more
automated and better integrated.