Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
This problem was introduced by SEDONA-276, where we changed how the maven project was configured.
This problem can be produced using Maven 3.6.3, but not using Maven 3.9.0.
I found that Maven 3.9.0 uses maven-deploy-plugin 3.0.0 by default while Maven 3.6.3 uses 2.7. After specifying the version of maven-deploy-plugin explicitly the problem went away on Maven 3.6.3.
I suspect that maven-deploy-plugin fixed this duplicated deployment problem in 3.0.0 but I cannot find a ticket for the MDEPLOY project. However, I'd like to upgrade maven-deploy-plugin to 3.0.0 for now instead of digging into this problem.