Maven plugin keeps looking for non-existent apacheds-*-2.4.1 dependency

Please provide pom.xml to reproduce this issue.

Please note that I do not have any trouble running 'mvn compile' on this from the ocmmand line, just in eclipse!

It could be because of the old embedder version. I'll take a look.

Still not quite sure what is happening. I can only test this on Windows (usually I use Sun's JDK 1.5). So, when I created empty project with your pom (no any classes) and enabled Maven nature it was able downloaded all the dependencies - 131 in total. That is some pom! There was about 39Mb of dependencies downloaded on complete resolving, but none with 2.4.1 version.

Then I tried to launch maven for "compile" phase and got some error from the embedder which I'll have to check with Maven folks.

Can you please describe what exactly you doing? Can you try this on Windows and also enable "debug output" option on plugin preferences.

It seems that error I got before was because of some issues with ibiblio. This time "compile" phase completed ok.

Federico, can you try this on windows and/or attach your own log with debug enabled?

Actually, Federico and I work in the same project. He's in Mac OS X and I'm on Windows, and the funny thing is that I'm not getting the error.
So, something about the specific JVM? Eclipse version?

Federico, wasn't the problem in the "dependency checker" instead of the compile? I mean, if you go to Eclipse and click on "Maven 2 build" and set maven to build, there's no problem. But when the Maven plugin validates the POM (in the Eclipse Builder) it is getting the error, right??

And right now I think there's no way of showing a debug log on that ( the correct location would be $ECLIPSE_WORKSPACE/.metadata/.log )

Hmm. It should be generic, though your pom has profile info specific for Sun's jvm. Please specify exact scenario and confirm that it does in fact working on Windows.

If it is about m2 launcher you can enable "debug output" propery in plugin preferences and maybe compare execution log between mac and windows.

If it is about builder (dependency resolver) you can also try code from svn. We have added console that will show what is being downloaded. If you can't do that I'll have to pospond this issue after 0.0.4, so you can try with the release later.

Also, are you behind proxy or firewall that does not allow direct connection? Or maybe have some redefines in settings.xml (which is currently not being used by embedder)?

It may be related to MNGECLIPSE-26 and if it is I can suggest to try start Eclipse with explicitly defined JVM. Eg.

C:\eclipse-3.2M4\eclipse.exe -data C:\dev\workspace -vm C:\jdk1.5.0_05\bin\javaw.exe

Testproject that reproduces (some) of the problems.

I have attached a small project that intents to reproduce at least some of the problems I described. I hope this will give you the same results!

If you build this project with eclipse as it is, then the "cannot find artifact...." error will appear. If you tried to compile this from the command-line, you would get the output I uploaded.

Please confirm that you can reproduce this.

This project is not a complete reproduction of the issue, though. If you uncomment the commented lines in the pom.xml file, and defined the dependency with an explicit version number, then the problems encountered during compile are reported properly in the plugin. This, of course, has already been reported in MNGECLIPSE-20. What makes (I think) this bug different is the fact that, the reported error (looking for a dependency with version 2.4.1) seems to be substituting another error message for some reason (plese note that command-line output and plugin error message do not match!)

In the first description of this problem (does not apply to the small project I am attaching now) the interesting thing was that I changed every pom of the local repository so that they did not use any reference to ${version} and I still got the same error message.

Using JDK 5 on the testproject gives an error with a different version number:

"Unable to download the artifact from any repository directory:apacheds-main-1.0.jar"

BTW the default JDK on my system is JDK 1.4.2_09, which means that the JDK version is not affecting maven on the command line.

Moving to 0.0.5 because of dependency on MNGECLIPSE-20

Tested this with trunk build and dont see this anymore. If it still happens with 0.0.10 or trunk build, please reopen and attach complete Eclipse project with pom.xml to reproduce.

i found the reason for the "${pom.version} is 2.4.1" problem (for more details and a fix see MNGECLIPSE-20). there is a system property of name "version" set to "2.4.1" in your eclipse jvm (see [Eclipse]>Help>About Eclipse Platform->Configuration Details).

Reopening to change resolution