You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Allen (JIRA)" <ji...@codehaus.org> on 2006/11/23 15:55:31 UTC
[jira] Created: (MNG-2679) Support proper project identity in site
URLs
Support proper project identity in site URLs
--------------------------------------------
Key: MNG-2679
URL: http://jira.codehaus.org/browse/MNG-2679
Project: Maven 2
Issue Type: Improvement
Reporter: John Allen
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
[jira] Updated: (MNG-2679) Support proper project identity in site
URLs
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-2679) Support proper project identity in
site URLs
Posted by "John Allen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2679?page=comments#action_80905 ]
John Allen commented on MNG-2679:
---------------------------------
previous @dev postings on this subject include: http://www.nabble.com/Publishing-plugin-sites-tf2584348s177.html#a7226941
> Support proper project identity in site URLs
> --------------------------------------------
>
> Key: MNG-2679
> URL: http://jira.codehaus.org/browse/MNG-2679
> Project: Maven 2
> Issue Type: Improvement
> Reporter: John Allen
>
> 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
[jira] Moved: (MSITE-448) Support proper project identity in site
URLs
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl moved MNG-2679 to MSITE-448:
------------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Sites & Reporting)
Fix Version/s: (was: 3.x)
Key: MSITE-448 (was: MNG-2679)
Project: Maven 2.x Site Plugin (was: Maven 2 & 3)
> Support proper project identity in site URLs
> --------------------------------------------
>
> Key: MSITE-448
> URL: http://jira.codehaus.org/browse/MSITE-448
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Reporter: John Allen
>
> 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