Svnchangelog-maven-plugin

I had to disable this for the project to build

</excludes>
          <!--compilerArguments>
            <verbose/>    
            <bootclasspath>${settings.localRepository}/com/sun/rt/1.4.2_13/rt-1.4.2_13.jar</bootclasspath>
          </compilerArguments-->
        </configuration>
        <!--dependencies>
          <dependency>
            <groupId>com.sun</groupId>
            <artifactId>rt</artifactId>
            <version>1.4.2_13</version>
          </dependency>
        </dependencies-->
      </plugin>

The site

• examples/example.html has a typo in the xdoc file name (exemple.xml). By the way this file could use better formatting.
• might be useful to describe what to do to add support to extra trackers

I looked briefly at the code. Some comments:

• code formatting isn't following project standard (1450 checkstyle errors)
• some comments are in French (e.g. in POM or site.xml)
• your might want to provide a french translation for the report
• some strings are hardcoded in the scm activity report
• in the scm activity report, some fields could be made @required
• hashcode() in SvnTargetEnum treats this.name == null as a potential case (shouldn't and not consistent with equals). Same for others.
• super() is optional
• in AbstractBufferedConsumer you could change the analize() contract change and make it return the elements, and get rid off the analyzed field and test for elements == null instead. Makes analyze() self contract descriptive
• you can reuse server in loadInfosFromSettings()

and as Trygvis said in the mailing list, how hard to make this scm independant ?

as for the bug Tracker interface, it would be nice to start a project to handle common issue trackers operations. But that's for later on...

Hope that helps.

Hi,
Thanks for your remarks !! I will take them into account as much as I can do this friday.
For the rt.jar this comes from the fact that I am using a jdk6 and I wanted to assure compatibility with the jdk1.42.
I will export the Strings so that we may have I18n. I am sorry for the French left (mother tongue) ;o).
ASfor the others SCM, most of the work is done by using the tags elements, I don't know for others scm. I don't think cvs would qualify.
I will improve the documentation for developpers, it is definitively lacking.
I'll hope to post an improved version soon.
Emmanuel

Updated code formatting, and Jerome's remarks are taken into account.
Updated documentation (the example is still to light, I know) with some elements about how to extend it.
Removed French comments
Removed rt.jar dependency.

Some images were in our skin, I have added them to the project.
There was an error with the internationalization.
I have updated the example and we provide a erport generated on another project while we are waiting for Codehaus svn urls to be ready.
Emmanuel

Implementation of Mercurial is done :o)
What blocks me from using only Maven scm Api is the fact that I can't get the revision in a ChangeSet. currently I have to provide my own implementation of commands to return this information.
Emmanuel

No more francetelecom reference.
Support for Hg.
Documentation update

The plugin should be renamed as scmchangelog-maven-plugin has it can be used with at least 2 SCMs and more could be supported.

https://svn.codehaus.org/mojo/trunk/sandbox/scmchangelog-maven-plugin