[
https://issues.apache.org/jira/browse/MPOM-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994518#comment-14994518
]
Thomas Weise commented on MPOM-90:
----------------------------------
Regarding where the release candidates should be deployed: We were asked to put
them under https://dist.apache.org/repos/dist/dev/ and not in staging Nexus.
It's really cumbersome and certainly not my preference. One has to move around
the artifacts, create checksums and check them into SVN, duplicating what Maven
can do out of the box. Having said that, it seems to be ASF policy and the
current parent POM does not optimally support that policy?
I know that I can overwrite and duplicate everything (which to some extend we
already have to do), but that defeats the purpose of a common organization POM?
> Give user control over finalName for source-release-assembly
> ------------------------------------------------------------
>
> Key: MPOM-90
> URL: https://issues.apache.org/jira/browse/MPOM-90
> 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
> $\{project.build.finalName}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
