Split site deployment URLs into release vs. snapshot, just like artifacts
-------------------------------------------------------------------------
Key: MNG-3699
URL: http://jira.codehaus.org/browse/MNG-3699
Project: Maven 2
Issue Type: Improvement
Components: Sites & Reporting
Affects Versions: 2.0.9
Reporter: Matthew Beermann
(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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
