Got Mevenide2 ? NetBeans Does. (cld.blog-city.com)
NetBeans 5 can support Maven 2 if you want it to do that.
The Mavenide team has released support for version 2.1.1 of their extension and it works with NetBeans 5.0.
Got Mevenide2 ? NetBeans Does. (cld.blog-city.com)
ANT files are great to get a project up and running with automated builds quickly. I have been using ANT for almost 5 years.
The only complaint I have about ANT is that over time, your ANT file - or files! - eventually start to grow like The Blob!
The problems creep in from a variety of sources. Here are some of the forces that conspire to make what used to be a simple ANT build file turn into a gigantic sweet of ANT targets:
As you can see, ANT is great when things start off simple. However, they do not stay that way.
Since there are lots of dependencies - and some incompatibilities between different ANT tasks and the 3rd party Java libraries they use - it quickly becomes a job in and of itself to maintain these ANT files and slay the versioning dragons.
That is where Maven comes in.
They have worked those problems out and found the compatible mix of libraries you need to use. They keep them up in repositories on public file servers. They make it easy to update from from old versions to new versions. They provide tons of functionality for Java build/test/document/measure requirements.
ANT did a great job of getting the ball rolling. Maven might just be the way to set it and forget about it.
The Mavenide team has released support for version 2.1.1 of their extension and it works with NetBeans 5.0.
Got Mevenide2 ? NetBeans Does. (cld.blog-city.com)
ANT files are great to get a project up and running with automated builds quickly. I have been using ANT for almost 5 years.
The only complaint I have about ANT is that over time, your ANT file - or files! - eventually start to grow like The Blob!
The problems creep in from a variety of sources. Here are some of the forces that conspire to make what used to be a simple ANT build file turn into a gigantic sweet of ANT targets:
- need for metrics to suit management goals
- need to automate execution of unit tests and generate test reports
- need for integration and/or system tests, maybe some functional tests that simulate user actions with the UI too
- need to do some fault-injection
- test coverage is required in order to make sure all those tests are doing something, and to find out what they are not testing
- in production, bottlenecks are showing up so have to get some profiling done
- want documentation generation to be automated
- have to start generating reports of issues and TODO items so long-overlooked issues do not get missed permanently and lead to problems
As you can see, ANT is great when things start off simple. However, they do not stay that way.
Since there are lots of dependencies - and some incompatibilities between different ANT tasks and the 3rd party Java libraries they use - it quickly becomes a job in and of itself to maintain these ANT files and slay the versioning dragons.
That is where Maven comes in.
They have worked those problems out and found the compatible mix of libraries you need to use. They keep them up in repositories on public file servers. They make it easy to update from from old versions to new versions. They provide tons of functionality for Java build/test/document/measure requirements.
ANT did a great job of getting the ball rolling. Maven might just be the way to set it and forget about it.
posted by John Collins | 4:54 PM
0 Comments:
Post a Comment
<< Home