[jira] (MNG-4506) Split site deployment URLs into release vs. snapshot, just like artifacts

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MNG-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte updated MNG-4506:
--------------------------------

    Component/s: FDPFC

> Split site deployment URLs into release vs. snapshot, just like artifacts
> -------------------------------------------------------------------------
>
>                 Key: MNG-4506
>                 URL: https://jira.codehaus.org/browse/MNG-4506
>             Project: Maven
>          Issue Type: Improvement
>          Components: FDPFC, POM
>            Reporter: Matthew Beermann
>             Fix For: Issues to be reviewed for 4.x
>
>
> (This is for Maven 2.1. My apologies if it's a duplicate, but I couldn't find this issue reported elsewhere.)
> One of the things we've always considered to be a major design oversight in Maven is that the artifact repositories (in the <distributionManagement> section) are split up into releases vs. snapshots, but the site repository isn't. This practice significantly conflicts with the way that we (and many others) use Maven: there's a centralized, locked-down release artifact repository, there are many, loosely secured snapshot artifact repositories for each team, /and there's a corresponding site repository for each/.
> This organization doesn't seem especially radical, but the way the POM is organized makes it difficult to achieve. Either we have to (hope to) remember to update the site deployment URL just before a release, or else override it from the command line during the release. Would it be possible to split these two apart by enhancing the POM schema in Maven 2.1?



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)