However, currently I am out of time and will check this later.
Just one thing: If m2e and maven only support http(s), why does the 0.9.8 plugin work?
My problem is that with the newer m2eclipse plugin my dependencies which should be fetched from our internal repository (over scp) do not become resolved. 0.9.8, all dependencies would be downloaded over scp from our repository instantly (tried this by renaming the .m2/repository directory and letting m2e fetching the dependencies from scratch). I just get error messages like this when watching the POM in the POM editor and clicking on one of the red messages at the top of the editor: ----------------- Project build error: Non-resolvable parent POM de.julielab:jules:1.3 for de.julielab:jules-medline-reader:1.15: Failed to resolve POM for de.julielab:jules:1.3 due to Missing: ---------- 1) de.julielab:jules:pom:1.3 ---------- 1 required artifact is missing.
for artifact: de.julielab:jules:pom:1.3 from the specified remote repositories: codehouse ( releases=true, snapshots=true), login (scp://login.../, releases=true, snapshots=true), central ( releases=true, snapshots=false) -------------- Both m2eclipse installations use the same .m2 directory and thus the same
Gradle plugin in Intelli J triggers Import Maven Repositories Task every time you run the IDE.
If your list of repositories is long or not always reliable you might want to disable this useless task.
Nexus Index Manager.update Index(Nexus Index Manager.java:1013) at org.eclipse.internal.index.
"Maven does not run" is not specific enough, unfortunately.
Also, the exception that you see comes from nexus-indexer integration and is expected because m2e only supports http(s) protocol to access remote indexes.
I used seperate workspaces and downloaded the same project down from our SVN, so the project I'm using to test this is identical in both workspaces.
Can you please explain what is the problem exactly?