Maven: 3.3.3
Nexus: 2.14.5-02
We have a product made up of several components:
Comp1 -> Comp2 -> Comp3 -> Comp4 -> Product
That is the order of dependencies for the builds. Each component uploads
some JARs to Nexus using Maven deploy:deploy-file. What we are seeing
is that the latest artefacts that are uploaded to Nexus are not being
picked up by subsequent components and the product. They are all
using -SNAPSHOT versions, as they should be. I will try to
illustrate with an example.
I have the following:
Comp3-artefact-1.2.3.4.5-20170820-080555-18-all.zip
Comp3-artefact-1.2.3.4.5-20170821-080423-19-all.zip
Comp3-artefact-1.2.3.4.5-20170822-075728-20-all.zip
Comp3-artefact-1.2.3.4.5-20170823-075717-21-all.zip
on my Nexus server, that I see using the web-ui.
When I build the Product, it should pick up the *-21-all.zip artefact
as that is the latest. What happens though is that it picks up the
*-20-all.zip artefact. I have to manually rebuild the metadata and
rebuild the index through the Nexus webui and than re-start the build
for it to pick up the latest version.
This is true regardless of what component it is, and also is showing up
in between the Components as well.
Is this an indexing issue ? Is it in Maven or Nexus ? And what
should I do to fix it ?
cheers,
mehul
--