Could it be an Artifactory bug? What's the content of the
maven-metadata.xml file of the
seta.config:seta-general-configuration:1.0-SNAPSHOT artifact?

On Mon, May 18, 2009 at 09:24, Bocalinda <[email protected]> wrote:
> Hi Anders,
>
> Thanks a lot.. You are right, I need to specifically specify to update on
> each build.
> When I do so, I can see from Maven's output that it's trying to download my
> POM again, but it actually isn't.
> The POM changed in the remote repository, but it remained the same local
> repository. I'm guessing this is a problem with my remote repository not
> telling Maven that the file has changed.
>
> Just in case it would be useful in some way, here is the Maven output:
>
> [INFO] Scanning for projects...
> [DEBUG] Searching for parent-POM:
> seta.config:seta-general-configuration:pom:1.0-SNAPSHOT of project:
> derivacion:Derivacion:pom:1.0
>  in relative path: ../pom.xml
> [DEBUG] Parent-POM: seta.config:seta-general-configuration:pom:1.0-SNAPSHOT
> not found in relative path: ../pom.xml
> [DEBUG] Retrieving parent-POM:
> seta.config:seta-general-configuration:pom:1.0-SNAPSHOT for project:
> derivacion:Derivacion:pom:1.0 f
> rom the repository.
> [INFO] snapshot seta.config:seta-general-configuration:1.0-SNAPSHOT:
> checking for updates from releases
> [DEBUG] Checking for pre-existing User-Agent configuration.
> [DEBUG] Adding User-Agent configuration.
> [DEBUG] Connecting to repository: 'releases' with url: '
> http://172.18.0.78:3333/artifactory/releases/<http://172.18.0.78:3333/artifactory/sadiel-releases/>
> '.
> [DEBUG] Skipping disabled repository central
> [DEBUG] seta-general-configuration: using locally installed snapshot
> [DEBUG] Trying repository releases
> [DEBUG] Checking for pre-existing User-Agent configuration.
> [DEBUG] Adding User-Agent configuration.
> [DEBUG] Connecting to repository: 'releases' with url: '
> http://172.18.0.78:3333/artifactory/releases/<http://172.18.0.78:3333/artifactory/sadiel-releases/>
> '.
> Downloading:
> http://172.18.0.78:3333/artifactory/sadiel-releases//seta/config/seta-general-configuration/1.0-SNAPSHOT/seta-general-configuration-1.0<http://172.18.0.78:3333/artifactory/sadiel-releases//es/sadiel/seta/config/seta-general-configuration/1.0-SNAPSHOT/seta-general-configuration-1.0>
> -SNAPSHOT.pom
> [DEBUG]   Artifact resolved
>
> It says "Downloading" but it didn't actually download anything.
>
> 2009/5/15 Anders Hammar <[email protected]>
>
>> I think SNAPSHOTs are only updated once a day or so, not for every
>> build. You can force it through "mvn -U" or by settings updatePolicy
>> in your settings.xml:
>>
>> http://maven.apache.org/ref/2.0.8/maven-settings/settings.html#class_releases
>>
>> Here's a blog about this:
>>
>> http://jlorenzen.blogspot.com/2008/07/maven-not-downloading-latest-snapshots.html
>>
>> /Anders
>>
>> On Fri, May 15, 2009 at 12:14, Bocalinda <[email protected]> wrote:
>> > Hi List,
>> >
>> > According to the documentation, when specifying a version as -SNAPSHOT,
>> > Maven downloads the artifact on each build.
>> >
>> > I specify:
>> >
>> >  <parent>
>> >    <groupId>config</groupId>
>> >    <artifactId>seta-general-configuration</artifactId>
>> >    <version>1.0-SNAPSHOT</version>
>> >  </parent>
>> >
>> > and expected Maven to download the parent pom again from the repository,
>> > however, this doesn't seem to be the case.
>> > Is this a bug, or is it not supported?
>> >
>> > I manage the parent pom, which is used in many different projects. The
>> > problem is that I am not the developer of all those projects, so if I
>> would
>> > change something in the parent pom, then I have no control over whether
>> > people are updating the parant pom version in order to fetch te latest
>> > version. It would be much easier if I could leave it as SNAPSHOT, and
>> have
>> > Maven download it each time a build is executed.
>> >
>> > I'm using Maven 2.1.0.
>> >
>> > Thanks.
>> >
>>
>> ---------------------------------------------------------------------
>> 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]

Reply via email to