Brett Porter wrote:
Yes, I do see why this is happening. Perhaps what should happen is for the plugins to provide a jar override that specifies ${maven.home}/lib/maven.jar if that works.
- Brett
well, if that were the case then maven shouldnot try to download it, right ? however i tracked it a bit to pom and release plugins that both declares :
<dependency>
<jar>maven.jar</jar>
<groupId>maven</groupId>
<artifactId>maven</artifactId>
<version>1.0-rc2</version>
</dependency>seems to be the root of the problem.. the funny thing is that on ibiblio maven.jar is 3 months old - older than rc2 thus.
is it something we should consider normal or do i have to enter a jira issue for that ? i personnally find odd that the artifactId-version pattern isnot applied there..
-- gd
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
