Adding a apache-snapshot as plugin repository could resolve this problem.
<pluginRepositories>
<pluginRepository>
<id>apache-snapshots</id>
<name>Apache Snapshots Repository</name>
<url>http://repository.apache.org/snapshots</url>
<layout>default</layout>
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
<checksumPolicy>ignore</checksumPolicy>
</snapshots>
<releases>
<enabled>false</enabled>
</releases>
</pluginRepository>
</pluginRepositories>
I think It should be a defect of MAVEN. But anyway, we should add the plugin
repository to workaround this problem for now.
On Fri, Jul 17, 2009 at 11:08 PM, Kevan Miller <[email protected]>wrote:
>
> On Jul 17, 2009, at 9:23 AM, Donald Woods wrote:
>
> I ran into build problems like the automated 2.1 build, as I didn't build
>> the new Tomcat artifacts locally and the snapshot resolution seems to be
>> broken due to using unique timestamps for the deployed artifacts....
>>
>
> K. Sigh. I'll have a look, but not likely to be until this afternoon... If
> anybody wants to have a look, feel free. Until then, building
> geronimo/external/trunk/tomcat-parent-6.0.20/ should avoid the problem...
>
> --kevan
>
>
--
Shawn
