maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <>
Subject [jira] [Commented] (MPOM-90) Give user control over finalName for source-release-assembly
Date Fri, 06 Nov 2015 20:55:11 GMT


Karl Heinz Marbaise commented on MPOM-90:

First the dist archives are filled by using SVN which means they will be updated after a successful
VOTE. Furthermore why not deploying to Nexus which is the door to maven central...and best
is to VOTE on the releases in the stage repository which makes it easier to cancel a VOTE
by just dropping the staging repository...only in case of a successful VOTE the artifacts
are checked-in into SVN to the dist repository...Apart from the above, if you just VOTE on
the dist content you can not verify the checksum of your release artifacts cause they are
not part of the dist repository....

Furthermore the configuration of the finalName will only change the name for the local {{target}}
folder and will **not** change the name which is deployed into a maven to
be honest i don't see a real use case for this.

If you really don't like the configuration you simply overwrite the configuration or just
turn off the usage of maven-assembly-plugin completely if you like...

> Give user control over finalName for source-release-assembly
> ------------------------------------------------------------
>                 Key: MPOM-90
>                 URL:
>             Project: Maven POMs
>          Issue Type: Improvement
>    Affects Versions: ASF-17
>            Reporter: Thomas Weise
> The out of the box behavior is pretty good, but it should be possible to customize the
name of the resulting archive (default $\{}.

This message was sent by Atlassian JIRA

View raw message