Maven 2.2.0 released
I was surprised to find a major new release of Maven. It seems that Maven 2.1.0 suffered from a major bug due to which releases could not be done. A quick overview of this bug and other feature improvements are discussed in this blog.
In my product [1] there is a component [2] which uses maven for building. I simply hate it.
- It adds non-determinism to your build
- Sometimes you can build older software [3] cause the repo has been moved/deleted
I much prefer using Ant build.xml scripts and checking in our jars in another source code control repo. While building our product the jars are pulled in using svn:external or a similar mechanism ( for other SCM’s we use )
[1] = http://studios.thoughtworks.com/twist-agile-test-automation
[2] = http://seleniumhq.org/download/
[3] = Selenium 0.9.2 wont build it’s eclipse:eclipse target due to the required version of bouncycastle being removed for instance – http://release.openqa.org/selenium-remote-control/0.9.2/selenium-remote-control-0.9.2-dist.zip
Manish Chakravarty
16 Aug 09 at 1:41 pm
[quote]It adds non-determinism to your build[/quote]
This is a valid issue. The Maven community is working hard to solve this.
I love Maven because it has simplified a lot of my development. I use Maven exclusively for all my OpenSource work.
Subhash Chandran
26 Aug 09 at 11:32 am