Some times maven refuses to download new released artifacts.  This seems
to occur when the lastUpdated value in the maven-metadata.xml is
similar, that is when the new release occurred soon after a prior
release.  However, we haven't been able to pinpoint an exact pattern to
this behavior.  In addition this may occur when we perform a maven
install or a when running idea:idea.

To resolve this we delete our local maven-metadata-inhouse.xml file,
which allows maven to download the correct version.

Old maven-metadata-inhouse.xml file:
<?xml version="1.0" encoding="UTF-8"?><metadata>
  <groupId>com.xrite</groupId>
  <artifactId>xrite-commons</artifactId>
  <version>1.0</version>
  <versioning>
    <release>1.18</release>
    <versions>
      <version>1.0</version>
      <version>1.2</version>
      <version>1.3</version>
      <version>1.4</version>
      <version>1.5</version>
      <version>1.6</version>
      <version>1.7</version>
      <version>1.8</version>
      <version>1.9</version>
      <version>1.10</version>
      <version>1.11</version>
      <version>1.12</version>
      <version>1.14</version>
      <version>1.15</version>
      <version>1.16</version>
      <version>1.17</version>
      <version>1.18</version>
    </versions>
    <lastUpdated>20070130165948</lastUpdated>
  </versioning>
</metadata>

With the old file it would not download the 1.20 version.  After
deleting the local file it would download version 1.20, here is the
resulting new file.

New maven-metadata-inhouse.xml file:
<?xml version="1.0" encoding="UTF-8"?><metadata>
  <groupId>com.xrite</groupId>
  <artifactId>xrite-commons</artifactId>
  <version>1.0</version>
  <versioning>
    <release>1.20</release>
    <versions>
      <version>1.0</version>
      <version>1.2</version>
      <version>1.3</version>
      <version>1.4</version>
      <version>1.5</version>
      <version>1.6</version>
      <version>1.7</version>
      <version>1.8</version>
      <version>1.9</version>
      <version>1.10</version>
      <version>1.11</version>
      <version>1.12</version>
      <version>1.14</version>
      <version>1.15</version>
      <version>1.16</version>
      <version>1.17</version>
      <version>1.18</version>
      <version>1.19</version>
      <version>1.20</version>
    </versions>
    <lastUpdated>20070130200231</lastUpdated>
  </versioning>
</metadata>

What may be causing this?

-dh


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to