[ 
https://issues.apache.org/jira/browse/AMQ-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736909#comment-17736909
 ] 

Jean-Baptiste Onofré commented on AMQ-9268:
-------------------------------------------

This update breaks the release process:

- basically the maven-source-plugin is called twice: with jar goal in the 
ActiveMQ deploy, with jar-no-fork coming from apache-release profile (from the 
Apache POM).
 * with maven-source-plugin 3.2.1, we just have a warning when we attach source 
artifact twice (from the jar goal and from the jar-no-fork)
 * with maven-source-plugin 3.3.0, there's no warning anymore, we have a 
failure instead

We have two options:
 * not use the apache-release profile (in maven-release-plugin), and do our own 
plugins configuration
 * not define explicitily the maven-source-plugin and just use the one from the 
apache-release profile

> Upgrade to maven-source-plugin 3.3.0
> ------------------------------------
>
>                 Key: AMQ-9268
>                 URL: https://issues.apache.org/jira/browse/AMQ-9268
>             Project: ActiveMQ
>          Issue Type: Dependency upgrade
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 5.19.0, 5.18.3
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to