Please open a bugreport and attach complete standalone project that
demonstrates the problem. I assume scp://localhost can be used to avoid
dependencies on external repositories.
I am not sure if there is anything we will be able to do about scp
repositories, but at least we'll have something in the backlog.
--
Regards,
Igor
On 11-07-25 11:08 AM, Erik Fäßler wrote:
Hey all,
since the out-of-the-box ssh/scp support has been removed from Maven 3.x, I use
the command line to download the dependencies of my projects from our internal
scp repository. For this to work, I use the wagon-scp extension:
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh</artifactId>
<version>1.0-beta-6</version>
</extension>
</extensions>
Then, I build my projects using "mvn compile" which loads all dependencies into
my local repository and everything's fine.
However, I'd really like to be able to resolve everything by the m2eclipse plugin within Eclipse.
But even with this extension, m2eclipse is not able to download our internal dependencies via scp.
Which further configurations are needed? I would love not being forced to switch to the command
line and perform an "mvn compile" every time an internal dependency has changed. I would
rather like to just activate dependency management / "update dependencies" to
automatically resolve all my dependencies, be it from public repositories via http or from our
internal repository via scp.
Best regards,
Erik
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users
