Re: [m2e-users] Unable to lookup plugin in Luna??

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

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

--
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 <kbarlow@xxxxxxxxx
> <mailto:kbarlow@xxxxxxxxx>> 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> 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>${local.repo.address}
>     <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>${local.repo.address}
>     <http://builds.lab.boomi.com:8080/nexus/content/groups/m1-repos>/nexus/content/groups/m1-repos)
>     of type legacy using the available factories
>     AsyncRepositoryConnectorFactory, WagonRepositoryConnectorFactory
>
>
>     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
> m2e-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users