groupId It identifies your project as a whole (it will make more sense when you start using multi-modules build) and should be unique. Maven enforces a naming schema following the Java package name rules. Hence, the groupId has to start by at least a domain name you control followed by any subgroups you want. For further informations, look at The package names in the Java language. [characters restrictions]
An example: org.apache.maven
artifactId It identifies precisely the current project inside the group identified by the groupId. [characters restrictions]
An example: groupdId: org.apache.maven.doxia, artifactId: doxia
and a version:
version: The version number allows you to distinguish your different project releases. There are two kinds of versions depending of the release type it is associated with:
Official releases : 1.0, 2.2, ...
Specific releases (nightly build or snapshots) : 1.0-SNAPSHOT, 2.1.2-SNAPSHOT [characters restrictions]

Having precise naming formats allows Maven to manage efficiently for you the dependencies and the plugins your project depends upon. We'll see what that means in the next lessons.
REF::http://docs.codehaus.org/display/MAVENUSER/Maven%2C+not+just+another+build+tool
No comments:
Post a Comment