My first suggestion would be to version all the plugins you use, maybe in a parent pom. Otherwise, builds that work now, will fail in the future, even your tags, because of updated plugins. Been there, done that, got the T-shirt.
Hth, Nick Stolwijk -----Original Message----- From: Joshua Pollak [mailto:[EMAIL PROTECTED] Sent: Thu 2/7/2008 5:06 PM To: users@maven.apache.org Subject: Error getting POM for 'org.apache.maven.plugins:maven-resources-plugin' from the repository Hello, Over the last few days this problem has been plaguing my development team. At first I thought it was a problem with a specific projects use of snapshot plugins and our internal repository cache (Artifactory), but I just discovered it is happening on an internal project which is not configured to use Artifactory. -------------------------------------- Project ID: org.apache.maven.plugins:maven-resources-plugin Reason: Error getting POM for 'org.apache.maven.plugins:maven- resources-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata. org.apache.maven.plugins:maven-resources-plugin:pom:2.3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.apache.maven.plugins:maven-resources-plugin -------------------------------------- I've only found two ways to make this problem go away: 1) Everyday, clear both the users ~/.m2/repository directory, and the Artifactory cache of plugin snapshots 2) Explicitly set the maven-resources-plugin version to 2.2. I don't particularly like either option, but we are going with #2 for now. Does anyone have any suggestions? Thanks, Josh -- Joshua ChaitinPollak | Software Engineer Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970
