[
https://issues.apache.org/jira/browse/MJAR-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957320#comment-17957320
]
Matthias Bünger commented on MJAR-242:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-jar-plugin#397|https://github.com/apache/maven-jar-plugin/issues/397].
> When building an empty project with mvn clean install deploy it will fail
> because it executes maven-jar-plugin twice with "have to use classifier"
> error.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MJAR-242
> URL: https://issues.apache.org/jira/browse/MJAR-242
> Project: Maven JAR Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 3.0.0
> Environment: 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"
> Reporter: Daniel Cruver
> Assignee: Robert Scholte
> Priority: Minor
> Attachments: empty-project-build.log, pom.xml
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
