Search code examples
eclipsemaven-2m2eclipseartifactory

Artifactory remote repository not up-to-date

I have 2 artifactory servers. Let say A and B.

One of them, A, has a remote repository pointing to the other, B.

My eclipse maven plugin (m2e) is configured to use B.

Let say I have on A an achetype myArchetype-1.0.jar.

The first time I use New maven project, the archetype-catalog.xml is downloaded on B and I can see the version 1.0 of myArchetype. Ok, it's good.

Now I publish the 2.0 version on A. The archetype-catalog.xml is also updated.

Back to eclipse, new maven project, the myArchetype is still with version 1.0. Nothing is updated on B.

What can I do to have the remote repository up-to-date ?

Solution

  • Artifactory does not support Maven Archetypes. That means that it is not aware of the fact that archetype-catalog.xml is expirable and should be checked for changes.

    If your Artifactory is Pro, you can implement the re-check via user plugin.