[Artifactory-users] maven-metadata.xml for artifacts seem corrupt

[Jan P. <jan...@le...>]

Hello,

I have a problem regarding artifactory (2.2.4 r11256) and maven-metadata.xml
files for some of the artifacts in a local repository. The problem has been
around for a while and probably relates to several previous versions of
artifactory since this artifactory instance has been around for several
years now.

There are two local repositories (one for snapshots and the other for
releases) to which the build server (TeamCity) deploys (maven deploy plugin
configured with the lightweight wagon-provider) artifacts to artifactory.

As time has passed, one of the artifacts (a pom project) has the following
snapshot versions (maven-metadata.xml from the snapshot repository):
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>my.company.project</groupId>
  <artifactId>project-parent</artifactId>
  <version>2.0.1-SNAPSHOT</version>
  <versioning>
    <latest>2.0.1-SNAPSHOT</latest>
    <versions>
      <version>1.7.1-SNAPSHOT</version>
      <version>1.7.0.1-SNAPSHOT</version>
      <version>2.0.1-SNAPSHOT</version>
      <version>2.0.2-SNAPSHOT</version>
      <version>2.0.3-SNAPSHOT</version>
      <version>2.0.4-SNAPSHOT</version>
      <version>2.0.5-SNAPSHOT</version>
      <version>2.0.6-SNAPSHOT</version>
      <version>2.0.7-SNAPSHOT</version>
      <version>2.0.8-SNAPSHOT</version>
      <version>2.0.9-SNAPSHOT</version>
      <version>2.0.10-SNAPSHOT</version>
      <version>2.0.11-SNAPSHOT</version>
      <version>2.0.12-SNAPSHOT</version>
      <version>2.0.13-SNAPSHOT</version>
      <version>2.0.14-SNAPSHOT</version>
    </versions>
    <lastUpdated>20100723010316</lastUpdated>
  </versioning>
</metadata>

The latest build deployed a 2.0.14-SNAPSHOT at 20100723010316, but that seem
not to be reflected in the artifact metadata in any way except that there
indeed exist a 2.0.14-SNAPSHOT version.

Actually, the 2.0.14-SNAPSHOT version does not have a maven-metadata.xml to
begin with (as I would have expected).

Version 2.0.1-SNAPSHOT has the following maven-metadata.xml:
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>my.company.project</groupId>
  <artifactId>project-parent</artifactId>
  <version>2.0.1-SNAPSHOT</version>
  <versioning>
    <snapshot>
      <buildNumber>27</buildNumber>
    </snapshot>
    <lastUpdated>20090518135240</lastUpdated>
  </versioning>
</metadata>

Version 2.0.13-SNAPSHOT has the following maven-metadata.xml:
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>my.company.project</groupId>
  <artifactId>project-parent</artifactId>
  <version>2.0.13-SNAPSHOT</version>
  <versioning>
    <snapshot>
      <buildNumber>1</buildNumber>
    </snapshot>
    <lastUpdated>20100331204229</lastUpdated>
  </versioning>
</metadata>

After inspecting the 2.0.13-SNAPSHOT, I can also tell that the metadata file
has not been updated as expected after the initial deploy (since build
number and update time does not reflect all times that version has been
rebuilt and deployed).

As stated above, 2.0.14-SNAPSHOT does not have a maven-metadata.xml at all.

The main problem at hand is that client side mvn builds do not detect that
the snapshot has been re-deployed, and the latest snapshot will not be
downloaded even if using -U to the mvn command line.

Is my artifactory corrupt?
Is there a way to manually trigger metadata to be rebuilt?
Anyone else having detected a corresponding problem?
Any solution or workaround available?

Of course, since this is a snapshot, I could probably just delete the whole
artifact and re-deploy a fresh 2.0.14-SNAPSHOT and forget about earlier
snapshots, but what if something similar happens to an artifact version in
the releases repository?

Any suggestions are welcome and assistance is greatly appreciated!

Regards - Janne

-- 
View this message in context: http://forums.jfrog.org/maven-metadata-xml-for-artifacts-seem-corrupt-tp5336149p5336149.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.