Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
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.
previous @dev postings on this subject include: http://www.nabble.com/Publishing-plugin-sites-tf2584348s177.html#a7226941