Mailing-List: contact dev-help@poi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "POI Developers List" <dev@poi.apache.org>
Received-SPF: pass (athena.apache.org: domain of nick.burch@alfresco.com
 designates 88.151.129.23 as permitted sender)
Date: Thu, 17 Jun 2010 19:02:55 +0100 (BST)
From: Nick Burch <nick.burch@alfresco.com>
To: POI Developers List <dev@poi.apache.org>
Subject: Re: [VOTE] Release POI 3.7 beta 1 (20100620)
In-Reply-To: <AANLkTikOLciIhjhnqgfnhpOuchE7c09zrGsNa424G1IR@mail.gmail.com>
Message-ID: <alpine.DEB.1.10.1006171900100.17098@urchin.earth.li>
References: <alpine.DEB.1.10.1006151252470.6733@urchin.earth.li>
 <AANLkTikOLciIhjhnqgfnhpOuchE7c09zrGsNa424G1IR@mail.gmail.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Thu, 17 Jun 2010, Jukka Zitting wrote:
> Works great with Tika, though I'll note that due to the already tight 
> POI integration in Tika the version upgrade requires quite a few code 
> changes in Tika. I think it would be useful for POI to specify a set of 
> APIs that are guaranteed to remain backwards-compatible over minor 
> version upgrades.

IIRC, the only changes needed should be in the scratchpad for HSMF. (Patch 
for that in Jira). In general, anything in the scratchpad is subject to 
change its API, as we normally still need to do major work to implement 
funcationality. Stuff in the main jar should be compatible (or largely so) 
between releases

Was there a change needed for things other than HSMF?

(FWIW, if you apply all the patches from me currently pending in Tika's 
jira, it ought to compile just fine against the release candidate jars, as 
I did a custom tika build using them earlier this week)

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org