[JIRA] Created: (JPAR-12) Generation of SCM URL's in generated site is broken, URI's are invalid

[Brent Putman (JIRA)]

Generation of SCM URL's in generated site is broken, URI's are invalid
----------------------------------------------------------------------

                 Key: JPAR-12
                 URL: https://issues.shibboleth.net/jira/browse/JPAR-12
             Project: Java Parent Project
          Issue Type: Bug
            Reporter: Brent Putman
            Assignee: Brent Putman
            Priority: Minor


For completely different reasons, the SCM output of v2 and v3 reports is broken.  The SCM report plugin seems to default to appending ${project.artifactId } on the end of the various SCM URL's.  I don't immediately see any way to change that.  You can change the name of the directory that it puts in the check-out command after the URL, but that doesn't affect how the URL is constructed[1].


So we get output that looks like this for a monolithic project (where the artifactId = "xmltooling"):

http://svn.shibboleth.net/view/java-xmltooling/xmltooling

$ svn checkout https://svn.shibboleth.net/java-xmltooling/xmltooling xmltooling


and this for a multi-module project (where the artifactId = "aggregator-cli")

http://svn.shibboleth.net/view/java-metadata-aggregator/aggregator-cli

$ svn checkout https://svn.shibboleth.net/java-metadata-aggregator/aggregator-cli aggregator-cli


which are invalid b/c the artifactId isn't really a part of any of those paths and/or it doesn't take into account that there's actually a trunk/tags/branches structure underneath there.


So, I think we have to completely re-think how all this works, unless there are other knobs and switches that can be used to control this behavior.

[1] http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira