tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TIKA-191) Using of maven-changes-plugin instead of hand made changes.txt
Date Sun, 08 Feb 2009 12:10:59 GMT

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

Karl Heinz Marbaise updated TIKA-191:
-------------------------------------

    Attachment: TIKA-191-1.patch

The first patch produces a warning as the following: [WARNING] DEPRECATED [issueLinkTemplate]:
As of 2.1 use issueLinkTemplatePerSystem : this one will be with system default
which will be removed by using the second patch instead.

> 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
>            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.


Mime
View raw message