latest snapshot not downloaded

[Brian Parker]

Hello,

Even with updatePolicy of always or -U, maven is not downloading the latest
snapshot dependency from my http repository (artifactory).  I can see that
the maven-metadata*.xml files are being updated.  Can anyone recommend the
best way to debug the issue, in order to see exactly what is going on?
 Using -X doesn't really tell me why maven thinks the jar in my local repo
is up to date.

The filesystem timestamp of the jar in my local repo is older than the value
in the maven-metadata*.xml on the server, so I would expect the jar to be
downloaded again.

Thanks!

Brian

Re: latest snapshot not downloaded

[Brian Parker]

Sorry, forgot to mention I'm using maven 3.0.3, on Mac.

Brian

On Sun, Jul 31, 2011 at 2:14 PM, Brian Parker wrote:

> Hello,
>
> Even with updatePolicy of always or -U, maven is not downloading the latest
> snapshot dependency from my http repository (artifactory).  I can see that
> the maven-metadata*.xml files are being updated.  Can anyone recommend the
> best way to debug the issue, in order to see exactly what is going on?
>  Using -X doesn't really tell me why maven thinks the jar in my local repo
> is up to date.
>
> The filesystem timestamp of the jar in my local repo is older than the
> value in the maven-metadata*.xml on the server, so I would expect the jar to
> be downloaded again.
>
> Thanks!
>
> Brian
>

Re: latest snapshot not downloaded

[Brian Parker]

This turned out to be an Artifactory configuration error with regard to
Maven 3 and non unique snapshots.  This page has a blurb about it:

http://wiki.jfrog.org/confluence/display/RTF/Local+Repositories

Thanks!

Brian

On Sun, Jul 31, 2011 at 2:23 PM, Brian Parker wrote:

> Sorry, forgot to mention I'm using maven 3.0.3, on Mac.
>
> Brian
>
>
> On Sun, Jul 31, 2011 at 2:14 PM, Brian Parker wrote:
>
>> Hello,
>>
>> Even with updatePolicy of always or -U, maven is not downloading the
>> latest snapshot dependency from my http repository (artifactory).  I can see
>> that the maven-metadata*.xml files are being updated.  Can anyone recommend
>> the best way to debug the issue, in order to see exactly what is going on?
>>  Using -X doesn't really tell me why maven thinks the jar in my local repo
>> is up to date.
>>
>> The filesystem timestamp of the jar in my local repo is older than the
>> value in the maven-metadata*.xml on the server, so I would expect the jar to
>> be downloaded again.
>>
>> Thanks!
>>
>> Brian
>>
>
>

Re: Maven 3.0.3: Problems with SNAPSHOT updates

[Brian Parker]

I ran in to this.  See
http://stackoverflow.com/questions/5249342/maven-3-0-2-u-option-does-not-update-snapshot/7081166#7081166

Brian

On Fri, Oct 21, 2011 at 5:13 AM, Dreier Ruediger wrote:

> Hello!
>
> Thanks for your answer, but both solutions do not work for me with Maven 3
> - both work perfectly with Maven 2.2.1.
> With Maven 3 only a metadata file is updated, not the artifact itself.
>
> Regards,
>
> Ruediger
>
>
> > -Original Message-
> > From: Thiessen, Todd (Todd) [mailto:tthies...@avaya.com]
> > Sent: Thursday, 20 October, 2011 17:09
> > To: Maven Users List
> > Subject: RE: Maven 3.0.3: Problems with SNAPSHOT updates
> >
> > There are two ways. You can force maven to update snapshot by using the -
> > U option. Ie:
> >
> > mvn -U install
> >
> > Or you can change when maven updates snapshots by default by changing
> > the updatePolicy in your settings.xml file.
> >
> > http://maven.apache.org/ref/3.0.3/maven-settings/settings.html
> >
> >
> > > -Original Message-
> > > From: Dreier Ruediger [mailto:ruediger.dre...@bdal.de]
> > > Sent: Thursday, October 20, 2011 11:02 AM
> > > To: 'users@maven.apache.org'
> > > Subject: Maven 3.0.3: Problems with SNAPSHOT updates
> > >
> > > Hello!
> > >
> > > We are currently using Maven 2.2.1 and Artifactory 2.3.4 (rev. 13017)
> > > as repository server and I am now evaluating if we can migrate to
> > > Maven 3.
> > >
> > > I am testing Maven 3 in the following environment:
> > >
> > > Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Java version:
> > > 1.6.0_26, vendor: Sun Microsystems Inc.
> > > Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7",
> > > version: "6.1", arch: "x86", family: "windows"
> > >
> > > I used a very simple POM file for this check:
> > >
> > >   
> > > 
> > >   de.bdal.common.bcl
> > >   settings
> > >   0.0.0.1-SNAPSHOT
> > >   binaries
> > >   zip
> > > 
> > >   
> > >
> > >   
> > > 
> > >
> > >   
> > >
> > > org.apache.maven.plugins
> > > maven-dependency-plugin
> > > 2.2
> > > 
> > >   
> > > process-resources
> > > 
> > >   unpack-dependencies
> > > 
> > > 
> > >   true
> > >   ./target/references
> > > 
> > >   
> > > 
> > >   
> > >
> > > 
> > >   
> > >
> > >
> > > On a second PC (our Jenkins build system, still using Maven 2.2.1) the
> > > project de.bdal.common.bcl:settings can be build.
> > >
> > > With an empty local repository, everything works well:
> > > 'mvn install' downloads the newest version of
> > > de.bdal.common.bcl:settings to my local repository and the dependency
> > > plugin extracts it.
> > >
> > > Then I use Jenkins on the build system to create a new SNAPSHOT build
> > > of de.bdal.common.bcl:settings.
> > >
> > > Now I try to use this new version:
> > >
> > > 'mvn -U install' only downloads metadata:
> > >
> > > Downloading:
> > > http://hbeswbinaries1/repo/de/bdal/common/bcl/settings/0.0.0.1-
> > > SNAPSHOT/maven-metadata.xml
> > > Downloaded:
> > > http://hbeswbinaries1/repo/de/bdal/common/bcl/settings/0.0.0.1-
> > > SNAPSHOT/maven-metadata.xml (319 B at 4.0 KB/sec)
> > >
> > > and my local repository contains updated files "maven-metadata-
> > > inhouse.xml", "maven-metadata-inhouse.xml.sha1" and "resolver-
> > > status.properties". But all other files are not changed (especially
> > > settings-0.0.0.1-SNAPSHOT-binaries.zip is not updated). However
> > > "maven- metadata-inhouse.xml" contains the correct value for
> > > lastUpdate (build time on the server).
> > >
> > > What am I doing wrong?
> > > How do I get updates of snapshot dependencies without deleting my
> > > local repository?
> > >
> > > Thanks for any help,
> > >
> > > i.A. Rüdiger Dreier
> > > Project Manager
> > >
> > > Bruker Daltonik GmbH
> > > Fahrenheitstr. 4
> > > 28359 Bremen, Germany
> > >
> > > Phone: +49 421 2205-393
> > > Fax: +49 421 2205-3005
> > >
> > > ruediger.dre...@bdal.de
> > > www.bruker.com
> > >
> > >
> > >
> > > 
> > > Sitz der Gesellschaft / Registered Office Bremen; Handelsregister
> > > Amtsgericht Bremen HRB 8150 / Commercial Register District Court
> > > Bremen HRB 8150; Geschäftsführer / Managing Directors: Frank Laukien,
> > > Ph. D., Gerd Hülso, Sebastian Meyer-Plath, Stefan Ruge, Ian Sanders,
> > > Ph. D., Dr. Michael Schubert
> > >
> > > Haftungsausschluss: Die Bruker Daltonik GmbH ist nicht verantwortlich
> > > für die ordnungsgemäße, vollständige und verzögerungsfreie Übertragung
> > > der Nachricht. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn
> > > er unsererseits durch einen Brief oder ein Fax entsprechend bestätigt
> > > wird.
> > >
> > > Disclaimer: Bruker Daltonik GmbH is not responsible for correct,
> > > complete and timely transmission of this message. The c