[
https://issues.apache.org/jira/browse/LUCENE-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551619
]
Matt Doar commented on LUCENE-1083:
-----------------------------------
The attached 1083_1.patch file does most of what you suggested. The svn task is
not in ant core yet, so I couldn't use it to check out the source of the
previous version. I had to define the version number as 3 separate numbers
because Ant doesn't make string subst easy on properties. All the links in the
JDiff reports should work, including the links to the previous and current
Javadocs.
> JDiff report of changes between different versions of Lucene
> ------------------------------------------------------------
>
> Key: LUCENE-1083
> URL: https://issues.apache.org/jira/browse/LUCENE-1083
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Affects Versions: 2.2
> Reporter: Matt Doar
> Attachments: 1083_1.patch, core-jdiff.zip, jdiff_lucene_191_220.zip,
> jdiff_lucene_210_220.zip
>
>
> I think that a helpful addition to the release process for Lucene would be
> [JDiff|http://www.jdiff.org] reports of the API changes between different
> versions. I am attaching reports of the differences between 1.9.1 and 2.2.0
> and also between 2.1.0 and 2.2.0. The reports could be changed to only show
> the public methods. The start page is changes.html.
> This is the Ant target I added to the top-level build.xml file in the JDiff
> directory to produce a report:
> {noformat}
> <target name="lucene" depends="dist">
> <taskdef name="jdiff"
> classname="jdiff.JDiffAntTask"
> classpath="${dist.dir}/antjdiff.jar" />
> <jdiff destdir="${reports.dir}/lucene"
> verbose="on"
> stats="on"
> docchanges="on">
> <old name="1.9.1">
> <dirset dir="${examples.dir}/lucene-1.9.1/src/java" includes="org/**" />
> </old>
> <new name="2.2.0">
> <dirset dir="${examples.dir}/lucene-2.2.0/src/java" includes="org/**" />
> </new>
> </jdiff>
> </target>
> {noformat}
> Disclaimer: I'm the author of JDiff
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
