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

Brett Porter updated MNG-2679:
------------------------------

    Fix Version/s:     (was: Reviewed Pending Version Assignment)
                   2.2.x
      Component/s: Sites & Reporting

> Support proper project identity in site URLs
> --------------------------------------------
>
>                 Key: MNG-2679
>                 URL: http://jira.codehaus.org/browse/MNG-2679
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Sites & Reporting
>            Reporter: John Allen
>             Fix For: 2.2.x
>
>
> IMHO there is a lack of proper POM UID namespace management in the URL 
> inheritence and extension  schemes used in site generation. I may have 
> a latest version of a project and this may have a nice site but i need to be 
> able to continue to access, and critically link to (from other projects), 
> older versions of the same project's sites. The 'latest' version can always 
> be made accessible via some nice URL mapping e.g. 
> http://maven.apache.org/plugins/maven-clean-plugin/ == 
> http://maven.apache.org/org/apache/maven/plugins/maven-clean-plugin/2.1.1/
> For me a site is simply another 'view' onto a project's products and in the 
> same way one can access different versions of those products based on specify 
> the version one can not access the various different sites. Note this can be 
> done by manually specifying the project.url and 
> project.distributionManagement.site.url for every project such that the URLS 
> include the group, artefact and versionId information but this is error prone 
> and nasty.
> In a nutshell, for us a project's site is just another project artefact and 
> therefore its identity should be preserved in the same robust way the the 
> other project products are (jars, pom, src-jars etc), i.e. stored in a unique 
> federated namespace. 
>  

-- 
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

        

Reply via email to