Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] External Artifacts only deployed in local Nexus failed to resolved by m2e.

Your local nexus repository should be visible to the project, either as
<repository> element in project pom.xml as via settings.xml. If you can
provide a small standalone project that works on command line but does
not inside m2e, please open bugzilla and somebody we'll have a look.

--
Regards,
Igor

On 12-09-17 12:37 PM, Ivalo wrote:
Hi,

If 3th party artifact is only deployed into local nexus and Maven
project can can resolve it from command line and then try to Maven
update project causes failure of dependency resolution.

<arftifact>.lastUpdated file appears into local repo with content:

http\://repo.maven.apache.org/maven2/.lastUpdated=1347898930048
http\://repo.maven.apache.org/maven2/.error=

and Eclipse m2e complains missing artifact.

So how to fix this.


rgds,

Markku
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users


Back to the top