Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0.5
-
Component/s: Design, Patterns & Best Practices, Documentation: General
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
it says:
$ svn checkout http://svn.apache.org/repos/asf/maven/components/trunk/ maven-site
We really should set the SCM URL correctly in the site pom again (to point to the site SCM), and the generated report should be excluded from the navigation. It could still be generated and linked from another doc that describes helping with the docs.
Attached is a change to the POM to fix the prefix for the source repository. However it does not address two issues:
1. It is still misleading to have SCM access for "Maven" only point to the site's source
2. maven-project-info-reports-plugin is coded to add the artifactId (maven-site in this case) to the end of all SCM URLs. A pre-existing comment in the POM states that the SCM section was repeated to prevent maven-site from being added, however the plugin will still add it regardless. I created
MPIR-33to address generated SCM access without the addition of the artifactId.MPIR-33to address generated SCM access without the addition of the artifactId.