Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Not A Problem
-
3.0.0
-
None
-
None
-
None
-
Windows 10 x64
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c; 2015-03-13T16:10:27-04:00)
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_131\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"Windows 10 x64 Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c; 2015-03-13T16:10:27-04:00) Java version: 1.8.0_131, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.8.0_131\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
Description
This issues should never happen because who has empty projects, well our project had a few, so I ran across this issue when running mvn clean install.
"You have to use a classifier to attach supplemental artifacts to the project instead of replacing"
I have attached the build log and an example pom that can reproduce the error, assuming you updated the distributionManagement section with an actual Maven Repository.