My understanding is that:
- Maven 1 checked for newer versions of snapshots every build.
- Maven 2 checks, by default, once a day, but can be forced
 to check explicitly (I don't know how, though).

There's a -U option on Maven 2 to forcibly download new
versions, but that applies to *everything* not just snapshots,
so you'll download new versions of any plugin or report you use,
etc., which can be destabilizing.

-- Adam


On 8/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:

On 8/14/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
>
> It worked for me.
>
> kill your org.apache.shale folder in the m2_repo
>
> the correct JAR is public


Hmm ... does that not imply that Maven's "timestamp based" checks for
downloading later snapshots is not working?  The JAR in question is still
"
1.0.3-SNAPSHOT" but I understood Maven treated snapshots specially and
checked for updates automatically.

Craig

On 8/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > On 8/14/06, Adam Winer <[EMAIL PROTECTED]> wrote:
> > >
> > > Is the latest Shale code out on the snapshot repository?
> >
> >
> > Yes, in the Apache snapshot repository (version 1.0.3-SNAPSHOT is
> updated by
> > the nightly builds).
> >
> > -- Adam
> >
> >
> > Craig
> >
> > On 8/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > > > On 8/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > Compilation of current Trinidad version fails because of
tearDown
> and
> > > > > setUp method overriding. Should I look into it or another patch
> for
> > > test
> > > > > classes is already on the way?
> > > >
> > > >
> > > > I checked in a patch for this on  Saturday, and it compiles for
> > > me.  You'll
> > > > need the latest source code to deal with this.
> > > >
> > > > Regards,
> > > > >
> > > > > Simon Lessard
> > > > > Fujitsu Consulting
> > > > >
> > > >
> > > >
> > > > Craig
> > > >
> > > >
> > >
> >
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>


Reply via email to