Joern -- I can't reproduce this behavior. For me, whenever a jar has "-SNAPSHOT.jar" in it's name, it copies the version from the remote repository (overwriting whatever is in the local repository). It doesn't seem to matter if your dependency is <version>1.1-SNAPSHOT</version> or just <version>SNAPSHOT</version>.
Might this be an Apache configuration problem? Any help would be greatly appreciated. -adrian- -----Original Message----- From: J�rn Gebhardt [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 02, 2004 7:37 AM To: Maven Users List Subject: AW: multiproject:artifact, SNAPSHOT dependencies and the reposito ry Hi Ben, maybe there is also a difference between SNAPSHOT and versioned SNAPSHOT jars. I.e. if your project A has a currentVersion like '1.1-SNAPSHOT' and you create the jar with 'maven jar:install' you'll have a 'a-1.1-SNAPSHOT.jar' in your local repository. In this case if a project B has a dependency like this <dependency> <groupId>a</groupId> <artifactId>a</artifactId> <version>1.1-SNAPSHOT</version> </dependency> a new version in your local repository gets overriden by an older version in the remote repository. However, if you install your jar with 'maven jar:install-snapshot' you'll find a 'a-SNAPSHOT.jar' and a 'a-YYYYMMDD.HHMMSS.jar' in your local repository. Maybe in this case if project B has a dependency like this <dependency> <groupId>a</groupId> <artifactId>a</artifactId> <version>SNAPSHOT</version> </dependency> the local 'a-SNAPSHOT.jar' doesn't get overridden by an older remote version. Note, that the Maven project and the Maven-Plugin uses the first way of creating SNAPSHOT jars. It would be great, if a SNAPSHOT download would check the date in bith cases. Joern > -----Urspr�ngliche Nachricht----- > Von: Ben Walding [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 2. M�rz 2004 16:11 > An: Maven Users List > Betreff: Re: multiproject:artifact, SNAPSHOT dependencies and the > reposito ry > > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
