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

[Ben Walding]

Nope, Maven does check the date - it uses the http protocol to only 
download as required.  However I think there might be some issues in it 
- possibly even in the ibiblio web server / dates on the server (see my 
earlier email today)

I'll take a further look when I code up the snapshot downloader for the 
maven-proxy.

Kalaveshi, Adrian wrote:

I also don't believe that Maven checks to see which SNAPSHOT is newer.
Maven seems to always download it -- even if they are identical.  Anyone
have a definitive answer for this?  I'm using 1.0-rc1.
Using the "-o" option isn't sufficient enough.  I'd like to avoid
downloading SNAPSHOT jars of my internal projects (or, I should say, I'd
like to avoid overwriting the newer SNAPSHOT jar that exists in my local
repository) but, at the same time, I need to have access to everything else
in the repository.
-adrian-

-----Original Message-----
From: J�rn Gebhardt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 02, 2004 1:19 AM
To: Maven Users List
Subject: AW: multiproject:artifact, SNAPSHOT dependencies and the
reposito ry
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 2. M�rz 2004 04:20
An: Maven Users List
Betreff: Re: multiproject:artifact, SNAPSHOT dependencies and the
repository
"Kalaveshi, Adrian" <[EMAIL PROTECTED]> 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
   

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]