[MNG-6460] Maven resolves old snapshot jars when an artifact changes from jar to pom deployment

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 3.5.0
• Component/s: Dependencies
• Assignee: Unassigned
• Reporter: Andy Grove
• Created: 17/Aug/18 00:38
• Updated: 21/Nov/20 21:34
• Resolved: 21/Nov/20 21:34

Description

I have two projects, A and B.

A started out as a simple project with single pom with jar packaging.

B had a dependency on A.

A was refactored to be multi module where each module has jar packaging. The parent pom now has pom packaging.

After building A and deploying new artifacts to artifactory, and making changes to B's pom I saw compilation errors with references to to the old A and the new A.

I eventually realized that B still had a reference to the original artifact from A (which was originally had jar packaging but now has pom packaging).

Even though the latest snapshot for the parent pom in A was correctly published with pom packaging and no corresponding jar file, the maven-dependency-plugin was resolving the jar file from the previous snapshot release from before the refactor.

This seems like a bug to me. It should have looked at the pom for the latest snapshot and seen that it had pom packaging and then failed to resolve the jar.