Community
Participate
Working Groups
I have a project with dependencies provided by scp repo. When I run mvn comile from comand line everything works fine, but when i update the dependencies from eclipse (by using m2e) I get this error: 9/27/13, 9:43:22 AM GMT-03:00: [WARN] Could not transfer metadata uy.xxx.xxx:xxx-xxx:2.0.13-SNAPSHOT/maven-metadata.xml from/to xxx.net (scp://xxx:22/usr/site/opt/maven2-repo): Cannot connect. Reason: timeout: socket is not established Could not transfer metadata uy.xxx.xxx:xxx-xxx:2.0.13-SNAPSHOT/maven-metadata.xml from/to xxx.net (scp://xxx:22/usr/site/opt/maven2-repo): Cannot connect. Reason: timeout: socket is not established 9/27/13, 9:43:22 AM GMT-03:00: [WARN] Failure to uy.xxx.xxx:xxx-xxx:2.0.13-SNAPSHOT/maven-metadata.xml from scp://xxx:22/usr/site/opt/maven2-repo was cached in the local repository, resolution will not be reattempted until the update interval of xxx.net has elapsed or updates are forced. Original error: Could not transfer metadata uy.xxx.xxx:xxx-xxx:2.0.13-SNAPSHOT/maven-metadata.xml from/to xxxx.net (scp://xxx:22/usr/site/opt/maven2-repo): Cannot connect. Reason: timeout: socket is not established Failure to transfer uy.xxx.xxx:xxx-xxx:2.0.13-SNAPSHOT/maven-metadata.xml from scp://xxx:22/usr/site/opt/maven2-repo was cached in the local repository, resolution will not be reattempted until the update interval of xxx.net has elapsed or updates are forced. Original error: Could not transfer metadata uy.xxx.xxx:xxx-xxx:2.0.13-SNAPSHOT/maven-metadata.xml from/to xxx.net (scp://xxx:22/usr/site/opt/maven2-repo): Cannot connect. Reason: timeout: socket is not established I have this in my project pom: <extensions> <extension> <groupId>org.apache.maven.wagon</groupId> <artifactId>wagon-ssh</artifactId> <version>2.4</version> </extension> </extensions> I guess that is a embedded maven problem wich always is used to resolve dependencies, because when I run (project-> run as -> maven install) it works fine.
I use eclipse kepler with embedded maven 3.0.4. And my external maven version is 3.1.0. I also tested external maven 3.0.4 from comand line and everithing worked fine. I guess that is not a maven version problem.
Unless a quality patch is provided, m2e team has no plans to look into this.
I could try to do it. But this worked with maven integration for eclipse 0.12.1 (Sonatype) . Why not allow to choose the external maven to resolve eclipse project dependencies? Could you send me some information to start working on the patch?
(In reply to Fernando Las from comment #3) > I could try to do it. But this worked with maven integration for eclipse > 0.12.1 (Sonatype) . Why not allow to choose the external maven to resolve > eclipse project dependencies? I believe this is very hard to implement. If I were you, I'd look at adding scp wagon support first, which I believe should be relatively straightforward and I think does not require any changes to m2e core. Once you have this working and understand m2e codebase you can decide if want to look at using external maven runtime for dependency resolution. > Could you send me some information to start working on the patch? Start here http://wiki.eclipse.org/M2E_Development_Environment , then ask on m2e-dev@eclipse.org if you have questions.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
