sorry about the noise, my pom also calls
<!-- add main jar to staging -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<id>project-jar-for-rpm</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<outputDirectory>${rpm.staging.directory}/lib</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
to push the main jar to another directory consumed by rpm-m-p, that
triggers this issue
Looks like I have to use antrun instead. Ouch!!
-Dan
On Thu, May 19, 2016 at 10:16 PM, Dan Tran <dant...@gmail.com> wrote:
> Hi
>
> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
> throws this error
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker)
> on project xxx: You have to use a classifier to attach supplemental artifacts
> to the project instead of replacing them. -> [Help 1]
>
>
> This is a valid use case where I can have mutiple artifact extensions without
> the need to use classifiers
>
>
> The release notes of jar plugin 3.0.0 also not mentioned about this
>
>
> I hope this is not intentional
>
>
> My appology, i should have tested the during its voting period
>
>
> Thanks
>
>
> -Dan
>
>
>
>
