Tuesday February 12, 2008
There has a lot of blog posting about the up- and downsides about Maven lately. As I was one of the early adopters, and probably made others to use it by writing articles in the Java Magazin about it, I am following the discussing with some interest.
On the one side, the idea behind Maven is certainly a good one. Everytime I created a build system based on good old Ant, I wished I would have been able to use Maven. On the other hand, Maven really sucks. Yes, it does. And people like Matt Raible and Don Brown who try to help improving Maven don’t make it much better. In fact, I strongly agree with Charles Miller of Atlassian, who says “Maven: Broken by Design” (btw: an excellent and entertaining read).
In this whole discussion, I personally think that the use cases for Maven should be re-thought. This would help focussing the discussion.
Posted on Feb 12, 2008 at 17:27 (MET) |
Permalink |
Thursday April 12, 2007
I’ve spend hours on Maven 1 and 2, while writing articles about it. I guess that’s what you have to do, when you evaluate a tool.
However, this is the result when lead developer/product architect Charles Miller of Atlassian spends too much time:
An Open Letter to Maven 2.
Posted on Apr 12, 2007 at 20:40 (MET) |
Permalink |
Saturday April 8, 2006
After reviewing Mevenide for the last issue of German Eclipse Magazine, I have had a look at the “Maven 2 Plugin for Eclipse“. There is only an development release available, but the Plugin already contains some great features and the UI design feels just right.
My favourite feature is the dependency browser, which also includes a repository browser. So if you need to add a dependency, you can search for it within Eclipse and let the plugin download it.
The next release will even provide the dependency download as a “quick fix” (when you hit Ctrl-1). Eugene (the plugin’s lead developer) provides more info about upcoming features.
Posted on Apr 8, 2006 at 13:35 (MET) |
Permalink |
Saturday December 31, 2005
I installed Mevenide for Eclipse (a plugin to add Maven support to different IDEs, e.g. Eclipse) a couple months ago and it worked right away. So, when Alexander Neumann of Software & Support Verlag asked me for an short article about Mevenide, I agreed to submit it for the 02/05 issue of the German Eclipse Magazine. When I started writing the article this week and trying to install it with my latest Eclipse installation, I had a nasty surprise: While the new project wizard and the POM configuration worked, the Maven launcher wouldn’t want to work even after hours of twiddling with different versions of Eclipse and Mevenide. In the end I got it working and I thought I share it not only with my readers of the Eclipse Magazine.
Prerequisites:
- Have Eclipse 3.1.1 downloaded & installed (no further information on that here… )
- Have Maven 1.0.2 downloaded & installed (no further information either
)
- Mevenide, download here
Installation:
- Unzip the downloaded ZIP to your Eclipse directory.
- Check the Plugin Configuration under Window > Preferences > Maven > Locations:
- Java Home points to a JDK
- Maven Home points to your Maven installation (not the one in the Eclipse directory)
- Maven Local Home points to your local home directory in your home directory.
- Maven Local Repository points to the repository in your maven local home directory.
- Tools.jar points to tools.jar in your JDK directory (under lib/).
That did the trick for me - I even can deploy Flowfuse from within Eclipse. Let me know if you have further tricks…
Besides the installation … errm … glitches, Mevenide provides good functionality. However, the Eclipse version of it seems sort of doomed: Most development efforts go into Netbeans version, which way more advanced and over at Megere - the Maven-Simulalabs-Opensource-Startup - they started developing and m2 plugin for eclipse. Once projects move to m2 the Eclipse version of Mevenide will probably disappear…
What do you think?
Posted on Dec 31, 2005 at 00:41 (MET) |
Permalink |
Sunday July 31, 2005
It looks like i’ll be writing an article about Maven to be published in the German Java-Magazin in October. It is based on experiences from my past projects and also contains practical tips. I will be probably posting some additional tips here - so stay tuned…
Posted on Jul 31, 2005 at 23:14 (MET) |
Permalink |
Thursday April 7, 2005
I just spent some time to get the Eclipse projects for ActiveMQ working. I encountered the following problems:
- Before running ‘maven eclipse’ it is required to build activemq first (run ‘maven’), as activemq-core-3.0-SNAPSHOT can not be found on any repository.
- The .classpath file for the core module contains a classpath entry for <ACTIVEMQ_HOME>/src/conf, while the correct path would be <ACTIVEMQ_HOME>/modules/core/src/conf.
- Eclipse’s compiler settings need to be change in order to enable the ‘assert’ keyword.
Apart from that I think ActiveMQ is fairly decent example for a complex Maven build.
Update: The wrong classpath entry has been fixed (AMQ-228)
Posted on Apr 7, 2005 at 15:33 (MET) |
Permalink |
Monday December 20, 2004
Very recently I’ve introduced Maven at work. Since then colleagues kept asking me how to pronounce ‘Maven’ - now i found it out. If you didn’t know either, here is the answer.
Update: The link to the actual WAV file is http//cougar.eb.com/sound/m/maven001.wav.
Posted on Dec 20, 2004 at 19:14 (MET) |
Permalink |