I think the key is to leave metadata.xml and the latest snapshot in place
and just whack all the older ones.
On 11/28/06, Mark Reynolds <[EMAIL PROTECTED]> wrote:
Maven appears to key off the ordinal at the end of the snapshot name.
On 11/28/06, Jesse Kuhnert <[EMAIL PROTECTED] > wrote:
>
> I
Maven appears to key off the ordinal at the end of the snapshot name.
On 11/28/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I did "reset" the snapshots. Felt like the directories were getting
overly large.
I wonder why maven won't resolve them regardless though?
On 11/28/06, Mark Reynolds <[E
I did "reset" the snapshots. Felt like the directories were getting
overly large.
I wonder why maven won't resolve them regardless though?
On 11/28/06, Mark Reynolds <[EMAIL PROTECTED]> wrote:
It looks like the maven 4.1.1 SNAPSHOTs somehow started over as of November
25. The consequence seems
It looks like the maven 4.1.1 SNAPSHOTs somehow started over as of November
25. The consequence seems to be that you don't automatically get the new
snapshot.The workaround is to whack the org/apache/tapestry section of your
maven repository.
-- Mark R
