Blogging Roller

Maven 3.0: 50% to 400% speed improvement?

2010-05-26T08:25:10+00:00

A drop-in replacement with 50% to 400% speed improvement? That sounds too good to be true.

Matt Raible: The main improvement in Maven 3 is speed. It's been performance tuned to be 50% to 400% faster. Benchmarks (guaranteed by integration tests) include better: Disk I/O, Network I/O, CPU and Memory. Another new feature is extensibility so Maven is a better library rather than just a command-line tool. Now there's a library and APIs that you can use to do the things that Maven does. Plexus has been replaced with Guice and it's now much easier to embed Maven (Polyglot Maven and Maven Shell are examples of this).

Apparently it is not entirely true, at least not yet (Maven 3.0 is still in beta). I tried switching to Maven 3 for the Roller 5 build and hit several build errors related to class-loading and JPA byte-code enhancement.

Maven support in IDEs

2010-03-23T10:11:14+00:00

I've been switching around between the Eclipse, Netbeans and IntelliJ IDEs at home and at work. I've found that fiddling around with multiple IDE specific project configurations and launchers and class-paths is no fun at all. That's one of the reasons I got interested in Maven. Yes, Maven is a build-system but it's also a sort of IDE portability solution. Maven projects can be loaded right into all the major Java IDEs as you can see in the screenshots below. IDEs can find your sources, resources, dependencies and via the Maven Jetty plugin even run your Java webapps from the IDE -- things that are not possible if you're using a custom Ant build-script as we were doing before with Roller.

Here some screenshots that show the various Maven IDE plugins and their dependency graph feature.

Roller / Maven Eclipse 3.5 / M2Eclipse

Here's Roller loaded into Eclipse via the Maven M2 Eclipse plugin.

By the way, if you want detailed instructions for getting Roller 5 up and running in Eclipse with the Eclipse Web tooling, check-out Harald Wellman's helpful blog on the topic: Setting up Eclipse for Roller.

Roller / Maven in Netbeans 6.8

Here's Roller loaded into Netbeans as a Maven project.

Roller / Maven in IDEA IntelliJ 9.0

And here's Roller loaded into IDEA IntelliJ as a Maven project.

I'm not sure which I prefer yet.

Built with Maven

2010-03-14T09:47:26+00:00

I was a Maven hater and resisted it for a long time but over the years Maven has gotten much better, it's well supported in IDEs and as far as I can tell, Maven has replaced Ant as the de facto build system for Java projects. If you want new developers be able to easily build, debug and run your code via command or their favorite IDE then Maven is the way to go, and that's especially true for open source projects like Roller.

That's why I spent a couple of weekends learning Maven and converting Roller's build process from Ant to Maven (ROL-1849). The process of conversion wasn't too difficult. Getting dependencies under control was a pain, but it believe it will be a one time pain and a worthwhile one. What took the most time was figuring out how to get Maven to start Derby, create the Roller tables and then run Roller's JUnit tests. Also, getting Maven's Jetty plugin setup to run Roller was a little tricky but hopefully also a one-time pain. The result is that Roller now uses a standard and well known directory structure, dependencies are managed and it's easier for developers to get started with the codebase.

If you have Maven and Subversion installed on your computer then these commands will fetch the Roller source code, compile the code, run all JUnit tests and then build the Roller webapp:


   svn co https://svn.apache.org/repos/asf/roller/trunk roller_trunk
   cd roller_trunk 
   mvn install

And once all that is done, the following commands will start the Jetty app server, start the Derby database and start Roller at http://localhost:8080/roller, ready for testing, experimentation, etc.


   cd weblogger-web
   mvn jetty:run-war

I think that's pretty damn useful.

Here are some articles/links that influenced my thinking on Maven recently:

Comparing Build Systems - Adrian Sutton concludes that Maven is too much work but "the consistency in how a project is built that the Maven project has brought to the Java would is absolutely revolutionary"
Maven in our development process - Sherali Karimov explains how Atlassian and says the need for Maven training is "the most important and most overlooked issue of all."
Sonatype - The Maven Company. Founded in 2008 by Jason van Zyl, the creator of Maven. Offers training, support and the Nexus Professional repo manager.

Latest Links: open source, social networking and etc.

2008-03-23T14:00:05+00:00

cgwalters - A software tsunami
"OpenJDK is finally changing that. Now, you can write a library using Java, it can be sensibly integrated with Free operating systems"
Countdown for IBM Project Zero | Reg Developer
"bringing the feedback typical of an open source project without any of the obligations to give the resulting technology back to the community."
Soviet-era JCP needs change, concedes top commissar | Reg Developer
Patrick Curran has reached a firm conclusion on his organization: "We have to change," he said. "No more smoke-filled rooms."
Glynn Foster: Why Our Governance Doesnâ€™t Work
"Thereâ€™s no substitute to JFDI - or improving our governance model so that it doesnâ€™t get in the way of suitably motivated people who want to contribute."

Skype Journal: Skype and the Social Network Stack
"We need a new stack to sort out social media's plumbing"
An Open Letter to American Express ~ Chris Pirillo
"You know, for all the buzz that FaceBook getsâ€¦ I get far more value out of Twitter."
buddypress - Google Code
"suite of plugins that will completely transform a vanilla installation of Wordpress MU into a fully functional social network platform"

App Platform Strategies Blog: Looking for SOA success stories
"SOA is not working in most organizations"
OLPC News: Negroponte Says XP on XO in 60 Days
"the end of a dream".
Atlassian Dev Blog - Maven in our development process. Part 4.
"Maven users need training."