|
further info: Switching in Eclipse to
use the command line installation of Maven on my system, rather
than the Embedded version default also makes the problem go away.
So the question appears to be:
What is wrong with the embedded Maven included in Luna. The
working Kepler version also uses its own embedded Maven, which
does not have the problem.
On 01/16/2016 12:08 PM, Steve Cohen wrote:
Okay, that way (command line or Run
As Maven - install) these errors do not occur. But errors shown
in Eclipse Luna persist.
On 01/16/2016 11:18 AM, Manfred Moser wrote:
Just try for a full build. That essentially tests the
download of dependencies.
So in the project directory run e.g.
mvn clean install -U
And as a next step you can try the same in the IDE with Run
As - Maven - install
Steve Cohen wrote on 2016-01-16 08:11:
Please define "it". I have no
idea of what the command line equivalent is of whatever
Eclipse is doing during its automatic build.
On 01/15/2016 05:40 PM, Manfred Moser wrote:
Does it work on the command line with -U ?
Steve Cohen wrote on 2016-01-15 15:34:
The same behavior is
experienced with NEW Maven projects created with Luna.
They immediately show these errors. If Luna is closed
and Kepler opened on the same workspace, and
Maven->Update run, the errors disappear.
On 01/15/2016 05:20 PM, Steve Cohen wrote:
I'd been working with Eclipse Kepler. I had
several Maven projects there. I connected to Maven
Central through a corporate Nexus repository.
Everything worked just fine.
Then I got Eclipse Luna and installed it. Using the
SAME workspace, with the same maven settings.xml that
had the settings for the Nexus repository, I find that
all Maven projects show errors that cannot be resolved
by running Maven->Update. All mention something
about connections being refused by Maven Central.
I closed Eclipse Luna and restarted Kepler on the same
workspace. (I was never running them simultaneously).
The same errors appeared, but now Maven->Update was
successful in resolving them.
I closed Kepler and restarted Luna on the same
workspace. Once again, the errors returned, and were
not resolvable by Maven->Update.
Here is one of the errors:
CoreException:
Could not get the value for parameter compilerId for
plugin execution default-compile:
PluginResolutionException: Plugin
org.apache.maven.plugins:maven-compiler-plugin:3.1 or
one of its dependencies could not be resolved: The
following artifacts could not be resolved:
org.apache.maven:maven-plugin-api:jar:2.0.9,
org.apache.maven:maven-artifact:jar:2.0.9: Failure to
transfer org.apache.maven:maven-plugin-api:jar:2.0.9
from http://mavencentral.it.whatever.com:8084/nexus/content/groups/whatever-public-group
was
cached in the local repository, resolution will not be
reattempted until the update interval of nexus has
elapsed or updates are forced. Original error: Could
not transfer artifact
org.apache.maven:maven-plugin-api:jar:2.0.9 from/to
nexus (http://mavencentral.it.whatever.com:8084/nexus/content/groups/whatever-public-group):
Connection refused: connect
What might the problem be?
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
|
