[ http://jira.codehaus.org/browse/MNG-2289?page=comments#action_66485 ]
Federico commented on MNG-2289:
-------------------------------
Hi,
we have the same problem when using the following configuration in our POM:
<snapshotRepository>
<id>internalRepo</id>
<name>our company internal repo</name>
<url>ftp://maven.xxx.xxx/opt/repository/maven</url>
<!-- uniqueVersion == false is needed to upload snapshots releases
without changing fileName to timestamp+buildNumber.
All deployment will override the -SNAPSHOT files on the repo. -->
<uniqueVersion>false</uniqueVersion>
</snapshotRepository>
during deploy phase the -SNAPSHOT.jar on the server is overridden by the newer
one and maven-metadata.xml is updated properly but when another client run
maven (and has already the older version of the SNAPSHOT in its local
repository) it doesn't download the newer pom and jar.
maven (with debug enabled says):
[DEBUG] Retrieving parent-POM: xxx:yyy::0.3.1-SNAPSHOT for project:
xxx:zzz:jar:0.3.1-SNAPSHOT from the repository.
[DEBUG] yyy: using locally installed snapshot
if we run on the client maven with the -U option we get:
[DEBUG] Retrieving parent-POM: xxx:yyy::0.3.1-SNAPSHOT for project:
xxx:yyy:jar:0.3.1-SNAPSHOT from the repository.
[INFO] snapshot xxx:yyy:0.3.1-SNAPSHOT: checking for updates from internalRepo
[INFO] snapshot xxx:yyy:0.3.1-SNAPSHOT: checking for updates from central
[DEBUG] repository metadata for: 'snapshot xxx:yyy:0.3.1-SNAPSHOT' could not be
found on repository: central
[DEBUG] yyy: using locally installed snapshot
in both cases maven is not downloading the newest POM.
Another strange thing is that after looking in our internalRepo it still looks
in the central repo if the metadata are there. Maven should have found metadata
information in our internalRepo (infact it DOES NOT give out the error
(repository metadata for: 'snapshot xxx:yyy:0.3.1-SNAPSHOT' could not be found
on repository: internalRepo). It seems maven find the metadata on our repo but
not consider it.
let me know if I can do some more test,
best regards,
Federico
> Newer SNAPSHOT parents in the remote repository are ignored
> -----------------------------------------------------------
>
> Key: MNG-2289
> URL: http://jira.codehaus.org/browse/MNG-2289
> Project: Maven 2
> Type: Bug
> Components: Inheritence and Interpolation
> Versions: 2.0.4
> Reporter: Joerg Schaible
> Priority: Critical
> Attachments: example.zip, mng2289.zip
>
>
> If a POM inherits from another one in the repository with a SNAPSHOT version,
> it will only look into the local repository for it, but not in the remote
> repositories.
> E.g. if a POM has following parent:
> {noformat}
> ...
> <parent>
> <groupId>pom.maven</groupId>
> <artifactId>super</artifactId>
> <version>SNAPSHOT</version>
> </parent>
> ...
> {noformat}
> it will not find a newer version of "pom.maven:super:SNAPSHOT" in a remote
> repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
