This is possibly a bug http://jira.codehaus.org/browse/MNG-3144
http://jira.codehaus.org/browse/MNG-3144 . The pom is updated but the jar
remains untouched (except for timestamp touch).
baerrach wrote:
>
> On 5/18/07, Evan Worley <[EMAIL PROTECTED]> wrote:
>> Barrie,
>>
>> Have you tried runni
On 5/18/07, Evan Worley <[EMAIL PROTECTED]> wrote:
Barrie,
Have you tried running with the "U" option? This forces maven to check for
snapshot updates. If you don't specify the U option, maven will check for
updates according to your snapshot update policy interval. I believe the
default is o
Barrie,
Have you tried running with the "U" option? This forces maven to check for
snapshot updates. If you don't specify the U option, maven will check for
updates according to your snapshot update policy interval. I believe the
default is once a day.
-Evan
On 5/16/07, Barrie Treloar <[EMAI
On 5/17/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Hi Zak,
Your interpretation sounds correct, so I'm not sure why that happens
incorrectly. Do you see this every time, or only in a clean repository?
The metadata file is indeed used to determine the latest - check the
lastUpdated timestamp ins
Hi Zak,
Your interpretation sounds correct, so I'm not sure why that happens
incorrectly. Do you see this every time, or only in a clean repository?
The metadata file is indeed used to determine the latest - check the
lastUpdated timestamp inside the file. The locally installed version
is
