Mailing-List: contact dev-help@poi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "POI Developers List" <dev@poi.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-Id: <D4536809-ED01-48E8-BBF7-5DA7B22DBBBD@jmlafferty.com>
From: David Fisher <dfisher@jmlafferty.com>
To: "POI Developers List" <dev@poi.apache.org>
In-Reply-To: <4675731.1240954403673.JavaMail.root@cps8>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: 3.5 final compatible with current 3.2 release?
Date: Tue, 28 Apr 2009 15:11:04 -0700
References: <4675731.1240954403673.JavaMail.root@cps8>

Pedro -

Nick said -

> all you should need to do is recompile your application

If this means that you need to recompile JasperReports, then isn't  
this something that you can do?

BTW - POI 3.2-FINAL is the most recent final - 3.5 FINAL does not yet  
exist.

> Does that mean that jar files like JasperReports will have to  
> provide a 3.5 compatible jar and a 3.2 compatible jar?
> Why not having a transition period having both APIs?

If this means that we need to communicate with JasperReports about  
this before we go to POI 3.5-FINAL we might consider doing so, but the  
rest of your questions are not going to get us anywhere - there are  
many reasons to have a Java OOXML implementation.

If you have success with POI 3.5 after re-compiling JasperReports then  
please let us know - it will help.

Regards,
Dave

On Apr 28, 2009, at 2:33 PM, pedrofaundezgon@terra.es wrote:

> nick@fluffy.internal.torchbox.com wrote:
>> On Mon, 27 Apr 2009, pedrofaundezgon@terra.es wrote:
>>> Will POI 3.5 final API be compatible with current POI 3.2?
>>
>> The aim is for it to be source compatible, but not always binary
>> compatible.
>>
>> (See http://poi.apache.org/spreadsheet/converting.html for how to  
>> convert
>> existing hssf code into the generic ss code, but if you just want  
>> to stick
>> with hssf, all you should need to do is recompile your application)
>
> Does that mean that jar files like JasperReports will have to  
> provide a 3.5 compatible jar and a 3.2 compatible jar?
> Why not having a transition period having both APIs? Who decided to  
> deprecate the current API and go for a new one just in one release?
>
> I understand that Microsoft want to undermine every Java software  
> and to implement their badly designed file formats, but there are  
> other office packages like OpenOffice that can read XLS and do not  
> need the pointless OOXML.
>
> Will Microsoft also implement OpenDocument Spreadsheet?
> Should we force OpenDocument to be implemented to allow Microsoft  
> include their pointless and badly designed OOXML?
>
>
>
>
>
>
> Ahora tambi&eacute;n puedes acceder a tu correo Terra desde el  
> m&oacute;vil.
>
> Inf&oacute;rmate pinchando aqu&iacute;.
>
>
>
>
>


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