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.
.lastUpdated file appears into local repo with content:
http\://repo.maven.apache.org/maven2/.lastU
Your local nexus repository should be visible to the project, either as
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-0
Thanks for quick response.
Reason was that settings.xml.
Caused by the fact that Eclipse m2e plugin somehow lost dedicated Maven
user settings file; now reconfigured .
Definitely user error, because I'm new with Xubuntu (or Linux at all).
Markku
On 09/17/2012 08:00 PM, Igor Fedorenko wrote:
If I create a non-maven ear project, and add an external library to
the ear specifying the deploy directory as /lib, I get an entry in
org.eclipse.wst.common.component that looks like this:
uses
If I have a maven project and I add a dependency to the ear, I get:
m2e-wtp only supports . See
http://stackoverflow.com/questions/4145021/has-maven-changed-ear-element-from-defaultjavabundledir-to-defaultlibbundledi
Regards
Fred Bricon
On Mon, Sep 17, 2012 at 8:48 PM, Paul Vonnahme wrote:
> If I create a non-maven ear project, and add an external library to
>
Thanks for the quick response Fred! I'm glad it turned out to be
something so simple. I found the reference to the old element name on
a maven-war-plugin page
(http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html),
so I've opened a minor issue to get the example updated:
htt
