[ 
https://issues.apache.org/jira/browse/TIKA-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jukka Zitting resolved TIKA-191.
--------------------------------

    Resolution: Won't Fix
      Assignee: Jukka Zitting

I think the current CHANGES.txt approach together with Jira reports works 
pretty well. So resolving this as Won't Fix.

> Using of maven-changes-plugin instead of hand made changes.txt
> --------------------------------------------------------------
>
>                 Key: TIKA-191
>                 URL: https://issues.apache.org/jira/browse/TIKA-191
>             Project: Tika
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 0.3
>         Environment: All
>            Reporter: Karl Heinz Marbaise
>            Assignee: Jukka Zitting
>            Priority: Trivial
>         Attachments: TIKA-191-1.patch, TIKA-191.patch
>
>
> Suggestion would be to use the maven-changes-plugin to product a change list 
> in relationship to the distributed releases and the current snapshot release 
> as part of the generated site. So it's part of the project reports and give 
> good overview of the made changes etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to