Hi,
I've prepared artifacts for the release of Apache POI 3.15-beta2 (RC1).
The most notable changes in this release are:
- initial work on extracting VBA macros (#52949)
- remove deprecated classes (#59170)
- various X/HSLF fixes for table and color handling
- XSSF: formula evaluation
59743 has been fixed - the other two are open, but I guess it's ok to postpone
them
for Beta3 / Final
I start now with the release workflow - please don't commit changes until the
votes
are over.
Andi
On 22.06.2016 21:48, Javen O'Neal wrote:
> Bugs that we might want to close before 3.15
On 22.06.2016 06:49, Javen O'Neal wrote:
> I can't find the flash drive I put my private key on. Someone else will
> need to be release manager for 3.15 beta 2 unless a miracle happens.
I can roll the release - if it's ok for you, I'd like to propose a release
workflow (... I hope it doesn't
On 19.06.2016 10:35, Dominik Stadler wrote:
> here my results from the regression-tests for 3.15-beta2, I see two newly
> introduced issues that we should take a look at.
I've fixed the mentioned PPT issue already via #59702, but that commit was
after you've started
the integration test. As this
Hi,
On 14.06.2016 20:31, Javen O'Neal wrote:
> If I am, I will happily be release manager.
This is good to hear/read - I'm happy to help you with the releasing as the
scripts probably
still need some tuning, i.e. only the optimistic path (hopefully) works, but as
soon as something needs
to be
Hi,
the UDFFinder interface had a constant (DEFAULT) to one of its subclasses.
I've changed the interface now to an abstract class - this will certainly break
other implementations,
but the fix to switch from "implements" to "extends" seems better compared to a
strange
self-reference.
I hope
Hi,
FYI - I'm trying to make the findbugs version depending on the java version, so
JDK8 should use the new version.
Currently Jenkins (i.e. the main poi job) is configured to the slaves
"ubuntu&&!cloud-slave" - I probably missed it, but why
was windows1 removed?
Andi
FYI - I've opened a ticket for it:
https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11919
Andi
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
Hi Javen,
this is just a quick response, so you don't think this topic is going under ...
I would prefer not to validate the whole file on save - especially as there are
still a few
areas where we can say for sure, if a modification corrupt the file - at least
for HSLF.
Although I can imagine
On 02.05.2016 23:11, Nick Burch wrote:
> On Mon, 2 May 2016, Andreas Beeker wrote:
>> - Jaxb (gpl licensed/not working on android)
>
> Isn't it dual GPL/CDDL 1.1? https://jaxb.java.net/ suggests it is, unless
> that's something else?
>
> Under certain restrictions,
On 24.04.2016 23:59, Nick Burch wrote:
> I think we still need more prototyping to check what is and isn't a viable
> option, before we go voting on things
>
Although we are using Jibx at my $dayjob, I have already problems with basic
schemas [1].
Looking at the answers at stackoverflow [2] or
> However, Jason could always re-license his existing code. (Whether he'd be
> willing to is a different matter!)
I don't think that re-licensing works, as the jaxb base is already GPLed.
Another option would be, to do the same with the MOXy port, but the eclipse
license is also regarded as
I had a look at the Jasons JAXB rebundled code [1], but I guess we aren't
allowed to include GPL2 code,
even as a dependency or do I understand [2] wrong?
So currently it's either JAXB (from the jvm) or some other solution for Android.
Not sure, if it makes sense to call a vote, where we want
Hi *,
I'm still struggling with the jaxb replacement for the xml signing classes.
Apart of spending a lot of time to get namespaces/prefix right (... and it
still doesn't work),
so that the signatures are valid again, I've realized that jaxb in java6 might
be also a problem ...
The reason for
The Apache POI project is pleased to announce the release of POI 3.15-beta1.
Featured are a handful of new areas of functionality, and numerous bug fixes.
See the downloads page for binary and source distributions:
http://poi.apache.org/download.html
Note: The Apache Software Foundation uses an
I've skipped the stagelocally task and when you click the files in the content
tab, you see those going into the root directory ...
I remove those uploaded files now and try the stagelocally task.
Andi
-
To unsubscribe,
Hi,
the upload scripts resulted in the artifacts to be uploaded to the nexus root
directory [1]
Currently I don't see a difference in the artifacts (which I've just uploaded
again) to
the artifacts uploaded via the nexus gui.
Not sure if you see my unreleased packages - but maybe you spot a
This vote has passed with 4x PMC +1 votes.
I release the artifacts now and announce the release on the website,
when I see the files on maven central.
Andi
(posted it twice, to keep it in the 3.15-beta1 vote thread ...)
-
To
This vote has passed with 4x PMC +1 votes.
I release the artifacts now and announce the release on the website,
when I see the files on maven central.
Andi
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For
08:09, Dominik Stadler wrote:
> Hi Andi,
>
> the "beta2" in the filenames/directories looks incorrect, or?
>
> Dominik.
>
> On Sat, Apr 9, 2016 at 11:36 PM, Andreas Beeker <kiwiwi...@apache.org>
> wrote:
>
>> Hi,
>>
>> I've p
Hi,
I've prepared another release candidate with Tims changes:
https://dist.apache.org/repos/dist/dev/poi/3.15-beta2-RC2
I'm not sure how often this error would happen, but I guess its better to be
safe than ...
Andi.
On 08.04.2016 23:58, Allison, Timothy B. wrote:
> I just finished the run.
Hi,
I've prepared artifacts for the release of Apache POI 3.15-beta1 (RC1).
The tag is based on r1737618 (04.04.2016) and doesn't contain commits after
that -
only the changed license file.
The most notable changes in this release are:
- removal of deprecated elements (#59170)
- avoid XmlBeans
On 06.04.2016 01:17, Javen O'Neal wrote:
> If trunk is not open or we need to create a beta 1 RC 2, some svn merging
> will be needed to exclude these post-beta1 commits.
So between the lines you suggest that the changes to the license file are
necessary for beta1.
I don't mind having the old
Hi All,
There are already checkins for beta2 ... how about postponing this
justification to beta2?
I had a discussion with Dominik about what to include in the beta1 and
if I should wait for #58787 to be finished.
As we had some extensive testing for the trunk and #58787 seems to be a bit
Hi,
I'm still fiddling with the release script - and need to try it out, which
leads to already changed version-ids.
Currently pinning the documentation (i.e. svn:externals) doesn't work - please
be patient with me.
Andi.
On 30.03.2016 23:30, Nick Burch wrote:
> I've had a go at adding some
Hi Dominik,
thanks again for running the regression tests.
@issue 1: I've tried to limit the classes to the lite-schemas, but the error
doesn't show up.
My guess is, the toArray fails when the children aren't returned as gd elements
but as xmlanytype [1].
Another wild guess is, I think
I never understood why the default is to write changes to disc.
I'd prefer the default to leave the document unchanged and only write the
changes when commit() is called.
close() should be callable in any case, possibly throwing away any temporary
objects -
and it should be ok, to call it again.
There's a button on the upper right corner on the individual builds. [1]
[1]
http://jenkins-ci.361315.n4.nabble.com/How-to-mark-builds-quot-keep-forever-td381135.html
On 27.03.2016 15:14, Javen O'Neal wrote:
> How do you pin a build on Jenkins? I didn't find such a link when logged in.
>
> On
On 18.03.2016 03:36, Javen O'Neal wrote:
> >From bug 59194, https://bz.apache.org/bugzilla/show_bug.cgi?id=59194
>
> If we want to make POI be compatible with Google App Engine, should we add
> java.awt.* to the forbidden API's list?
>
If you do, you need to add a separate ant task excluding
Hi,
first of all, thank you for your comments.
TL;DR: I put it on hold.
> However also Gradle has quite a learning curve, ...
I've checked their quick start for the first time ... probably I'm unaware of
Gradle as I'm not an android developer,
and only a maven user of spring(/hibernate)/...
Hi,
I'd keen to switch our ant build to a modulized maven build.
I guess there were already several discussions about this topic,
but I couldn't find them on a quick view.
Most of the work has been already done by Dominik in the sonar builds,
so I hope it's not too time consuming to change.
I
Hi Nick,
please add the 3.14 version to our bugzilla.
Thank you,
Andi
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
The Apache POI project is pleased to announce the release of POI 3.14.
Featured are a handful of new areas of functionality, and numerous bug fixes.
See the downloads page for binary and source distributions:
http://poi.apache.org/download.html
Release Notes
Changes
The most
This vote has passed with 4x PMC +1 votes.
I'll release the artifacts on Sunday evening and
announce the release on the website, when I see the files on maven central.
the new proposed notable changelog is: ...
Common: OPC relation fix for multiple same named ids (#54916)
Common: Update
Hi PMCs,
up till now we only have two PMC +1 votes for the next final,
but we need at least three +1 votes for the final to pass -
the voting ends tonight, 23:59 UTC.
After the votes have passed I will post an updated version of the
notable changes, to be included in the general announcement.
Hi,
I've prepared artifacts for the release of Apache POI 3.14-final (RC1).
The most notable changes in this release are:
- various HSLF parsing and rendering fixes
- WMF parsing and rendering
- OPC relation fix for multiple same named ids (#54916)
- various XWPF fixes for handling paragraphs
Hi,
I've fixed the ppt-based NPE and start now with the release preparations.
As usual, if there are any late-time fixes, I can still roll a RC2 ...
Andi
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For
Hi,
I've applied the x/hslf/wmf regression fixes.
There are still a lot of rendering problems - especially with hslf - but I'd
like to push the release soon.
Which order do you prefer - first common-crawl regression testing and then
releasing
or test the release candidate on common-crawl?
> * The OutOfMemory failures are likely false-positives as I run with fairly
> small memory settings to avoid blowing up on the small machine where I run
> these
>
> Thanks... Dominik
>
>
> On Thu, Feb 11, 2016 at 11:58 PM, Andreas Beeker <kiwiwi...@apache.or
If no-one objects, I'll roll the final release on next Saturday.
Andi
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
So it seems we will have a final soon.
Who is playing release manager? Javen?
if yes, please announce when you'll have time for the release.
Andi.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional
Hi Javen,
I've already thought about writing to the dev list when I've read your comments
on bug 58787.
And now that you've mentioned common sl, I think I need to give my two pence ...
With common sl I also had to made that decision of going the *ssf way or having
base classes (e.g. for
> What is the current preference among the POI committers and community?
Receiving a patch:
I haven't checked how to receive the git pull requests as I'm not having a
local POI git repository -
so this is currently my least preferred format.
Apart of that, I don't care if approach 1 or 2 is used
Hi Dominik,
I'd like to have the X/HSLF files, so a few of the first 280ies and the NPE.
Thank you for your efforts!
Andi.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail:
Hi,
I've created a IRC channel for POI (#apache-poi) on chat.freenode.org
I'm usually around from 22:00 to 01:00 CET ...
Folks can log on and share ideas/help/suggestions.
Please note, the channel is not a place to make any official decisions
regarding POI.
It's simply another option for
Hi Tim,
sorry for dropping on that issue ... I've seen the Jira-Issue but somehow
forgot about it.
I've renamed the vendor specific packages with #58617, so they fit better to
the visio
resources.
Please try adding the following to tika-bundle\pom.xml:
Hi,
I'd like to ask one of the PMCs to review my patch for #54916.
The reason is, that it affects not only XSLF, but all OOXML modules and it's
kind of a base change.
For more information, have a look at the bugzilla entry.
As I'll be on a hang gliding trip from 01-10.01.16, I might not have
+1 from me
When this is out, I'd like to ask someone (of the PMCs) to review #54916
Andi
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
Hi Tim,
please validate the trunk against the ppts of the gov docs again.
If this works, we can decide if we want to push the existing 3.14-Beta1 release
or repack a new one.
Sorry for the inconvenience and thank you for your tests.
Andi.
Here is my +1
... and my 2 cents:
- most notable section is a bit short, for so many changes (... but I'm also
always puzzled what to mention and what to skip)
please add a note about the changed ooxml-schemas (#58617)
not sure if it makes sense to mention, that the deprecation on array
Hi,
is there someone preparing the next release? David? Javen?
... otherwise I would be overjoyed to do it again ;)
Andi
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail:
e the damage to other files
Nick fixed it in r1715845
https://svn.apache.org/viewvc/poi/site/publish/apidocs/org/apache/poi/ss/util/class-use/CellAddress.html?view=log
On Sun, Nov 29, 2015 at 6:47 AM, Andreas Beeker <kiwiwi...@apache.org> wrote:
> Hi David,
>
> in case you'll sta
Hi David,
in case you'll start with the beta preparation soon, please leave an one-liner
here,
with the time you begin, so we stop committing stuff by then.
Apart of that, feel free to begin with the releasing.
> I'm still happy to do so if that's acceptable to everyone?
One thing, which took
Hi,
about 5-6 days ago, I just wanted to fix a few unnecessary cast, but now I'm in
the middle
of cell formatting hell :)
Would it be ok, if DataFormatter delegates much of its logic to the
org.apache.poi.ss.format
classes?
Currently, I'm struggling with CellNumberFormatter and noticed that
Hi,
this is partly a follow up to [1] and [2] - and sorry in advance to bring this
up again,
but I feel we are too conservative.
Summary:
When we introduce new methods/enums/classes/... we try to be compile compatible
with older versions.
After two releases the deprecated stuff can be removed.
Hi,
I've added the windows slave(s) again to the Jenkins build config ... maybe the
build problem is fixed there now.
Don't wonder if the build suddenly stop working, as this was the reason for
disabling the windows slaves.
Andi
Hi,
> Nick proposed we should have an ooxml-schemas-1.2 JAR containing visio,
> security & main, rather than three separate artefacts. But keep the
> existing lightweight one too. All agreed this made sense. ACTION:
> Someone to implement this.
As this seems to be shortly before done - and the
Hi,
I've limited the POI job now to ubuntu (before it was "ubuntu || windows1").
Apart from the longer builds, it seems there are some svn problems on windows1.
Andi.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For
The Apache POI project is pleased to announce the release of POI 3.13.
Featured are a handful of new areas of functionality, and numerous bug fixes.
See the downloads page for binary and source distributions:
http://poi.apache.org/download.html
Note: The Apache Software Foundation uses an
I'll remove it with the next commit.
3.13 (including HDF) is already out in the wild - as the release guide says +7
days (-> 29.09.2015) for the release timestamp, I'll make the announcement
tonight.
Andi.
On 28.09.2015 16:55, Nick Burch wrote:
> On Mon, 28 Sep 2015, Andreas Beeker
Hi,
although I hardly do anything in the x/hwpf package and therefore don't know
the connections,
would it be ok, if I finally remove the hdf packages (and update the docs[1])?
I have already removed those legacy classes locally and the tests are still ok.
Andi
[1]
Hi Nick / Dominik,
please update the javadocs for 3.13 again.
I've used the unofficial windows openjdk 1.7 and it shuffles the javadocs, too.
Thank you ... and have fun at the con.
Andi.
On 10.08.2015 10:39, Dominik Stadler wrote:
> Ok, yes, with openjdk-7 I get very similar results to
This vote has passed with 4x PMC and 1x soon-to-be-PMC :) +1 votes.
I'm now releasing the maven artifacts and check for the other
after-voting-todos.
I'll announce the release on the website, when I see the files on maven central.
Andi.
Hi,
I've prepared artifacts for the release of Apache POI 3.13-final (RC1).
The most notable changes in this release are:
- conditional formatting support for DataBars, Icon Sets / Multi-States, and
Color Scales
- various improvements in spreadsheets formula and cell reference handling
-
On 21.09.2015 18:54, Nick Burch wrote:
> On 19/09/15 21:21, Dominik Stadler wrote:
>> Sounds good to me! Maybe we should do a 3.13 soon as well before
>> starting to add the Visio stuff as that wpuld likely delay things some
>> more ...
>
> One option might be to aim to release 3.13 final and 3.14
I'll apply a few SL changes tonight, and then create the release candidate
tomorrow evening.
Andi.
On 19.09.2015 22:21, Dominik Stadler wrote:
> Sounds good to me! Maybe we should do a 3.13 soon as well before
> starting to add the Visio stuff as that wpuld likely delay things some
> more ...
Hi,
originally I wanted to check in the forbidden api changes already yesterday,
but I've decided to also check how it reacts when I use an arbitrary timezone
(PST)
and locale setting (RU).
Currently I'm checking why there seems to be a link between
Hi,
I have a lot of test errors and already fixed quite a lot, but haven't
committed them yet.
Short version:
how about ... instead of using Locale.ROOT and Timezone UTC,
the initial value of the ThreadLocal return Locale.getDefault() and
Timezone.getDefault()
and can be set if needed ... so
Hi,
in the code we have some places where we reset the default time zone [1], like
the following:
TimeZone cet = TimeZone.getTimeZone("Europe/Copenhagen");
TimeZone.setDefault(cet);
Although this is just in a junit test, I don't think it's a good idea to set
the jdk default.
Hello Teressa,
What I like to do is to extract texts from a textshape and if a text is
bullet style, I'd like to add a bullet with a proper nested indentation. For
example, on slide 2 in the enclosed ppt file,
have a look at [1] ... is this was you are looking for?
As I've changed a few
On 15.08.2015 19:59, Nick Burch wrote:
Any chance you could point us to a couple of examples? Might help with
evaluating if we feel it's a real problem or not
Just open the findbugs page and navigate to the type named in the thread subject
or use [1] for the last build.
-
Hi,
we have several cases of NM_SAME_SIMPLE_NAME_AS_SUPERCLASS in the
findbugs reports and as the description says, this is confusing
(a) A few classes just delegate to their same named parent.
and (b) and others add a bit of extra logic to.
I'd like to remove (a) and replace the import with the
Hi Nick,
I'm currently adapting #58190 - the idea of the bug will remain, but the
implementation
is actually different to the patch provided.
Furthermore I haven't provided Tika with the patches yet.
So I would prefer to wait a bit longer.
Andi
Hi Teresa,
the new common_sl code was committed after I've pushed the 3.13 beta1 release,
so it's living only on the trunk for now.
If a text is in one of styles (italics, bold, etc), then it gets splits and
very difficult to put them together into a same bullet statement.
When a x/hslf
Hi,
as you've might noticed, I've applied the common_sl branch/changes to the trunk
now.
I'm now looking over the documentation and fix it where needed.
I haven't written a migration guide yet ... this is still a todo on my list.
Andi.
The Apache POI project is pleased to announce the release of POI 3.13-beta1.
Featured are a handful of new areas of functionality, and numerous bug fixes.
See the downloads page for binary and source distributions:
http://poi.apache.org/download.html
Note: The Apache Software Foundation uses an
Hi Nick / Dominik,
I'm having problems with the javadocs website update, there are again a lot of
differences (line breaks and others).
Would you please generate the javadocs for the 3.13-beta1 tag on your linux box
and commit them.
I'm currently generating/updating the other docs, so javadocs
This vote has passed with 3 +1 votes.
I'm now releasing the maven artifacts and check for the other
after-voting-todos.
I'll announce the release on the website, when I see the files on maven central.
Andi.
-
To unsubscribe,
Hi Dominik,
Let me know if you run into a huge number of merge-conflicts
yes, I ran into them ... I spent quite some time to find out how to do it via
eclipse,
but finally did it via the console. The problem was, that I've never merged
the trunk into my branch and so it accumulated since
Hi,
I'm starting to merge the common sl branch to the trunk.
It probably takes a while for the first commit, but I think it's in a shape to
be merged.
There will be quite a few api-breaks, but this is natural, as the XSLF and HSLF
differ a
lot in certain areas ... and I either don't want to
Hi Mark,
my guess is, that's a xmlbeans/classloading issue too.
I would try the following:
- replace the poi-ooxml-schemas with the ooxml-schemas [1]
- check how the netbeans classloading mechanism is working
and try to put the libs in a different context. Maybe temporarily
try the libs
I'm starting now the release preparations ...
Andi
On 15.07.2015 15:22, Dominik Stadler wrote:
Ready for beta1 from my side!
The build-failures from Jenkins for POI-OpenJDK are not a problem, I
am trying to get this build running on a freebsd machine which
prevents downloading some
It looks like the regression is solved ;)
May I start with the next beta release?
Andi
On 10.07.2015 06:42, Dominik Stadler wrote:
Fine by me, there is one regression bug that I would like to include, a
NullPointerException, but that should be an easy fix, I'll try to put it in
over the
Hi Nick,
although I haven't worked much in the trunk lately, I'm +1 for pushing the zip
stuff ... and I would play the release manager again, if it's ok for you guys
(... after the last release desaster )
Andi
Hi again,
I don't think any users actually use POILogger in their code,or?
Timewise in parallel I thought the same and applied the patch.
e.g. by stating that after 2 releases in deprecated state we can remove
things for good.
+1
Regarding slf4j, we could also look at commons-logging
at my
Hmmm ... ... newsheet.class ... vs. ... netsheet ...
I'll buy a t instead of a w
fast reply is appreciated...
I've received your mail just now - so it was sleeping in some outbox for the
last 1,5 days ...
Andi.
On 20.06.2015 16:22, rkishore.qa wrote:
Hi experts,
I
Hi,
I've just changed something in POILogger for #58040 and additionally refactored
the various methods to a varags method.
This works when code gets compiled but fails if only the binary is replaced.
What is our guideline regarding ...?
- binary compatibility
- deprecated objects, i.e.
I'm stuck with the slide rendering code in the common_sl branch.
it seems that I solved this issues ... XSLF seems to be rendered differently
than HSLF,
when it comes to group rotations. I guess the next rendering difference is not
very far away ...
Andi
Hi,
I'm stuck with the slide rendering code in the common_sl branch.
Would be cool, if you have a look at
org.apache.poi.hslf.usermodel.TestPicture.bug54541().
There are 4 different test files which contain rotated shape groups.
In the org.apache.poi.sl.draw.DrawShape.applyTransform method, you
Thank you, David and Tim.
Before I ask you to go a bit more into detail, I wanted to add a few of my
motivation points -
everything is minor and I can live without it, but when choosing between
wildcards and full import,
I tend towards wildcards:
- when writing junit4 test, every time I use a
On 28.05.2015 21:36, Allison, Timothy B. wrote:
4) don't use wildcards on imports
This is something I'd like to change.
Can we limit this to X classes per package or X static imports?
For common_sl, I've used a setting of 3 full imports, and for a higher number
wildcards will be used.
The
Ideally we should have the core classes/interfaces in the main jar, so that
the ooxml classes can work without scratchpad. I'd say it's fine for
scratchpad to depend on core, ooxml to depend on core, not sure about ooxml
(nominally stable) depending on scratchpad (nominally not)
What does
Hi,
the site updates result in quite a lot of differences when I update them on my
Windows box
using jdk 1.7.0_72.
I've noticed two issues:
- javadocs are not always ordered the same way
- linebreak differences
For the the javadocs I've already changed the svn properties to linux-only (lf)
The Apache POI project is pleased to announce the release of POI 3.12.
Featured are a handful of new areas of functionality, and numerous bug fixes.
See the downloads page for binary and source distributions:
http://poi.apache.org/download.html
Note: The Apache Software Foundation uses an
This vote has passed with 3 +1 votes.
I'm now releasing the maven artifacts and check for the other
after-voting-todos.
I'll announce the release on the website, when I see the files on maven central.
Andi.
-
To unsubscribe,
Hi,
here is the 3rd release candidate, which is accessible under:
https://dist.apache.org/repos/dist/dev/poi/3.12-final-rc3/
The most notable changes in this release are:
* remove limitations within XSSF - up to 64k cell styles (#57880) and 65k
comments (#56380)
* fixed XSSF cloning issues -
On 08.05.2015 15:47, Nick Burch wrote:
On Fri, 8 May 2015, kiwiwings wrote:
With my slow DSL, I've started to wonder anyway if we really need (to
upload/provide) those src archives. If someone wants to get involved, they
should fetch the trunk from the svn.
We're an open source project, so
Hi,
here is the 2nd release candidate, which is accessible under:
https://dist.apache.org/repos/dist/dev/poi/3.12-final-rc2/
This release has been built based on the same SVN revision as RC1.
The most notable changes in this release are:
* remove limitations within XSSF - up to 64k cell
Hi,
every now and then I have an idea what would be a nice add-on for POI,
but I don't want to spam the bugzilla nor the dev list with unfinished ideas.
So maybe you want to have a look at http://people.apache.org/~kiwiwings/
In case something sounds interesting to you, I'd be more than happy
Hi,
I prepared artifacts for the release of Apache POI 3.12-final (RC1).
The most notable changes in this release are:
* remove limitations within XSSF - up to 64k cell styles (#57880) and 65k
comments (#56380)
* fixed XSSF cloning issues - for sheets (#57165), styles (#56295), pictures
501 - 600 of 673 matches
Mail list logo
