2007/3/28, Maria Odea Ching <[EMAIL PROTECTED]>:
Hi Stefan,
Maybe your dependency plugin metadata file (in local repo) isn't updated?
You could try installing the 2.0-alpha-4 version again with
-DupdateReleaseInfo=true..
I couldn't get a clue of that updateReleaseInfo-option you mentioned,
except of me fixing up the
org/apache/maven/plugins/maven-metadata-central.xml in my local repo
where there was depency-maven-plugin registered (the wrong one). That
solved my problem.
Hope this helps! :)
Thanks for pointing in the right direction :-)
Cheers,
Stefan
Thanks,
Deng
Stefan Hübner wrote:
> Hi,
>
> I've run into a weird issue, while trying to make use of the
> dependency-plugin's new resulve-feature.
>
> If I invoke Maven by mvn dependency:resolve, it complains about no
> goal "resolve" found in plugin. Digging into it with "-X" it becomes
> clear, that Maven is using a different dependency-plugin from what I
> was expecting, since it invokes
> "org.codehaus.mojo:dependency-maven-plugin:1.0".
>
> Why does Maven pick up that plugin in favour of
> "org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4", which
> available from my local repo as well?
>
> Any idea?
>
> Cheers,
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> !DSPAM:602,460a30a7165909301039927!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
