Hard to tell for sure without specific example I can use to reproduce the problem. What repository does nexus-m1-repos use, default maven2 or legacy maven1? m2e does not support legacy/maven1 layout.
-- Regards, Igor On 2014-07-09, 19:32, Keith Barlow wrote:
Igor, I downloaded maven 3.2.2 and am seeing a discrepancy. When I choose Maven -> Update Project... in eclipse, I got the following exception: eclipse.buildId=4.4.0.I20140606-1215 java.version=1.7.0_45 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product org.eclipse.m2e.logback.appender Warning Wed Jul 09 11:10:48 EDT 2014 Failure to transfer org.codehaus.mojo:cobertura-maven-plugin/maven-metadata.xml from http://${local.repo.address}/nexus/content/groups/m1-repos was cached in the local repository, resolution will not be reattempted until the update interval of nexus-m1-repos has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo:cobertura-maven-plugin/maven-metadata.xml from/to nexus-m1-repos (http://${local.repo.address}/nexus/content/groups/m1-repos): No connector available to access repository nexus-m1-repos (http://${local.repo.address}/nexus/content/groups/m1-repos) of type legacy using the available factories AsyncRepositoryConnectorFactory, WagonRepositoryConnectorFactory However, when I run in maven 3.2.2, I get a bunch of warnings about my repository configuration but the build (mvn clean install) still completes successfully and installs the missing plugin into the repository at the m1-repos location: kbarlow@laplace:~/workspace/connector-marketo$ ~/Applications/apache-maven-3.2.2/bin/mvn clean install [WARNING] [WARNING] Some problems were encountered while building the effective settings [WARNING] 'usePluginRegistry' is deprecated and has no effect. @ /home/kbarlow/.m2/settings.xml [WARNING] 'profiles.profile[boomi-default].pluginRepositories.pluginRepository.layout' for m1-plugin-repos uses the unsupported value 'legacy', artifact resolution might fail. @ /home/kbarlow/.m2/settings.xml [WARNING] [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for com.boomi.redsky.connectors:connector-marketo:jar:4.0.14-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:cobertura-maven-plugin is missing. @ com.boomi:boomi:4.0.8, /home/kbarlow/.m2/repository/com/boomi/boomi/4.0.8/boomi-4.0.8.pom, line 104, column 21 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ com.boomi:boomi:4.0.8, /home/kbarlow/.m2/repository/com/boomi/boomi/4.0.8/boomi-4.0.8.pom, line 93, column 21 [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:buildnumber-maven-plugin is missing. @ line 79, column 21 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-surefire-plugin is missing. @ com.boomi:boomi:4.0.8, /home/kbarlow/.m2/repository/com/boomi/boomi/4.0.8/boomi-4.0.8.pom, line 133, column 21 [WARNING] 'pluginRepositories.pluginRepository.layout' for m1-plugin-repos uses the unsupported value 'legacy', artifact resolution might fail. [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Boomi Marketo Connector 4.0.14-SNAPSHOT [INFO] ------------------------------------------------------------------------ Downloading: https://repository.jboss.org/nexus/content/repositories/releases/org/codehaus/mojo/cobertura-maven-plugin/maven-metadata.xml Downloading: http://builds.lab.boomi.com:8080/nexus/content/groups/m1-repos/org/codehaus/mojo/cobertura-maven-plugin/maven-metadata.xml [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ connector-marketo --- [INFO] [INFO] --- cobertura-maven-plugin:2.5.2:clean (clean) @ connector-marketo --- After I run the commandline version, the repository seems to contain the required file and eclipse Maven -> Update Project... runs w/o error. I know that my project is designed for maven 2 so the warnings are expected (were starting to evaluate a migration to maven 3) but should the discrepancy in behavior be reported? Thanks. Keith On Wed, Jul 9, 2014 at 2:13 AM, Igor Fedorenko <[email protected] <mailto:[email protected]>> wrote: Maven 3.0 is more strict about resolving artifacts from local repository [1]. See if you can reproduce the problem with Maven 3.0.5 (which was included in m2e 1.4/Kepler) and 3.2.1 (embedded in m2e 1.5/Luna). If the project builds with Maven 3.2.1 on command line but does not build inside m2e, please open new bugreport and provide small standalone example we can use to reproduce the problem. [1] https://cwiki.apache.org/__confluence/display/MAVEN/__Maven+3.x+Compatibility+Notes#__Maven3.xCompatibilityNotes-__ResolutionfromLocalRepository <https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository> -- Regards, Igor On 2014-07-09, 2:49, Keith Barlow wrote: Sorry... I forgot to mention that the plugin is actually installed under http://${local.repo.address}/__nexus/content/groups/public. I don't have that configured as a plugin repo but I am not sure why that is not a problem for commandline versions of maven (Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)). Thanks. Keith On Tue, Jul 8, 2014 at 6:43 PM, Keith Barlow <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> wrote: Hiyas, I just upgraded eclipse from Kepler to Luna (and consequently from m2e 1.4 to m2e 1.5). After the upgrade, I am getting the following message when I use "Maven->Update Project..."): eclipse.buildId=4.4.0.__I20140606-1215 java.version=1.7.0_45 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.__product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.__product org.eclipse.m2e.logback.__appender Warning Tue Jul 08 18:11:36 EDT 2014 Failure to transfer org.codehaus.mojo:buildnumber-__maven-plugin/maven-metadata.__xml from http://${local.repo.address}/__nexus/content/groups/m1-repos <http://builds.lab.boomi.com:__8080/nexus/content/groups/m1-__repos <http://builds.lab.boomi.com:8080/nexus/content/groups/m1-repos>> was cached in the local repository, resolution will not be reattempted until the update interval of nexus-m1-repos has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo:buildnumber-__maven-plugin/maven-metadata.__xml from/to nexus-m1-repos (http:// <http://builds.lab.boomi.com:__8080/nexus/content/groups/m1-__repos <http://builds.lab.boomi.com:8080/nexus/content/groups/m1-repos>>${local.repo.address} <http://builds.lab.boomi.com:__8080/nexus/content/groups/m1-__repos <http://builds.lab.boomi.com:8080/nexus/content/groups/m1-repos>>/nexus/content/groups/__m1-repos): No connector available to access repository nexus-m1-repos (http:// <http://builds.lab.boomi.com:__8080/nexus/content/groups/m1-__repos <http://builds.lab.boomi.com:8080/nexus/content/groups/m1-repos>>${local.repo.address} <http://builds.lab.boomi.com:__8080/nexus/content/groups/m1-__repos <http://builds.lab.boomi.com:8080/nexus/content/groups/m1-repos>>/nexus/content/groups/__m1-repos) of type legacy using the available factories AsyncRepositoryConnectorFactor__y, WagonRepositoryConnectorFactor__y I don't seem to get this message when I use the command line version of maven and I have eclipse configured to use that version. If I'm not mistaken, m2e still uses the embedded engine when updating classpaths and things other than running the actual maven executable, right? Is there something new in m2e 1.5 that would cause this? Maybe this is related but I use maven 2.x when building projects. Thanks. Keith -- Keith Barlow /Software Engineer/ *Dell Boomi* -- Keith Barlow /Software Engineer/ *Dell Boomi* _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> -- Keith Barlow /Software Engineer/ *Dell Boomi* _______________________________________________ m2e-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
