Is there any specific reason for the update? Any missing feature, solved bug or anything like that? Usually upgrades for the sake to stay on most recent version are not convenient: they tend to break instead to solve...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes there is a reasen: We need Support of the new Excel format so that we can load huge excel files. More than 66000 lines and we get the (testing) data in the new excel format
The patch I've created is an example how you can support both format,s the old and the new one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We really need the support of POI (at least 3.6). In our project (using Maven), we have conflicts between POI 3.6 (needed for xlsx support) and the usage of DBUnit (which use POI 3.2-Final).
Is it possible to have a binary form the DBUnit with the proposed patch of ralfmuehle ?
Thx
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Last DBUnit-release 2.4.8 is more than two years old (2010-09-01). Is this issue still on your list? When will the next version be released? Maybe a 2.4.9-SNAPSHOT or something similar which uses the patch?
We are using Excel 2010 and are very interested to get a new version of db-unit which uses newest version of poi. Building db-unit from source is not a possible way for us. :-(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For anyone that wants this change, please attach a clean patch with only the changes needed to make the latest POI work. There are formatting, spaces-to-tabs, and other non-necessary changes in the attached patch.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SVN Patch for using POI 3.7
Is there any specific reason for the update? Any missing feature, solved bug or anything like that? Usually upgrades for the sake to stay on most recent version are not convenient: they tend to break instead to solve...
Yes there is a reasen: We need Support of the new Excel format so that we can load huge excel files. More than 66000 lines and we get the (testing) data in the new excel format
The patch I've created is an example how you can support both format,s the old and the new one.
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
Last edit: Anonymous 2019-03-19
We really need the support of POI (at least 3.6). In our project (using Maven), we have conflicts between POI 3.6 (needed for xlsx support) and the usage of DBUnit (which use POI 3.2-Final).
Is it possible to have a binary form the DBUnit with the proposed patch of ralfmuehle ?
Thx
Last DBUnit-release 2.4.8 is more than two years old (2010-09-01). Is this issue still on your list? When will the next version be released? Maybe a 2.4.9-SNAPSHOT or something similar which uses the patch?
We are using Excel 2010 and are very interested to get a new version of db-unit which uses newest version of poi. Building db-unit from source is not a possible way for us. :-(
For anyone that wants this change, please attach a clean patch with only the changes needed to make the latest POI work. There are formatting, spaces-to-tabs, and other non-necessary changes in the attached patch.
Mr Jeff Jensen.
Sorry to bother you.
You said "please attach a clean patch with only the changes".
So I did a pull request.
https://sourceforge.net/p/dbunit/code.git/merge-requests/6/
I think this correction is simple sufficiently.
The test is being passed, and a Excel file of the old version can also be read.
Many people are correcting separately to this problem.
(It's Japan mainly.)
A bad custom is spreading.
It's being hoped that I'd like to stop that.
I don't know whether this way is right.
But please take this modification into consideration.
I'm sorry.
I'd like to apologize for a poor English.
Great job Mr. Kazuhito Miura. Your pull request was clean merge and build successful. Thank you.