- While Maven 2.0 is quite useful as is, it does not yet have all of the features of it's predecessor, and has - some limitations that may impede it's use on a day-to-day basis in your projects. + Maven 2.0 is now in beta testing. We believe it is equally functional to Maven 1.0, however there are still + some bugs and usabilities issues including documentation to be resolved.
- This release is being made available so that people who are interested in the future of Maven can take a - sneak peek, while those interested in becoming early adopters can get involved in the development and + While some minor features may be added, the key goal is to retain backwards compatibility so this will be + limited. +
++ This release is being made available so that people who are interested in using Maven 2 when it is released + can test and provide feedback, and those interested can get involved in the development and direction of the project.
@@ -106,11 +110,11 @@
- We are working to a 4-5 week release cycle, meaning that there will be at least one release per month.
+ We are working to a fortnightly release cycle until the final release.
- The first releases such as the technology preview will be designated "alpha" releases, indicating that
- they are not yet feature complete and there are outstanding bugs. Following that, "beta" releases will be
+ The first releases such as the technology preview were designated "alpha" releases, indicating that
+ they were not yet feature complete and there were outstanding bugs. Following that, "beta" releases are being
made available where introduction of new features will be restricted and the focus on improving usability and
stability. Finally, one or more release candidates will be distributed for testing that are genuinely believed
to be final, with the expectation that a final release would be available shortly afterwards.
@@ -209,10 +213,6 @@
Channel
box).
- Please remember that it is a preview release, so please be patient with features that are not yet implemented,
- and be prepared to do some research and to help out yourself wherever possible.
-
prereqs,
- preGoals and
- postGoals.
+ Defined build lifecycle
+ - No more
+ prereqs
+ ,
+ preGoals
+ and
+ postGoals
+ .
The build is a series of well defined phases. This also means that the normal goal names are not used -
- compile,
- test and
- install work for any project type.
+ compile
+ ,
+ test
+ and
+ install
+ work for any project type.
SNAPSHOT handling
- - Snapshots are now checked for updates only once per day by
+ SNAPSHOT
+ handling
+
+ - Snapshots are now checked for updates only once per day by
default - though can be configured to be once per build, on a particular interval, or never. A command line
option can force a check - making it more like updating from an SCM.
pom.xml).
+ No more properties files
+ - All plugins are now configured from the POM (which is now called
+ pom.xml
+ ).
maven.xml
- - Plugins are now easier to build and integrate, and are the only way
- to script your builds. (Note that additions may later be made to the POM to allow simple things that scripting
+
+ - Plugins are now easier to build and integrate, and are the only way
+ to script your builds. (Note that additions may later be made to the POM to allow simple things that
+ scripting
was used for, such as goal aliasing).
- The simple answer is that we hope you'll try Maven 2.0, and use it if it works for you. However, it is a preview - release, so you can expect some features to be missing at this point and there may be unexpected bugs. - We'd hate for your first experience with Maven 2.0 to be a bad one - so if you are embarking on a big, complicated + The simple answer is that we hope you'll try Maven 2.0, and use it if it works for you. However, it is a beta + release, so you can expect some unexpected bugs. + We'd hate for your first experience with Maven 2.0 to be a bad one - so if you are embarking on a big, + complicated or mission critical project - we still recommend Maven 1.0.2 as the latest stable release.
- If you are already using Maven 1.0 - feel free to try out Maven 2.0, but it may be better to remain on an existing + If you are already using Maven 1.0 - feel free to try out Maven 2.0, but it may be better to remain on an + existing version that is working for you until you need the new features and it covers all of your needs.
If you do use Maven 1.0, and would like to upgrade in the future, you should carefully consider following some of the - Best Practices listed. These will make + Best Practices + listed. These will make your project a lot easier to migrate in the future.
@@ -85,14 +106,16 @@
maven.xml file?maven.xml
+ file?
+ Taken from this post to the Maven User's List: +
Taken from + + this post to the Maven User's List + :
-Everything in m2 is a plugin so for doing any sort of custom work like -that you will need to make a plugin. This 1) greatly reduces the -complexity within m2 because we only deal with proper plugins. The -maven.xml file in m1 was a psuedo plugin essentially and greatly -complicated the internals and 2) it promotes the sharing of your work -right from the get go. To start with you'll probably write a plugin that -is only applicable to your specific requirements, or your team's work, -but you'll see people asking for some functionality and you'll go "hey, -I have something like that!" and hopefully people who have concrete -solutions will generalize their solutions so they can be shared with -others. That's what we're trying to encourage. + Everything in m2 is a plugin so for doing any sort of custom work like + that you will need to make a plugin. This 1) greatly reduces the + complexity within m2 because we only deal with proper plugins. The + maven.xml file in m1 was a psuedo plugin essentially and greatly + complicated the internals and 2) it promotes the sharing of your work + right from the get go. To start with you'll probably write a plugin that + is only applicable to your specific requirements, or your team's work, + but you'll see people asking for some functionality and you'll go "hey, + I have something like that!" and hopefully people who have concrete + solutions will generalize their solutions so they can be shared with + others. That's what we're trying to encourage.
-We estimate that there's a lot of work bound up in project's maven.xml -that is not being shared and we'd like to try and change that. We plan -to make it dead simple to share plugins and hopefully people can use -other project's plugins as a start for a plugin that they may need -themselves. + We estimate that there's a lot of work bound up in project's maven.xml + that is not being shared and we'd like to try and change that. We plan + to make it dead simple to share plugins and hopefully people can use + other project's plugins as a start for a plugin that they may need + themselves.
- NOTE: Compare this tutorial to + NOTE: Compare this tutorial to Developing - Plugins from the Maven 1.0 website. Marmalade is meant to be quite similar to Jelly in its - syntax, so this process should be very familiar to Maven 1.0 plugin developers. + Plugins + from the Maven 1.0 website. Marmalade is meant to be quite similar to Jelly in its + syntax, so this process should be very familiar to Maven 1.0 plugin developers.