i would like to knpw "Most Common Issues in Maven"?

Any body can focus on this?

You may get error with Java Heap Size error.
Solution: set the Environment Variable of MAVEN_OPTS to "-Xms512m -Xmx512m -XX:MaxPermSize=1024m"

2)ArtifactResolutionException

This error generally occurs when Maven could not download dependencies. Possible causes for this error are:

1. The repository you have configured requires authentication and Maven failed to provide the correct credentials to the server. In this case, make sure your ${user.home}/.m2/settings.xml contains a <server> declaration whose <id> matches the <id> of the plugin repository to use. See the Maven Settings Reference for more details.
2. The remote repository in question uses SSL and the JVM running Maven does not trust the certificate of the server.
5. Maven failed to save the files to your local repository.
4. You have configured Maven to perform strict checksum validation and the files to download got corrupted.
3. There is a general network problem that prevents Maven from accessing any remote repository, e.g. a missing proxy configuration.(Communication Issue local box and repo)

3)DuplicateProjectException
This error signals a collision of project identifiers during a reactor build. The coordinates for a project as given by its group id, artifact id and version must be unique within a reactor build. The usual cause for this error is a in one of the POMs so please verify the project coordinates are correctly set and valid.

InternalErrorException


This error indicates a bug in Maven itself.

1. Capture the debug output of the failing build, e.g. by adding the flag -X to the command line and redirecting the console output of Maven to a file:

mvn <your goals> -X > debug.log

2.If interested report this bug to maven gurus you could submit a ticket in jira.codehaus.org/browse/MNG so we can avoid this bug in future provided bug has been fixed.It is said it is intermittent.

4) InvalidPluginDescriptorException

5) InvalidRepositoryException

This error is occurred if a repository declaration in the POM or the settings,xml specifies a bad repository identifier or URL. Simply double check tha POM and settings.xml and make sure each repository has both an <id> and <url> sho

uld resolve this issue.

6)LifecycleNotFoundException

This error is generated by a plugin goal that tries to fork non-existing life cycle.

7)LifecyclePhaseNotFoundException

This error is generated if you try to invoke a build command that Maven does not understand.

8)LocalRepositoryNotAccessibleException

This error is raised when Maven could not access your local repository. This could have the following reasons:

1.No local repository is present the drive.
2. The file permissions prevent Maven from accessing the repository.

So please verify that your settings.xml specifies a valid directory and Ensure that your user account has both read and write access to this directory and all its sub directories and files.