[hibernate-issues] [Hibernate-JIRA] Commented: (HV-423) Publish an API change report as part of the documentation

[Matt Doar (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HV-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39689#action_39689 ] 

Matt Doar commented on HV-423:
------------------------------

What does a compatibility centered report look like? JDiff takes two sets of source, generates one XML file for each set and then uses the two XML files to generate the report. Version control is only used to check out the source. I guess there is a maven plugin that does this for svn?

> Publish an API change report as part of the documentation
> ---------------------------------------------------------
>
>                 Key: HV-423
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-423
>             Project: Hibernate Validator
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Hardy Ferentschik
>             Fix For: 4.x
>
>
> These reports can be generated via JDiff or clirr. See also HV-417.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira