CVS Usage Page is blank when using Subversion scm.

I have tried to add necessary output to velocity macro cvs-usage.xml file. But it seems the following macros are not parsed if scm is svn in project.xml.

#set ($conn = $repository.getCvsRoot($repository.connection, ''))
#set ($module = $repository.getCvsModule($repository.connection))

I couldn't find the repository class in maven repository. If somebody shows me the code, i may alter it to parse it.

Anyway, i'll continue to examine the code.

I was using maven 1.0 and after downloading CVS snapshot, i realized that all maven-scm package is restructured.

After my observations, there is no method named getSvnRoot() inside maven versions 1.0 and 1.0.1.

Although situation seems to push me to wait for final-restructured-scm release, a quick hack can be done using jelly.

Ive seen that scm:parse-connection goal parses svn connection string into tokens. I may try to copy-paste code into xdoc/plugin.jelly and make maven.scm.svn variable available to velocity template. If i move it to xdoc plugin, xdoc can parse the connection string but it obviously results code duplication.

Anyway, this will be quick hack, not a real solution. After new maven scm release, problem will be solved simply by calling scm-provider-specific methods ie getCvsRoot(), getSvnRoot().

Attached patch parses svn <connection> string from pom and inserts it into generated cvs-usage.html.

It does not implement a parser for <developerConnection> string because i am bored that jelly does not have a regexp token replacer.

As I have discussed this patch must be updated according to new scm structure. I will be easier than my hacking effort.

svn.patch attachment seems to resolve the issue.

Ive forgotten a dot char in the output. Hope this night will end

Reopened to review patch

Patch is not directly applicable anymore (i18n), need to make ScmUtil SVN-aware.

Vincent S has done a fantastic job on this for the Maven 2.x plugin. Please investigate some way of reusing that, it greatly pains me to see so much duplicate work

Yes, I am aware of that. I forgot to mention to make it at least compatible with the m2 layout. Thanks!