richfaces - maven-compiler-plugin won't upgrade from 2.0.2.SP1 to 2.3.2 -

i'm maven newbie, have been studying maven week now, have 5 years experience using ant, i'm able come speed without trouble. have read through documentation @ maven.apache.org twice -- several hundred pages of reading. have created several test apps using several different maven archetypes better understanding i've read through documentation. now, i'm setting new project , finer points coming play...

i think know why maven-compiler-plugin won't upgrade latest release, 2.3.2, when run

mvn versions:use-latest-release 

but need know if there workaround, or if should concerned. first, here's snip of pom.xml:

        <plugin>             <artifactid>maven-compiler-plugin</artifactid>             <version>2.3.2</version>             <configuration>                 <source>1.5</source>                 <target>1.5</target>             </configuration>         </plugin> 

as can see specifying version 2.3.2. thinking there might problem maven not knowing needed update files in repository, ran mvn versions:use-latest-releases noticed jar file downloaded ~/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/ i.e.

ll ~/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.3.2 total 60 -rw-rw-r--. 1 pgarner pgarner 29176 oct  7 21:29 maven-compiler-plugin-2.3.2.jar -rw-rw-r--. 1 pgarner pgarner   335 oct  7 21:29 maven-compiler-plugin-2.3.2.jar.lastupdated -rw-rw-r--. 1 pgarner pgarner    40 oct  7 21:29 maven-compiler-plugin-2.3.2.jar.sha1 -rw-rw-r--. 1 pgarner pgarner  7329 oct  7 21:29 maven-compiler-plugin-2.3.2.pom -rw-rw-r--. 1 pgarner pgarner   335 oct  7 21:29 maven-compiler-plugin-2.3.2.pom.lastupdated -rw-rw-r--. 1 pgarner pgarner    40 oct  7 21:29 maven-compiler-plugin-2.3.2.pom.sha1 -rw-rw-r--. 1 pgarner pgarner   208 oct  7 21:29 _maven.repositories 

but when ran following evident maven-compiler-plugin version remained 2.0.2.sp1:

mvn help:describe -dplugin=org.apache.maven.plugins:maven-compiler-plugin /usr/java/jdk1.7.0 [info] scanning projects... [info]                                                                          [info] ------------------------------------------------------------------------ [info] building richfaces 4 application 1.0-snapshot [info] ------------------------------------------------------------------------ [info]  [info] --- maven-help-plugin:2.1.1:describe (default-cli) @ patrac --- [info] org.apache.maven.plugins:maven-compiler-plugin:2.0.2.sp1 name: maven compiler plugin description: maven plugins group id: org.apache.maven.plugins artifact id: maven-compiler-plugin version: 2.0.2.sp1 goal prefix: compiler 

noting did use richfaces-archetype-simpleapp archetype generate project, , required add jboss repository project, next thought there might have been in richfaces prevented project using latest compiler, took at

~/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/maven-metadata-jboss-public-repository-group.xml

and sure enough there, think, found problem:

<latest>2.4-snapshot</latest> <release>2.0.2.sp1</release> <versions>   <version>0.1-stub-snapshot</version>   <version>2.0.2.sp1</version>   <version>2.3.2-snapshot</version>   <version>2.4-snapshot</version> </versions> 

so, mean richfaces cannot used maven-compiler-plugin version 2.3.2?

i started on new project using latest version of maven-compiler-plugin. stay away using snapshots , stick releases. instinct tells me dangerous add entry version 2.3.2 above xml file i.e. 2.3.2. correct? or matter of jboss-maven repository not having complete set of versions of maven-compiler-plugin?

what options? should satisfied using v. 2.0.2.sp1? or there way ask maven ignore maven-metadata-jboss-public-repository-group.xml, or perhaps ask maven give precedence maven central repository on jboss repository?

you've got quite bit here, i'll try , take apart , answer as can...

i think know why maven-compiler-plugin won't upgrade latest release, 2.3.2, when run

based on snippet below that, looks worked fine. checked compile plugin page , 2.3.2 in fact latest version.

when run this: mvn help:describe -dplugin=org.apache.maven.plugins:maven-compiler-plugin /usr/java/jdk1.7.0 i'm guessing default. if run mvn compile in said project, should use 2.3.2 you've specified.

my instinct tells me dangerous add entry version 2.3.2 above xml file i.e. 2.3.2. correct?

leave metadata files alone unless looking trouble or know doing :)

what options? should satisfied using v. 2.0.2.sp1? or there way ask maven ignore maven-metadata-jboss-public-repository-group.xml, or perhaps ask maven give precedence maven central repository on jboss repository?

i don't think 2.0.2.sp1 of plugin being used. if was\is, using snapshots of plugins isn't big of deal imo. using snapshots of dependencies needs caution.

i'm sure there ways override repository resolves what, , in order, don't know how in instance.

i hope helps.