AW: multiproject:artifact, SNAPSHOT dependencies and the reposito ry

[Jörn Gebhardt <Jo...@ptv.de>]

Hi,

That's strange. We have exactly the same problem that Adrian described. I
believe that Maven doesn't check any dates when resolving SHNAPSHOT
dependencies, but just downloads the SNAPSHOT jar from the remote repository
if it is there.

I've posted a similar message some weeks ago and was advised to used the -o
(offline) option of Maven (e.g. maven -o jar) to suppress the download from
the remote server. Alternatively, you can set a property (I don't remember
the property name, but it's documented somewhere...) in your local
build.properties to switch to the offline mode.

Jörn

> -----Ursprüngliche Nachricht-----
> Von: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Gesendet: Dienstag, 2. März 2004 04:20
> An: Maven Users List
> Betreff: Re: multiproject:artifact, SNAPSHOT dependencies and the
> repository
> 
> 
> "Kalaveshi, Adrian" <ak...@rsasecurity.com> wrote on 02/03/2004 
> 08:09:36 AM:
> 
> > Greetings --
> > 
> > Is there a best practices document describing maven's role in a 
> multiproject
> > environment?
> > 
> > One of the problems I'm currently trying to tackle is this: 
> > 
> > - internal components have dependencies to SNAPSHOT 
> versions of other
> > internal components.
> > - after each project is compiled, it's SNAPSHOT artifact is 
> created and
> > 'installed' to the local repository (for use by other projects)
> 
> We have exactly this.
> 
> > - when the next project is compiled, it's dependencies are 
> downloaded 
> from
> > the repository (overwriting the SNAPSHOT artifact that was 
> created in 
> the
> > previous line item)
> 
> This doesn't happen for us. We never get a download as our 
> local SNAPSHOT 
> is newer than the one in the remote repo.
> 
> --
> dIon Gillard, Multitask Consulting
>