It's possible your maven had cached some metadata that caused maven to
not be able to locate the correct timestamp version.
On Thu, Sep 17, 2009 at 1:47 PM, Benson Margulies wrote:
> This seems to have been a nexus bug.
>
> I made some changes in how my mirrors were configured, and this problem
>
Could you be more specific about this potential bug?
Thanks,
~t~
On Thu, Sep 17, 2009 at 7:47 PM, Benson Margulies wrote:
> This seems to have been a nexus bug.
>
> I made some changes in how my mirrors were configured, and this problem
> evaporated.
>
>
This seems to have been a nexus bug.
I made some changes in how my mirrors were configured, and this problem
evaporated.
On Thu, Sep 17, 2009 at 10:22 AM, Olivier Lamy wrote:
> Hi,
> The snapshot url you are using and the stack trace you have could be
> very helpfull.
>
> 2009/9/17 Benson Ma
Hi,
The snapshot url you are using and the stack trace you have could be
very helpfull.
2009/9/17 Benson Margulies :
> I set out to use a snapshot of the maven-release-plugin. I added the
> snapshot repo to the pluginRepositories, with snapshots set to true.
>
> Then I called out version 2.0-beta-
