maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MPOM-115) Add property for assembly descriptor version
Date Tue, 10 May 2016 23:25:12 GMT

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

Christopher Tubbs commented on MPOM-115:
----------------------------------------

Yeah, although it would have helped in the two cited cases, the parent POM is usually released
shortly after a fix has been applied to the assembly descriptor. Hopefully that continues
to be the case if a future fix is needed.

Otherwise, it's very inconvenient to override the entire assembly configuration (which I was
doing prior to MPOM-47).

This change would be very minor, limited benefit. I can understand not wanting to add it.
It was just something I had thought could have helped in the previous cases.

> Add property for assembly descriptor version
> --------------------------------------------
>
>                 Key: MPOM-115
>                 URL: https://issues.apache.org/jira/browse/MPOM-115
>             Project: Maven POMs
>          Issue Type: Improvement
>          Components: asf
>            Reporter: Christopher Tubbs
>
> The apache-source-release-assembly-descriptor dependency of the source assembly in the
apache-release profile specifies its version directly.
> This version should be moved into a property instead. That would ease users applying
fixes without having to completely override the assembly execution or the entire apache-release
profile to apply fixes like MASFRES-16, and MPOM-47 before that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message