To improve the experience for users in Europe, Sonatype has provisioned a new official repository in the United Kingdom. This is more than a mere mirror of Central, this system is updated in lockstep with the systems here in the US, and is managed and monitored 24×7 by Contegix, the same team watching over the US repositories. The new repository consists of two fully redundant systems running in parallel to provide complete fail-over capacity.

In addition to the new repository, we have taken several steps to improve and further secure Central itself:

• A new system has replaced Central as the inbound processing engine. On this staging system, we can now vet inbound artifacts for quality and other parameters before publishing them to repo1 and Europe. It also serves as a hot standby for the US repository.
• We’ve worked with Contegix to implement additional layered security around the repository machines themselves.
• There is a new Jira project to manage any and all concerns and issues with Central, the Mirrors, Content, etc
• We are working to setup another official Central Repository in Asia soon

The new repository is live at http://uk.maven.org/maven2/ if you’re using a repository manager, just replace references to http://repo1.maven.org/maven2 with the new url. If you’re not, you should be (Whitepapers: Intro to Repository Management / Stages of Repository Adoption), but until you get a repository manager in place, add the following to your settings.xml:

<mirrors> <mirror> <id>uk</id> <mirrorOf>central</mirrorOf> <url>http://uk.maven.org/maven2/</url> </mirror> </mirrors>

Some additional coverage on this topic can be seen at InfoWorld, BusinessWire and InfoQ

Maven 3.0

With Maven 3.x we have made our best attempt to listen to users, find out what they need and want, and make reasonable preparations and plans to fix the problems, implement useful features, and create the integration points for working properly with third-party systems like Nexus and Hudson. While there have been many new feature requests — and we have many new features done or in the works — the number one concern is backward compatibility. Maven 3.x makes an ardent attempt to be 100% backward-compatible with Maven 2.x. All your Maven 2.x builds should work out of the box using 3.x without change to your projects. We simply can’t cause pain to the existing user base. We are very cognizant that even small changes can have a huge impact and so we have tried achieve complete Maven 2.x fidelity with Maven 3.x.

In Maven 3.x we have reduced the number of modules, we have simplified and extracted the artifact resolution system, we have put a performance framework in place, and we have created an enormous set of integration tests for Maven’s core and for many of the core plugins. We are constantly trying to validate core features and core plugins are working properly. We hope with the simplifications that we have made that more people will get involved in the project. We have done some heavy overhauling of many of the internals to make way for future features and I believe Maven 3.x is really the only path forward for Maven. What’s the technique we used to decide on how to plan and work toward the completion of Maven 3.x? A very practical approach to determining an optimal path called desire lines.

Desire Lines

A desire line usually represents the shortest or most easily navigated route between an origin and destination. The width and amount of erosion of the line represents the amount of demand. The term was coined by Gaston Bachelard in his book The Poetics of Space. Desire lines can usually be found as shortcuts where constructed pathways take a circuitous route. A concrete example: the pathways around the Berkeley campus in California. During the early years of Berkeley no pathways were paved. Instead they let inhabitants walk in optimal paths between the buildings and location over a period time to form clear pathways over the grass. Once these pathways had been established they could be paved to make the pathway more permanent. This is very similar to what happened with Maven 2.x. Consider Maven 2.x the pathways marked in the grass. Consider Maven 3.x taking all that learning from Maven 2.x and adopting the optimal form of use and codifying those forms of use i.e. paving the desire lines.

Over the course of hundreds of thousands of people using Maven we have a very good idea of what these optimal pathways look like now. Here are a few examples of some of the things we’ve seen and the things we have to do in order to make these lasting improvements.

Responding to invitations for improvement

There are many things in Maven 2.x that work reasonably well but have some minor flaws which cause irritation:

• Dependency management. How to effectively manage what we will call a target platform (intentionally using the Eclipse nomenclature). It is easy to manage the versions of an applications runtime or its target platform. But what happens when you start pulling in multiple, separately developed target platforms.
• Version specifications and version ranges. Maven’s notion of this is workable, but when it comes to the version specification and ranges it’s time to just defer to OSGi in this regard. What OSGi specifies and what Maven specifies are not wildly different but different enough to cause some problems. We’ll be working on aligning Maven to the version specification of OSGi.
• The way plugins interact with embedded environments was just wrong. We allowed for no support for incremental changes. The result is that in M2Eclipse when you change an individual resource, that individual resource can be processed efficiently and not fire up all of Maven to run the whole build lifecycle. Sorry, but you won’t have time to get a coffee anymore.
• There are slew more, but we’ll save those for other blog entries.

Responding to … being completely wrong

There are some things in Maven 2.x we just didn’t get right and we have to make reparations:

• Composition versus inheritance in the POM. There are some great debugged toolchains like we have in the Apache Organization POM for releasing, but this toolchain is not easily consumable by outside projects because it makes no sense to inherit from the Apache Organization POM for your projects. So how can we make these chunks of debugged combinations of plugins and their associated configuration? We will introduce mixins to help with this. Essentially it will be a POM consisting of plugins and configurations that can be externally parameterized. These mixins will be deployed to a repository and be referenced with a standard coordinate. Basically it will be an intelligent import with validation which will allow composition in your POMs.
• Checking out the whole source tree versus an individual module and parent element versioning. We have always intentionally made projects specify versions in the parent elements. When you check out individual modules this is necessary. But for projects where the whole source tree is checked out, the version of the parent can be inferred and the requirement for specifying the version element in the parent can be removed.
• Clean separation of operations that need to happen at the beginning and end of the lifecycle versus in the lifecycle itself. To make the OSGi integration we created work we needed to get at the projects before the build lifecycle was executed so we added a clear hook before lifecycle execution. What we have done to make OSGi integration work in Maven 3.x is simply not possible in Maven 2.x. We also had a terrible problem with reporting and aggregation because there was no clear point at which the lifecycle was over. Now once the build lifecycle is complete there is a clear hook to get the projects in the reactor so they can be processed easily. Accurate aggregation is now possible.

• Again, there are slew more, but we’ll also save those for other blog entries.

Responding to under-utilization of what exists

Unfortunately there are still a lot of powerful features and plugins in Maven that a lot of people don’t know about. We have tried to remedy this situation with the four books that we constantly update stream, and a stream of blog posts, and the soon to be enterprise Maven users list which will focus on the holistic and systematic use of Maven, M2Eclipse, Nexus and Hudson. We need to do a better job explaining end-to-end best practices for developing, testing, and provisioning software. We also need to do a better job describing some of the incredibly useful plugins we have like the enforcer plugin and the dependency plugin.

But again, our best attempt to show people what is available through the four books that we have:

• Maven: The Definitive Guide
• Repository Management with Nexus
• Developing with Eclipse and Maven
• The Maven Handbook

Here is a picture I always use to illustrate the point that even though something may be sitting directly in front of you, it’s not always immediately obvious unless someone points it out to you. Th is is very much the case where we see users asking us for help with particular use cases and in frequently it’s very easy to answer the question by pointing to a URL. My example is the Fedex logo which was designed to have an arrow being formed between the last two letters of the logo. Quite ingenious but most people I point this out to haven’t notice it.

We are going to try a lot harder to make sure the value that exists is easier to find. I don’t enjoy reading blog posts from unhappy users at all, but I especially don’t like it when I know there is a solution which has been documented somewhere. Those painful situations can be reduced if not eliminated completely.

Backward Compatibility

I can’t stress enough how important backward compatibility is to us. We have done a non-trivial amount of work to pave the way for new capabilities in Maven 3.x while preserving 100% backward compatibility for:

• Maven itself and the behaviour that users expect from the CLI
• Artifact Resolution API
• Plugin API
• Plugin configuration
• Site generation (even though we’ve extracted site/reporting entirely into the maven-site-plugin)

We must ensure that plugins and reports written against the Maven 2.0.x APIs remain viable in 3.0. We don’t want people rewriting their plugins or having to change their projects at all or it will simply be chaos. We simply have too many users and requiring changes will have an enormous human cost so we’ve been slow in announcing Maven 3.x. The version of Maven 3.x you can pull from the Sonatype grid is probably the best version of Maven that has existed but we are still being careful about releasing it. If you want to try it you can find it here.

We must also ensure that POMs of version 4.0.0 are supported in 3.x along with the behavior currently experienced. We will need to make changes to the POM in order to introduce many of the new features so we’ve made the requisite preparation. We are relying heavily on our integrations tests right now but as we move forward the work that Benjamin is doing on the project/model-builder will help us to accommodate different versions of a POM, and different formats we decide to support. The model-builder code has no limitation with respect to formats. We can support XML, or any source that anyone can dream up. These implementations may find use outside of Maven. For example someone might build something with the Maven, JRuby, and Mercury to create a JRuby-based system. The same could be done for Groovy. We already have some examples of this with the Polyglot Maven project we’ve started which will be the topic of a subsequent post.

We have managed to keep almost everything backward compatible and we will go so far as to provide an isolated execution environment that can contain older versions of the plugin API so that everything from the past can continue to work in Maven 3.x. We will not truly be able to do this until we change the internal Maven runtime over to OSGi but we know what needs to be done.

Integration Testing

An enormous amount of time and energy has gone into improving the the integration tests for Maven. The integration tests are the gatekeeper and let us determine that we have a Maven 3.x that is compatible for Maven 2.x. We now have 506 integration tests that will help protect us as we move forward. We will likely approach 600 integration tests by the time we reach the Maven 3.0 GA.

All core Maven plugins now have ITs and we have started branching out into the Mojo project to create plugin ITs there as well. We have a good pattern so we are encouraging anyone writing a Maven plugin to create ITs so that we can help ensure we don’t break people in the future. We have really taken fixing the problems we see seriously. I couldn’t help but make a little spoof of the SNL skit and adapting it for the Maven perspective.

In the next post I will start talking about some of the technical changes we have made to Maven 3.x in order to achieve our goals. Those will include:

• Refactored model/project builder (the support Polyglot Maven uses)
• Queryable lifecycle
• Lifecycle Extension points
• Error and integrity reporting
• Mercury: Jetty Client & SAT4J
• Embedding
• Incremental build support (used heavily in M2Eclipse for performance improvements, these are changes to the plugin API)

I plan to try and write something about Maven 3.x frequently in preparation for the Maven 3.x talks in Stockholm, Dusseldorf, Cologne, and Devoxx.

Stay tuned!

• Proxy Repository Browsing – With Nexus 1.4, the local cache and logical index views have been separated into separate tabs. We found that the previous single tab with a combo box to select the source was confusing.
• Publishing Web Sites to Nexus Professional – Nexus Professional 1.4 provides you with a WebDAV endpoint for publishing a web site. You can configure a Site repository that can be used as a publishing destination for project documentation. This means you don’t have to worry about providing some alternate solution to host your reports. The full support of Nexus security applies to this new type of repository, so you can control access at a very fine grained level.
• Repository Configuration Changes
  • Fine-grained control of Redeployment for Hosted Repositories: Nexus 1.4 provides administrators a simplied way to control how a hosted repository deals with the redeployment of artifacts. You can configure a repository to allow for the redeployment of previously deployed artifacts, allow for one-time deployment, or to provide a read-only interface for clients.
• Improvements to the Staging Plugin – The staging plugin had numerous improvements in the 1.4 release to increase usability and provide new functions for staging artifact bundle and verifying that staging repositories follow user configurable rule sets.
  • Support for Staging Rulesets: Nexus Professional 1.4 provides administrators with the ability to define a set of rules to apply to staging repositories before they can be promoted. The 1.4 release can validate that staging repositories contain valid POMs, valid PGP signatures, javadocs, and sources for all artifacts. The rules are pluggable and we expect to add more rules in the near future to support the Apache repository and our OSS hosting repository
  • Support for Uploading Artifact Bundles: The staging plugin now accepts artifact bundle uploads. Artifact bundles are archives which contain one or more associated artifacts, they are used to publish artifacts to the Central Maven repository, and you can use Artifact bundles to validate artifacts uploaded to Nexus.
  • General Usability Improvements in the Staging Plugin: This release of the Staging plugin focused on usability, the Staging plugin is full of improvements that make the user interface more intuitive and easier to use.
• User Account Plugin – The User Account Plugin in Nexus Professional gives unauthenticated Nexus users the ability to sign-up for a Nexus account. When this feature is enabled, a new user would click a sign-up link, fill out a simple profile form, read a captcha, and then activate a new account via an email confirmation message. Nexus Administrators can configure the default roles and permissions that are granted to newly signed up users.
• Repository Summary Panel – The repository summary panel provides statistics and configuration information for a specific repository. Users can consult the repository summary panel to gather the necessary distribution management settings for Maven configuration.
• Security Improvements – Many improvements to the user security model. In general, it is now easier to configure custom role mappings for externally managed users, and Sonatype has paid close attention to the user interface for managing users and roles. It is easier than ever to configure and secure a Nexus repository.
  • New User Role Tree: Click on a user and then click on the user role tree to see how each role contributes to the permissions for a particular user.
  • New User Privilege Trace feature: this features allows Nexus administrators to pinpoint which roles contribute which permissions to a particular user. While the user role tree provides an intuitive interface that lists role in a hierarchy, the privilege trace panel under user administration provides an alternate view. Click on a particular permission to find the roles contribute that permission to a user.
  • New Role Tree: Since a Nexus role can consist of both roles and privileges, we’ve provided an intuitive tree browser that allows an administrator to browse the hierarchy of roles and privileges associated with a Nexus Role.
  • Fine-grained control of View Repository Privilege: Nexus added the ability to configure a role to prevent users from browsing particular repositories. This is used to provide a cleaner view to users, for example to show them only groups they use via Maven and not confuse them with all the repositories aggregated by that group.
• Integration with Atlassian Crowd – Atlassian Crowd is a capable user and directory management system that can consolidate authorization and authentication to a central server. Nexus Professional’s Atlassian Crowd plugin provides seamless integration between Nexus and Atlassian’s Crowd server.
• Automated Nexus Error Reporting – Nexus 1.4 ships with an automated error repository system which can be configured to report Nexus exceptions and errors to the Nexus Issue Tracker. If configured, the system will send data to Sonatype’s Jira instance. The information contained includes the configuration (all passwords are obfuscated) as well as a file list of the repositories and exception traces. All of this data is encrypted using public-key cryptography so only Sonatype can view the contents. We expect that this information will allow us to further refine the stability of Nexus.
• Upgrades to the Nexus Book
  • A new chapter on Nexus Best Practices.
  • A new chapter on publishing web sites to Nexus.
  • Over 100 corrections and clarifications.
  • Over 80 new figures and diagrams.
  • Addition of a New Nexus Book Cover with the Nexus Logo
  

Sonatype Maven Meetup will focus on technologies centered around development infrastructure, offering talks and workshops led by core contributors and package maintainers. Sessions in two tracks will cover tools as the Apache Maven build and release manager, Hudson continuous integration engine, Nexus repository manager, Sonar quality server and other technologies widely used by software developers around the world.

Read more

Blogs

Vaadin blog: Vaadin 6.1 goes to Maven and adds Google App Engine support “It is now easy for Maven users to enhance their web projects with Vaadin user interfaces. The latest 6.1 version of the Vaadin Java web library is now available also for Maven users, via the Maven central repository.” by Sami Ekblad September 10, 2009 9:34 AM

The Lazy Dev: Wicket Stuff Core – Maven2 generated site “Maven2 has a power site generation tool. I cannot find this on the web for wicketstuff-core so I checked out the whole svn trunk and generated it on my machine. First news, it worked perfeclty Second, the generated site is very helpful in understanding what stuff are available for wicket.” by Daniele Dellafiore on September 9, 2009

The Lazy Dev: Use update-alternatives to upgrade maven installation on Ubuntu “Use debian update-alternatives to easily swith from different version of the same program you have installed on your machine. Or, more frequently, just to switch to a new version in a fast and clean way. Let’s make a simple example with maven.” by Daniele Dellafiore on September 2, 2009

Stash’s Development: Playing with Scala and Maven “Recently, I’ve taken up an interest in Scala and wanted to try it out with Maven. Luckily, people have already blazed this path for us by developing a Scala plugin for Maven. In this post, writing as I go, I’m going to play with what we can do with this plugin to get started.” by John Prystash on Sunday, August 23, 2009 at 1:40 PM

Next Presso: WTP + M2eclipse + Seam : Maven works! “Lucky me ! It’s only now that I need that one of my Seam project works with Eclipse WTP and Maven. Lucky because a few months ago, that tutorial would have been impossible to write. This article will show how to adapt a JEE5 project in order to make it usable with Eclipse WTP and Maven.” by Antoine Sabot-Durand on June 29th, 2009

JetBrains Zone: How to use Intellij IDEA and Maven 2 together for debugging and context help “Latest version of Intellij IDEA has excellent integration with Maven 2. I want to explain one tip that could help you to gain productivity.” by Alexander Shvets on Mon, 2008/02/11 – 11:22am

Tweets

neotyk: Advice for #Maven #MOJO #Plexus users, try sticking to defaults. Will save you lots of time. Tuesday, September 15th at 14:51:22

david_horwitz: learning to love the maven assembly plugin Tuesday, September 15th at 14:40:52

aheritier: +1 RT @jvanzyl:The Loving Iron Fist of Maven. The Enforcer Plugin is probably the most under utilized plugins there is: http://bit.ly/23mL5 Tuesday, September 15th at 14:37:03

SciComp: pf9 [maven-release-plugin] copy for tag sns-translation-client/2.13.3 http://tinyurl.com/TSchg/4334 Tuesday, September 15th at 13:58:32

mentby: How do you release your projects? #maven http://bit.ly/1COTwe Tuesday, September 15th at 13:05:53

evenisse: Useful Maven Plugins: Part 2 http://bit.ly/itG68 Tuesday, September 15th at 13:05:50

antoine_sd: @jlrigau thanks for RT #WTP #M2eclipse #Seam #Maven http://bit.ly/E4ZN5 Tuesday, September 15th at 08:08:35

bubbl_scala: Running Scala specs tests in Maven with JUnit 4 – mccv http://ff.im/-88qza Tuesday, September 15th at 05:56:16

aikisteve: Gonna put Maven into the project today. And then test the deploy on a local server. Hope it works out like a charm Tuesday, September 15th at 05:28:01

kevinSuttle: @bpanulla I like to write Ant Tasks by hand (at least at first). Does Maven offer something better as far as GIT integration? #n00b Tuesday, September 15th at 05:20:30

virtualandy: Silly question – do I have to download the GMaven src & build? Or is there a .jar that I just can’t seem to find on codehaus? #groovy #maven Tuesday, September 15th at 03:17:25

yyamano: Should we use http://repo1.maven.org/maven2/org/apache/velocity/velocity/ instead? Tuesday, September 15th at 01:41:10

steffeng: Impressed by apache http://hudson.zones.apache.org/ and sonatype https://grid.sonatype.org/ci/ continuous builds. Sort of entertaining. Monday, September 14th at 22:43:12

stuartsierra: Built custom #clojure #maven plugin with REPL & non-submodule #swank http://bit.ly/yil7g Monday, September 14th at 21:58:31

stuartsierra: Building parent #maven POMs for AltLaw.org, custom builds of #swank #clojure #hadoaop Monday, September 14th at 21:13:09

avinashmeetoo: Maven: The Definitive Guide | Sonatype: Maven and Nexus: Enterprise build and release management http://ff.im/-86QFt Monday, September 14th at 19:04:27

thierry_n: Today I had the opportunity to use the scope “import” introduced in #maven 2.0.9… Useful … Monday, September 14th at 18:41:02

AntonKronseder: Stumbled over a nice trick to disable an inherited #maven plugin: add a plugin element with an execution for pahse ‘none’. Works great. Monday, September 14th at 16:47:59

Steve_Oakley_: is looking for a snr J2EE developer for large co’ in NL. Fixed location. Websphere, Junit, Maven and Flex. Contact me to discuss or refer? Monday, September 14th at 15:56:11

SciComp: pf9 [maven-release-plugin] prepare for next development iteration http://tinyurl.com/TSchg/4328 Monday, September 14th at 15:52:05

fmcypriano: @graemerocher What changed in maven plugin 1.1? Is it working with Grails 1.2? Monday, September 14th at 15:24:31

graemerocher: Done releasing version 1.1 of the Maven Grails plugin. Will take a little while for it to propagate to the central repo I guess. #grails Monday, September 14th at 15:16:07

jlrigau: Good article (fr/en): #WTP + #M2eclipse + #Seam : c’est bien #Maven ! « Next Presso http://bit.ly/E4ZN5 Monday, September 14th at 15:18:50

jlrigau: Very usefull for #Maven users: Sonatype Nexus Maven Repository Manager http://bit.ly/tS6hL Monday, September 14th at 15:38:51

bfhall: Maven profiles rock! Lots of power and relatively easy to use. Monday, September 14th at 15:00:22

munkius: @larsvonk then go for a parent pom. You can check apache maven artifacts for an example. In the parent you can include shared dep’s & stuff Monday, September 14th at 14:22:49

peter_pilgrim: RT @jvanzyl: I’ll be at Skills Matter tonight giving a talk on Maven, M2Eclipse, Nexus and Hudson: http://bit.ly/27Z5YL (Jason Best Luck!) Monday, September 14th at 14:07:16

prauber: what is the advantage of maven? it downloads all dependencies itself. what is the disadvantage of maven? it downloads dependencies itself. Monday, September 14th at 12:46:32

munkius: @larsvonk check out nexus as a maven repository manager. You can auto-feed this by your ci-system Monday, September 14th at 12:34:54

alblue: RT @benoitx @jvanzyl Looking forward to the Maven talk tonight at #skillmatters <<< wish I could be there, hope it goes well Monday, September 14th at 11:56:38

antony: RT @graemerocher: Working on releasing the 1.1 version of the Grails maven plugin to the Codehaus repos <– My hero Monday, September 14th at 11:09:26

javatv: #java New video: Using the Naked Objects 4.0 Maven Archetype http://bit.ly/12a19a Monday, September 14th at 10:54:41

graemerocher: Working on releasing the 1.1 version of the Grails maven plugin to the Codehaus repos Monday, September 14th at 10:52:15

jvanzyl: I’ll be at Skills Matter tonight giving a talk on Maven, M2Eclipse, Nexus and Hudson: http://bit.ly/27Z5YL Monday, September 14th at 10:36:53

delicious50: M2Eclipse: Home http://bit.ly/gSvGd eclipse maven plugin Monday, September 14th at 10:23:06

jneira: M2Eclipse: maven plugin for Eclipse Home http://tinyurl.com/mepnhz Monday, September 14th at 10:22:42

olivergierke: Btw. probably was unfair to @m2eclipse… They moved to jira.sonatype.org… Was really hard to find out at the old Codehaus one… Monday, September 14th at 09:31:46

erani01: Searching how to build custom package with Maven Monday, September 14th at 07:20:49

anpieber: couldnt there be a forced guidline for apache projects to use maven?!?!? Tried to build ode; buldr… hurray yet another build tool… Monday, September 14th at 07:23:27

nerdgerl: playing round with clover – trying to get it to work with multi-module maven project Monday, September 14th at 06:58:17

dirmgr: Just released UnboundID LDAP SDK for Java 1.1.0. Includes LGPLv2.1, Maven & OSGi support, and more. http://tinyurl.com/kukzkb Monday, September 14th at 06:45:18

mediaslave: #Scala and #Lift are nice. Like the frameworks they use, blueprint, jquery, etc. Plus jvm and maven integration. need to explore them more Monday, September 14th at 05:56:39

i386: now @zhasper and I are configuring the maven-compiler-plugin together. This is true love, people. Build love. Monday, September 14th at 04:58:47 – Reply – Retweet – View

i386: I cant beleive im helping @zhasper with Maven Monday, September 14th at 04:50:35

omargomez: Happen to be doing a compiler with ANTLR. Netbeans+Maven+ANTLR is just fantastic. Anyone knows a better tool? (even if not Java based) Monday, September 14th at 04:32:36

miztylaneous: brought Maven to work today. XD Monday, September 14th at 04:08:33

mwhooker: wow, Maven is actually kind of enjoyable to watch work Monday, September 14th at 03:51:05

Georg_Tavonius: I did it! Finally, I got NetBeans, Maven and Scala to work together and rendered my first website using Scala in the backend. #scala #maven Sunday, September 13th at 21:49:38

timperrett: Just finished refactoring a legacy project into Maven – despite its foibles its still miles better than Ant or plain ol’ Eclipse Sunday, September 13th at 20:18:41

burkewebster: Working on a Maven plugin for JsTestDriver Sunday, September 13th at 14:41:47

Exmatrikulant: Watching some presentations on slideshare. Topics: Maven, Ant, Nexus, Hibernate Sunday, September 13th at 14:21:19

timdrury: setting up Hudson, maven, and maven repo to build some tools, plugins used in SAP ME Sunday, September 13th at 13:58:54

flying_gramma: http://tinyurl.com/qwcyqm How to use Intellij IDEA and Maven 2 together for debugging and context help | JetBrains Zone Sunday, September 13th at 10:05:10

gdickens: Is there any way to generate a maven pom file from a project in Eclipse or IntelliJ #maven #eclipse #intellij Sunday, September 13th at 15:30:04

acdog: [yescache] http://bit.ly/11HHlM Artie Copeland – fixed terracotta caches to support terracotta 3.1.0 updated to use oss.sonatype.org ren … Sunday, September 13th at 01:05:17

marktakala: Much of the OSGi metadata drudgery is relieved by Maven plugins, some written for Apache Felix OSGi container; others are provided by Sling Saturday, September 12th at 21:14:28

onekilo79: parallel junit 4.7 via maven and spring 3.0 http://bit.ly/1aeadv hopefully will be included in future releases Saturday, September 12th at 21:13:38

game_flash: Continuous Integration with Maven, Flex, Fliunt, and Hudson http://bit.ly/3Q4DBY Saturday, September 12th at 19:43:32

blojsomdev: r3720 provides the upgrade utility as a maven project. Need to push some snapshots to the #artifactory repos before you can use it. Saturday, September 12th at 16:16:52

acdog: [yeslib] http://bit.ly/1ZWhEI Artie Copeland – added oss.sonatype.org repo Saturday, September 12th at 14:03:28

davecheney: Playing with maven and github, http://bit.ly/1zGmAc Saturday, September 12th at 06:20:04

kevinmook: Complete Google App Engine + Lift + Maven project zipped up (Eclipse friendly): http://bit.ly/2x7lKy Saturday, September 12th at 05:09:03

JavaChilly: O’reilly to the rescue: Maven, Dojo, Javascript definitive guides AND Practical Perforce. Reference at hand –check! Saturday, September 12th at 01:37:27

acdog: [jmlnitrate] http://bit.ly/Ncc74 yestech – added gpg and other pom artifacts so it can be relesed to oss.sonatype.org Saturday, September 12th at 06:53:10

rpanachi: #maven funciona mas é muito complicado. hora de mudar para #buildr http://buildr.apache.org/ Friday, September 11th at 18:51:16

nwkr: @kbrazulewicz : One of the #Atlassian #Maven servers provides invalid data. My solution may be also proper for #Confluence. www.tiny.pl/hqgwt Friday, September 11th at 15:09:24

AntholoJ: looks like am starting to <3 #maven thanks for the good #netbeans integration Friday, September 11th at 13:01:09

krimple: For my own reference as well, #flexmojos information #flex https://docs.sonatype.org/display/FLEXMOJOS/Home Friday, September 11th at 12:30:01

joonaslehtinen: #Vaadin + #Maven & #Vaadin + Google #AppEngine micro-howtos: http://tinyurl.com/nsypfr Friday, September 11th at 10:30:56

jvanzyl: People really like the Sonatype FlexMojos project: http://bit.ly/SNXuc Friday, September 11th at 09:05:10

jfiset: @scott_lowe We’re about to implement Flex-10, #nexus, and NetApp for vSphere over the next few weeks. should be fun. Thursday, September 10th at 23:29:38

Han_Cholo: Got #Nexus and half way through with #Hudson. Thursday, September 10th at 22:14:27

Han_Cholo: Installing #Nexus and #Hudson. Thanks @scottawilliams for the help on getting started. Thursday, September 10th at 18:26:38

nwkr: in #IntelliJ IDEA CTRL+SHIFT+F9 in debug mode is very useful while developing a #JIRA plugin. No need for rebuilding whole #Maven project. Thursday, September 10th at 17:23:00

neotyk: RT @stuartsierra: #maven enabled swank #clojure fork http://bit.ly/3mY3OT Thursday, September 10th at 16:37:19

vincentkok: @stuq just tried this one: http://m2eclipse.sonatype.org/ and you should have a look at SpringSource #sts too Thursday, September 10th at 12:17:43

karianna: Battling various #Maven plugins – really annoying when you see issues fixed but no-one merges the patches in Thursday, September 10th at 11:47:09

brettporter: @cziegeler are you sure? OS X version 10.5.8 and 10.6.0 both install #maven 2.0.9 here Thursday, September 10th at 11:33:59

talios: #maven enforcer rule API looks simple enough I should be able to solve my needs easily if theres no third-party rules. Thursday, September 10th at 10:29:18

coffeecoders: Read #Maven: The Definitive Guide online or download the PDF for free (English,German and Chinese) @http://tr.im/yk3B #props to sonatype Thursday, September 10th at 09:07:12

ildella: Upgrade #maven on Ubuntu: http://bit.ly/3udpWJ Thursday, September 10th at 08:35:47

vishwajeets: @mrdonbrown thanks for your support I have only one small concern that docs should stress more on using atlas wrapper commands for maven Thursday, September 10th at 07:52:49

cambo_sareuon: @leejava If you want to know more about Maven go to http://bit.ly/xgZ9H Thursday, September 10th at 03:55:47

bubbl_scala: Stash’s Development: Playing with Scala and Maven http://ff.im/-7RVqf Thursday, September 10th at 02:36:37

brettporter: if you’re looking to fail a build, you’ll want to use the Maven PMD plugin and write a rule for it. Thursday, September 10th at 01:00:25

steffeng: Having fun with #hudson’s #maven integration internals. Anybody using hudson with maven > 2.1.0? I need a hand: http://is.gd/35HIy Thursday, September 10th at 00:09:53

talios: lazyweb – Is there an Apache Maven plugin to fail a build a certain codefragment/constructor is called? I know aspectj has something… Thursday, September 10th at 00:05:56

stuartsierra: Wrestling with #maven #clojure #hadoop http://bit.ly/2UAW6H Wednesday, September 9th at 22:12:38

stuartsierra: #maven enabled swank #clojure fork http://bit.ly/3mY3OT Wednesday, September 9th at 15:11:07

rystraum: is checking out apache #archive, #maven and #continuum. Wednesday, September 9th at 13:33:18

dsonpatricio: #maven: Pulando testes na hora de uma instalação de emergência: http://bit.ly/28vuOd Wednesday, September 9th at 13:33:14

giovanninappi: #Maven me place sempre plus… Anque si io non ha ancora trovate alcun guida vermente complete de nivello base Wednesday, September 9th at 09:16:57

devylon: RT @stuartsierra Updated #hadoop #maven POMs http://bit.ly/18BETG Wednesday, September 9th at 07:46:49

somkiat: mvn war:war =>export war file #maven Wednesday, September 9th at 07:43:15

Tunaranch: /me thinks #maven should stop using -SNAPSHOT plugins by default… Wednesday, September 9th at 04:39:16

itdnext: learning how to use #maven and enjoying it. Wednesday, September 9th at 01:50:20

Blogs

Upgrading Maven on Mac OS X “Upgrading Maven on Mac OS X is generally nothing very special, but I’d like to summarize the steps I’ve done. Maybe it is helpful for users which are not so familiar with the Terminal application.” by Moritz Petersen on September 5th, 2009 at 14:12

Maven project filtering “Depending on your project requirements/number of customers, you may have to support different target environment. This article will help you to make your Maven build a bit more portable in that sense. Maven can help you avoiding having stage dependent data across all your Maven projects/ modules very easily thanks to resources filtering.” by Walter Cedric on Saturday, 05 September 2009 13:43

Cutting-Edge Clojure Development with Maven “I promised, in my previous post, that I would show you how to use the latest-and-greatest versions of Clojure and clojure-contrib in your Maven projects. Here’s that post.” by Stuart on 04 Sept 2009

Automated Deployment with Maven – Going the Whole Nine Yards “This talk discusses a number of strategies for automating your deployment process, and shows how you can integrate CI tools like Hudson and Bamboo with other tools such as the popular JIRA issue tracking software for an (almost) seamless deployment experience. In particular, it will show in practical terms how to automate the deployment using Bamboo, JIRA and Nexus in a real-world multi-module Maven web application.” by John Ferguson Smart on Thu, 2009/09/03 – 1:00am

Maven’s Not So Bad: Further Thoughts on Clojure Package Management “Maven is a touchy subject. People tend to have strong opinions about it. But like it or not, it’s the de-facto standard for dependency management in the Java world. Clojure lives in the Java world, so that means we have to live with Maven.” by Stuart on 03 Sept 2009

Tweets

stuartsierra: Updated #hadoop #maven POMs http://bit.ly/18BETG Tuesday, September 8th at 22:03:57

hudsonci: @eciramella Yikes! Do tell! I hope you now think that #Hudson rocks as much as #Maven 2 though Tuesday, September 8th at 21:34:55

stuartsierra: More #maven fu, creating your own public repo http://bit.ly/26iBLg Tuesday, September 8th at 15:50:55

talios: Nice, Scott Fleckenstein just created a #maven archetype for my #clojure plugin – http://bit.ly/NTKta Tuesday, September 8th at 00:59:33

thragor: Reading how to test #Maven #Mojos http://is.gd/2ZNQQ and http://is.gd/2ZNVj Monday, September 7th at 13:25:31

lucabastos: Desenvolvedores Java. Maven The Definitive Guide, livro grátis da Sonatype. Última versão em http://bit.ly/y4e2p Monday, September 7th at 12:54:35

cynipe: the-definitive-guide-edition-071-released #maven http://bit.ly/4pV08y Monday, September 7th at 12:33:31

neotyk: Here is some useful documentation from #Maven http://bit.ly/ja9dT Monday, September 7th at 12:09:21

devylon: using maven since version 0.9.x, but never used the release plugin before today #maven Monday, September 7th at 11:54:40

thragor: Problems with #Maven and #Log4j 1.2.15 Dependencies? See here: http://bit.ly/2GXDfV Monday, September 7th at 11:51:04

GabrielCorpse: Developing with #Eclipse and #Maven http://bit.ly/12kUtM Sunday, September 6th at 20:24:20

torstenwerner: just blogged about 10 years in #Debian now http://u.nu/7ax53 – #Java #Maven Sunday, September 6th at 09:42:42

cedricwalter: http://tinyurl.com/lhb5e3 – Apache Maven project filtering: make your build portable and target any runtime environment (tips & tricks) Saturday, September 5th at 11:45:10

laurentkempe: @jrguay At Innoveo Solutions we use for both .NET and Java, Team City works great with Maven and Visual Studio solution Saturday, September 5th at 13:17:45

cloudme: New blog post: Upgrading Maven on Mac OS X http://bit.ly/EpvBz Saturday, September 5th at 12:41:32

cedricwalter: New blog post: http://tinyurl.com/nvdaqw – JSF static analysis in your build with Maven and JSFUnit Saturday, September 5th at 12:40:27

chrissearle: New post: Using maven-exec-plugin to store the current git sha in a build (http://ping.fm/WPMpK) Saturday, September 5th at 09:52:35

integratedarts: Messing about with #ableton and #dblue glitch – made a arpeggiated run with #nexus and routed aux out to #lexicon vortex then back in. Yeah! Saturday, September 5th at 05:41:38

jasondlee: Maybe someone listening will point me to an existing one. That would be awesome. #seam #maven #archetype #glassfish Saturday, September 5th at 04:13:11

site_news: learntechnology.net – Maven JEE (EBJ3 JPA) http://tinyurl.com/mjrvjh Saturday, September 5th at 03:18:27

stuartsierra: @dysinger I admit clojure-maven-plugin is lots of Java for a simple task, but maybe it’s good to enforce convention Saturday, September 5th at 01:27:00

dysinger: I would be interested in corkscrew if it did everything maven does @technomancy @bradfordcross Friday, September 4th at 22:59:38

bjagg69: Portal seems stable again. Back to tweeting … set up a maven proxy repository to make Oracle driver easily accessible Friday, September 4th at 22:55:16

alisohani: #Apache technologies that did & will change computing by @cutting http://bit.ly/mrbrx #struts #ant #lucene #hadoop #couchdb #maven Friday, September 4th at 22:51:28

olamy: RT @jvanzyl: 454 integration tests as evidence, we are very close to Maven 3.x be a drop-in replacement for Maven 2.x: http://bit.ly/6iQ8E Friday, September 4th at 21:43:31

talios: @stuartsierra @technomancy Using pure clojure code and the Maven Embedder could be an interesting route Friday, September 4th at 21:31:28

stuartsierra: @bradfordcross @technomancy #corkscrew is nice idea, but won’t fly unless it’s a #maven plugin Friday, September 4th at 20:39:53

stuartsierra: Using nightly #clojure and contrib builds in #maven http://bit.ly/19frrd Friday, September 4th at 19:14:59

stuartsierra: @dysinger @bradfordcross I think I prefer the #Clojure #Maven plugin over embedded Ant because it’s more declarative. Friday, September 4th at 18:03:46

coding: Ob wohl Google App Engine Projekte auch mit #Maven funktionieren? Gibt’s ein stabiles #Plugin? #GAE Friday, September 4th at 15:56:01

stuartsierra: http://paste.lisp.org/+1USG clojureshell-maven-plugin sample pom.xml #clojure #maven Friday, September 4th at 14:30:06

javawugcom: @jvanzyl Available now! Video of #Apache #Maven 3 talk from 17 June 2009, London #JAVAWUG http://bit.ly/xhI8A N-joi Friday, September 4th at 12:05:49

fahdshariff: mvn release:perform -Dgoals=deploy (to skip site-deploy) #maven Friday, September 4th at 08:00:26

stuartsierra: #Maven ‘s Not So Bad: Further Thoughts on #Clojure Package Management http://bit.ly/17pPFE Thursday, September 3rd at 22:40:16

Abderrazakk: Moteur de recherche Maven par Sonatype http://ff.im/7AHGE Thursday, September 3rd at 12:28:13

acampanario: discovering Apache Maven http://maven.apache.org/ via @jabad… thanks!!! Thursday, September 3rd at 08:05:41

NorseOne: Using the Naked Objects 4.0 Maven Archetype | Domain Driven Design using Naked Objects http://post.ly/3pOb Thursday, September 3rd at 07:36:24

LostInTangent: Can’t sleep so I’m watching a presentation on #Maven from the Seattle Java User’s Group (http://bit.ly/IuUxt) #SeaJUG Thursday, September 3rd at 07:34:37

taroleo: [B!] Maven – Guide to Working with Multiple Modules http://bit.ly/hJhxU Thursday, September 3rd at 04:27:45

Flexmojos: FlexPMD, never used but already liked. Why? Built using Maven + Flexmojos. Check is pom: http://is.gd/2OI0k Thursday, September 3rd at 02:26:41

paulosuzart: Is #maven better than #sbt for scala? I’m lefting sbt for a while. scala project with mvn see my slideshare (conejo). Thursday, September 3rd at 02:17:08

meowtaro: actually thinks maven 2 is kinda nice… Wednesday, September 2nd at 23:06:09

morlhon: Something i’d like to do with #maven possibly with #nexus : find all references of a given dependency within a given groupid. Wednesday, September 2nd at 11:56:04

ulysseskao: 分享 http:www.sonatype.com/people/2008/11/building-eclipse-plugins-with-maven-tycho/ http://plurk.com/p/1sazpe Wednesday, September 2nd at 11:39:13

taroleo: [B!] Packaging Java apps for OS X with Maven – simplericity http://bit.ly/uoquC Wednesday, September 2nd at 07:28:33

vaadin: RT @joonaslehtinen: The 6.0.x Vaadin releases and a sample archetype are now in the central Maven repositories (or being replicated to them) Wednesday, September 2nd at 07:18:03

taroleo: [B!] Maven IzPack Plugin – Maven IzPack Plugin – Introduction http://bit.ly/4cumZp Wednesday, September 2nd at 06:58:26

lachlanhardy: Holy Maven Resources Plugin, Batman! Can you say automagical version updating of JavaScript libraries on release? @i386 is my hero! Wednesday, September 2nd at 06:41:49

acdog: [maven-hibernate-search] http://bit.ly/KLB63 Andrew Wright – debugging. Wednesday, September 2nd at 05:43:03

talios: Wrapping up some code then heading off to the JUG. Gentoo+Java and EBean’s Maven Migration. Should be interesting. Wednesday, September 2nd at 05:10:44

wakaleo: Automated deployment with maven – going the whole nine yards: #agile2009 available online: http://tinyurl.com/nbqo7x #maven Wednesday, September 2nd at 04:20:34

xinotes: Maven dependency scopes http://www.xinotes.org/notes/note/583/ Wednesday, September 2nd at 02:46:43 Rnaufal: Using Maven for the first time..Very practical its dependency management (download and adding it to a Java project) Wednesday, September 2nd at 00:44:54

drewylui: RT @sarahmaddox: Just published: guide to using the new Atlassian Plugin SDK. Fun! Am now a Maven geek by proxy http://tinyurl.com/le48rh Wednesday, September 2nd at 00:36:58

Blogs

The importance of Central “One of the selling points of maven is it’s dependency mechanism. You say what code you need, and maven makes sure it’s there for you. The magic behind this is called central. It’s a phenomenal collection of software (much akin to Perl’s CPAN).” August 23rd, 2009 by Dominic Mitchell

Importing Flexmojos Projects to IntelliJ IDEA 8.1.3 “IntelliJ IDEA 8.1.3 includes initial support for importing Flex projects that are set up using Flexmojos Maven plugin.” August 17th, 2009 by AlexanderD

Nexus vs. Artifactory “There are multiple reasons for us to use a repository manager:

• Unified access to repositories
• Finer grained access control
• Automated creation of the Nexus index
• Web based artifact search”

June 16th, 2009 by Stefan Reuter

Tweets

indiwiz: Maven Profiles: Thanks to Arun Jeganath for making me understand Maven Profiles. Often we are forced to specify .. http://snipurl.com/rip78 Tuesday, September 1st at 12:22:37

Kenyth: maven 3.x Artifact resolution and repository discovery http://twitzap.com/u/eX8 Tuesday, September 1st at 10:17:25

akquinet: @clementplop iPOJO 1.4.0 is now available from Apache Felix downloads, Felix OBR and Maven repository. http://bit.ly/1GxamD #iPOJO #OSGi Tuesday, September 1st at 07:49:40

joonaslehtinen: The 6.0.x Vaadin releases and a sample archetype are now in the central Maven repositories (or being replicated to them). Tuesday, September 1st at 06:14:45

ealliaume: Maven:The Definitive Guide http://tr.im/xBRX Traduction du chapite 6 terminée… Tuesday, September 1st at 04:55:42

stuartsierra: Cool, Maven Definitive Guide is free- http://bit.ly/Erixp Tuesday, September 1st at 02:58:12

rawyler: Trying to configure a small #Scala project with #Maven and #Hudson. Pretty cool stuff. Monday, August 31st at 15:18:07

GabrielCorpse: Demystifying #maven http://bit.ly/4vZtHF Sunday, August 30th at 17:09:59

paulosuzart: Google App Engine using #maven http://www.salientpoint.com/blog/?p=480 but how to debug? jejejej Sunday, August 30th at 02:13:20

gabrielflores: aqui: #Maven #Flex Plugin http://icio.us/fhxvxt Saturday, August 29th at 21:06:08

gabrielflores: interesante #Maven #Flex #Plugin http://icio.us/ewuf0d Saturday, August 29th at 21:05:19

gabrielflores: LEYENDO ON LINE #Maven: The Definitive Guide http://icio.us/i3p3nr Saturday, August 29th at 20:48:06

GabrielCorpse: Maven archetypes for web applications http://www.webtide.com/resources/maven.jsp #maven Saturday, August 29th at 16:32:11

kyleburton: #maven is actually pretty nice for building our #clojure app…need to write up another blog post Friday, August 28th at 18:41:58

matthewmccull: Submitting a patch to #Maven SCM-495 to add password encryption to SCM providers (my tribulations): http://tr.im/xmhn Friday, August 28th at 16:42:31

vhle: My new favourite phrase that brings me joy every time I see it: “BUILD SUCCESSFUL” #maven Friday, August 28th at 01:34:05

wichit_sombat: mirror maven2 repositories on ubuntu server: sonatype nexus works!! http://bit.ly/leeRK Tuesday, August 25th at 18:33:39

ehsavoie: Maven Reporting Plug-ins, Part 1: Static Analysis Tools http://tinyurl.com/lew4kg #maven Tuesday, August 25th at 13:21:04

jlrigau: Sonatype Nexus Maven Repository Manager http://bit.ly/tS6hL Tuesday, August 25th at 08:54:37

glen_a_smith: Just released a new version of opencsv using Sonatype’s infrastructure. http://is.gd/2x1Tc From Nexus to maven central in <10 minutes! Wow! Tuesday, August 25th at 00:21:37

rantav: I’ve just installed Nexus the maven repository and had a wonderful experience. http://nexus.sonatype.org/ Looks like a kickass product Monday, Aug 24th at 14:49:00

happygiraffe: The importance of central: http://bit.ly/3Wmlib #maven Sunday, August 23rd at 22:36:00

mosabua: @tobrien Agreed. The Debian testing package is a bit more up to date. What I do though is http://tinyurl.com/lqp32g #maven #ubuntu #nexus Saturday, August 22nd at 16:10:29

This release includes some important bugfixes and other improvements, including:

Removed feature from 2.1.0 that resolved expressions in version elements within the POM on installation and deployment.

This code was causing inconsistencies between the POM that landed in the repository and artifacts that are derived from that POM. The most prominent example deals with the GPG plugin: since the POM was modified on deployment, the GPG signature generated during the build was useless. This by itself effectively made Maven 2.1.0 unusable for releases.

Switched to a HttpClient-based wagon implementation for reaching HTTP repositories.

This is crucial for people sending long passwords, since the HttpUrlConnection-driven wagon did not-nice things with BASIC authentication headers when the password was very long…it line-wrapped the Base-64 header value, rendering the HTTP request invalid. In addition, HttpClient offers a wide range of options for configuration over HttpUrlConnection.

New default execution IDs for goals bound from the default lifecycle mapping and those invoked from the command line.

Previously, the only way to configure plugins that were used from the command line was to put the configuration options into the plugin-level configuration. This meant that it was impossible to separate CLI-oriented configuration settings from those used in goals that were bound to the lifecycle. Now, you can simply use an execution block with an id of default-cli to compartmentalize CLI-specific options.

Likewise, Maven 2.1.0 forces users to add configuration at the plugin level for any goals bound to the build via default lifecycle mapping. This could be particularly troublesome when you had multiple goals from a single plugin bound in via lifecycle mapping, and needed to respecify the same configuration option differently for the different goals. For instance, using different includes or excludes between the compiler:compile and compiler:testCompile goal executions was basically impossible. In Maven 2.2.0, you can use executions with the new per-goal default execution-Ids. For the compiler example, you can use default-compile and default-testCompile, respectively, to separate configurations for these two default goal executions.

Java 1.5+ is now a requirement.

Maven 2.2.0 upgrades the Java requirement to 1.5 or later. This allows us to finally start making the migration onto the Java5 generics syntax, and other nice little perks that come with a less archaic version of Java.

…and more…

For the full list of updates, see the Release Notes.

The Nexus 1.3.3 Pro release includes enhancements to allow validation of PGP signed artifacts, and block access based on the results of that check. This release also adds an enhanced set of capabilities and rules in the procurement suite. Download your free Nexus Professional Evaluation or Learn more about Nexus Professional today. Continue reading this post for more information about these new procurement features.

How Artifacts are Signed

Most artifacts being added to the Maven Central Repository these days are signed during the release process using the maven-gpg-plugin. The GPG plugin is an implementation of the PGP public-key cryptography algorithm. Artifacts are signed by calculating a hash of the artifact that is then encrypted with that user’s private key. This digitally signed hash is added to the repository along side the original file as an .ASC file.

Developers that sign public artifacts normally publish their keys to a public key server such as pgp.mit.edu. (you can see my key and the list of people that have signed it here).

Validating the signed artifact is done by inspecting the .ASC file to determine the key id used to sign the artifact. The key is then retrieved from a configurable list of public keystores (if it’s not already available in a local keyring), and the decrypted hash is then compared to the recalculated hash of the artifact. If they match, then you know the artifact hasn’t been tampered with or corrupted since the artifact was signed by this key.

Verifying PGP Signatures with Nexus Professional

Nexus is able to perform these signature checks on the fly via the Procurement support. Users are able to define rules based on the group/artifact/version (with wildcards) that tell Nexus how to handle the validation. This makes it possible to approve only artifacts with valid signatures and block those that are invalid. How to handle missing signatures is also configurable.

Although signatures have been available for artifacts in Central for quite some time, most people do not take advantage of them because the process to validate artifacts is cumbersome and manual. This Nexus support now makes it possible to further guard your builds against corrupted or intentionally tampered artifacts in an automatic and transparent way.

Future releases of Nexus will build upon the signature checking to provide the ability to scan entire repositories and report on the signature status, as well as manage the web of trust so that you can block artifacts signed by people you don’t yet trust.

You may recall some release candidates early last fall from 2.0.10 — those eventually became 2.1.0M1 as several new features were introduced that had a potential to destabilize 2.0.x users. The features were pulled out and the bug fixes kept behind, producing the official 2.0.10 release. This RC process started last year with 2.0.9 should produce another solid release.

Our attention will now turn back to finalizing the 2.1.0 release. The M1 release turned out to be very stable, but unfortunately since it was called a milestone release, many users didn’t (or weren’t allowed) to use it. Because of this, we have pushed out the features originally planned for future 2.1.0 milestones into the 2.2 release so we can focus on making 2.1.0 final.

Hopefully this will mean that 2.0.10 is the last release of the 2.0.x line, but the possibility remains of a release to fix any serious regressions that weren’t uncovered with all the release candidates.

The 3.0 alphas are also coming along, with alpha-3 due out any time now. With active releases coming out from three branches (2.0.x, 2.1.x, 3.0.x), you can pick your flavor: boring but stable, fresh yet familiar, or cool yet mysterious.

See the release notes for all the information and links to download the new release.