Yes the compile (of course with the exact same POM) works from the command line. That is why I was wondering if the problem was either the new Mars 2 version of Eclipse or possibly the m2e plugin. As per the question in your reply and my answer here, I will post something to the m2e mailing list, as you suggest.
Michael Tarullo Contractor (Engility Corp) Software Engineer FAA WJH Technical Center (609)485-5294 -----Original Message----- From: Barrie Treloar [mailto:[email protected]] Sent: Tuesday, June 07, 2016 5:13 PM To: Maven Users List Subject: Re: Maven and Eclipse On 8 June 2016 at 01:33, <[email protected]> wrote: > I have recently been doing Maven builds from Eclipse Luna with no problems. > > Recently I upgraded Eclipse to Mars 2 and Maven builds that worked in > the past no longer work. I have posted the error I'm getting at the > end of this email. In addition, it appears that the Maven -> Update > project.... > Feature is no longer working. When I do this from Eclipse Mars 2 on > an empty local repo, the local repo is populated from my remote repo > fine, but the Java Build Path Libraries are not populated, when I > start with both an empty local repo and no libraries other than the JDK. > > I am using the m2e-workspace v0.3.1. Does this need to be changed as > a result of my upgrade from Luna to Mars 2? > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile > (default-compile) on project queue.producer: > Execution default-compile of goal > org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile failed: > Plugin org.apache.maven.plugins:maven-compiler-plugin:2.5.1 or > one of its dependencies could not be resolved: > Failure to find org.apache.maven:maven-plugin-api:jar:2.0.9 in > https://swimrepo.faa.gov/nexus/content/repositories/Repo-jboss-fuse-06-02-01-Releases > was cached in the local repository, resolution will not be > reattempted until the update interval of SwimRepo > has elapsed or updates are forced -> [Help 1] Does this work on the command line ? If yes, then you need to email the m2e mailing list to troubleshoot further. https://dev.eclipse.org/mailman/listinfo/m2e-users This error doesn't look like a problem with maven or m2e. This looks like org.apache.maven:maven-plugin-api:jar:2.0.9 is not in your organisations nexus proxy. From the path in the url to the nexus repo it looks like a jboss fuse cache. My last recollection of the jboss caches were they were bastardized copies of central to work with jboss. I'd recommend making that cache the last thing the nexus proxy attempts to check. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
