Sorry if I did not precise it exhaustively, but in fact taglist 2.3 is declared in <pluginManagement>, in <plugins>, in <dependencies>, in <dependencyManagement> and in <reporting> sections as well... (in the corporate pom). maven-site-plugin is declared only in <pluginManagement> section. I also deleted anything about this snapshot version of taglist (metadata and jar) from my archiva managed repositories, with no change.
What I don't understand is this log : "[DEBUG] taglist-maven-plugin: resolved to version 2.4-SNAPSHOT from repository central" ...because this version is NOT in central repository... I really miss some understanding on maven plugins way of working I'm afraid :( I understand it's retrieving youngest version, but it should not as I declared a specific version ? mkr wrote: > > You have to specify the version > of the > plugin in the "reporting"/"plugins" *also*, it is not enough to put the > version in the > "pluginManagement" or "build"/"plugins" section. > > The other thing is I believe for plugins Maven is going to retrieve the > youngest version > (regardless of SNAPSHOT or RELEASE). cheers > -- View this message in context: http://www.nabble.com/Why-is-maven-looking-for-snapshot-plugins---tp24840838p24864407.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
