On Fri, 3 Jun 2016, Mark Murphy wrote:
Where can I find that. I searched for the 58779 bug, but there is no
test that references it. Sorry, not really fully up to speed on the
entire project yet.
I added a disabled "word read-only file to new stream" test last week,
it's
On Tue, 7 Jun 2016, Shivakumar e wrote:
For XLSX i used OPCPackage it solved the problem.but now i am facing
problem with XLS format.
When i use normal POI like POIFSFileSystem to read files. i am getting java
heap space error.
Use a new copy of POI, and open the POIFS with a File not an
On Thu, 2 Jun 2016, Murphy, Mark wrote:
Read Only doesn't work in XWPF, it won't let me write to any file.
Plenty of bugs to go around.
Hmm, that's bad, it ought to! Maybe add a quick disabled unit test for
that (along the lines of the one we have for XSSF), and maybe also a XSLF
one too
On Thu, 2 Jun 2016, Murphy, Mark wrote:
Does that not cause a memory leak in Closeable objects?
We need to fix the underlying bug really! For now, you can open the
package Read Only to avoid it, or wait for GC to clear out the closable
object a bit later
Nick
On Wed, 1 Jun 2016, Murphy, Mark wrote:
Then write to a different file:
FileOutputStream out = new FileOutputStream(new File(
"createdocument.docx"));
document.write(out);
out.close();
document.close();
There's an issue with close and things opened from files with X??F, I'd
On Wed, 1 Jun 2016, Murphy, Mark wrote:
Is there a main developer for XWPF?
Nope!
On Wed, 1 Jun 2016, Murphy, Mark wrote:
Do you use the stuff in the wp package, or was that simply
experimentation?
It wasn't common enough to be able to swap the Tika stuff onto it, so no.
I'd like to for
On Wed, 1 Jun 2016, Murphy, Mark wrote:
At work I have been using the SS side of POI, and have become fairly
comfortable with it. I realize that there are some things still that
need to be done, and some issues with XML Beans that have been
discussed, but it seems fairly well organized.
On Tue, 3 May 2016, Jason Harrop wrote:
I'm pretty relaxed about the license; whatever is compatible with the
original license and makes sense for ASL v2 code bases, and on Android
...
Thanks!
In any case, anyone could follow the recipe in the blog post to redo it.
It might be worth
On Mon, 2 May 2016, Andreas Beeker wrote:
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
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, CDDL can be used:
http://www.apache.org/legal/resolved.html#category-b
Nick
On Sun, 24 Apr 2016, Andreas Beeker wrote:
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?
Apart from a few special cases (build tools, testing resources, completely
optional plugins),
On Mon, 4 Apr 2016, Javen O'Neal wrote:
Also, do we need to add bouncy castle, jaxb, or any other 3rd party libs to
our LICENSE or NOTICE file?
Depends on the license that they're under
Best resources for looking up what needs what is a mixture of
http://www.apache.org/legal/resolved.html
On Thu, 31 Mar 2016, Murphy, Mark wrote:
If you have any questions or comments, I would love to hear your
feedback.
I haven't looked at this patch of yours. However...
Several small patches are easier to review and apply than one big, for
un-related fixes or improvements. However, one big
On Wed, 30 Mar 2016, Allison, Timothy B. wrote:
I added a new report "mime_diffs_A_to_B_details.xlsx", which I'll send
to you privately shortly. I can share this if anyone wants it, and it
will be included in all future report dumps.
Checking a few from there, I think the detection as only
On Wed, 30 Mar 2016, kiwiwings wrote:
This time I think about ant-scripting the svn changes, e.g. un-/pinning of
the docs, creating the branch, uploading the artifacts.
I'd like to have something like:
- ant release-beta
- ant release-final
I've had a go at adding some things for this in
On Wed, 30 Mar 2016, kiwiwings wrote:
Maybe I should spent some time to script more of the manual work ... -
as we use Jenkins here at my $dayjob, I'm used to (nearly)
one-click-releasing the artifacts - I guess something like this would be
possible with Ant too ...
My vague recollection is
On Wed, 30 Mar 2016, Allison, Timothy B. wrote:
The only differences in exceptions were caused by Tika now identifying
several files as xlsx vs zip or ooxml...which I can't explain.
I did some work on improving exceptions in 3.14 for POIFS given non-POIFS
stuff, and since then on OPCPackage
On Wed, 30 Mar 2016, Dominik Stadler wrote:
I'm generally in favor of more releases to reduce the amount of time that
people need to wait for fixes, our unit-tests and other ways of testing
should catch the majority of problems quickly nowadays and if the next
release is coming up soon anyway, a
Hi All
I know it's not been very long at all since 3.14, but we've fixed a decent
number of bugs already, including one for which Tika is awaiting a fix
(TIKA-1836).
What do people think about doing a beta release in a few weeks time, to
get those fixes out to our users? I figure we might
On Tue, 22 Mar 2016, Javen O'Neal wrote:
There appears to be a problem with the configuration of jenkins-test-93.
Is there a way to fix this worker or blacklist it?
If you drop a note to builds@, they can either help you blacklist it, or
help get it fixed
Nick
On Sat, 12 Mar 2016, Mark Murphy wrote:
My new class org.apache.poi.ss.util.CellBorders has some private methods
that respond to a subset of enum values being passed in. If the methods
were private, I would throw an exception if an invalid enum value was
passed, but since the methods are
On Thu, 10 Mar 2016, Dominik Stadler wrote:
Here a few initial ideas where we could improve this:
1. Add some CI to the Github project so that PRs are automatically verified
I think some other Apache projects already do something like this. Maybe
ask on dev@community
2. Move to Git/Github
On Thu, 10 Mar 2016, Andreas Beeker wrote:
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)/... - at least it seems to grow
On Wed, 9 Mar 2016, Andreas Beeker wrote:
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.
IIRC, the stuff for building the ooxml-lite jars was felt to be one bit
which'd be
On Mon, 7 Mar 2016, Andreas Beeker wrote:
please add the 3.14 version to our bugzilla.
I've added 3.14-FINAL and 3.15-dev
I've also stopped 3.13-dev, 3.9-FINAL and 3.10-FINAL from being used for
new bugs. (Old bugs raised against them will keep that, it's just that new
bugs can't pick them)
On Sun, 6 Mar 2016, Andreas Beeker wrote:
The schema updates were already in POI 3.14-beta1 ... therefore I omit the
following:
Excel: New version of ooxml-schema and ooxml-security jars to incorporate newer
code
Since not everyone tracks our betas, and it's a noticable change, I'd
suggest
On Mon, 25 Jan 2016, edwgiz wrote:
GitHub user edwgiz opened a pull request:
https://github.com/apache/poi/pull/28
Extends parsing for old-format Excel files
Has anyone else had a chance to look at this? Seems very interesting to
me, and has unit tests, which is good!
Could someone
On Sat, 27 Feb 2016, Dominik Stadler wrote:
I also tried to add the widget to the "contribute" section on our landing
page poi.a.o, but I couldn't find a way to convince Apache Forrest to
verbatim include the piece of HTML from
https://helpwanted.apache.org/wtest.html
This should now be sorted
Hi All
For those who haven't heard the announcement, a week or two ago the Apache
Community Development project[1] launched "Help Wanted"
https://helpwanted.apache.org/
The idea is to make it easy to match up people interested in contributing
somewhere to Apache, to projects that
On Fri, 19 Feb 2016, nos...@kaigrabfelder.de wrote:
I'm wondering if there are any activities or plans for replacing
xmlbeans with something else. I'm asking a) because the xmlbeans is
retired and b) it has some issues in regards to memory usage and more
important scalability.
Projects can
On Thu, 4 Feb 2016, Javen O'Neal wrote:
I didn't get any responses to a keysigning party email, so I'm still out
of the Apache web of trust. I need to reach out to the kind folks at
[1], but in the mean time, someone else gets to do the *π* release.
Pesky, you could always send a follow-up
On Wed, 3 Feb 2016, kiwiwings wrote:
I'm currently digging in the JAXB support for the document signing and
this will have an impact on the security schemas, size-wise for the
security stuff it will be something like 1.9mb (old version) vs. 100kb
(new version) So either we decide to have the
Hi All
It's been well over month since we released 3.14 beta 1, and from looking
at the changelog we've had some interesting new features (plus bug fixes)
since then. We've also got at least one user, based on bugzilla today,
wanting to try those out in a proper release!
So, what do we all
On Mon, 18 Jan 2016, Javen O'Neal wrote:
There are certainly some good cases for having Util classes, but
sometimes the best thing is to have the functionality right in the
class. The problem is there is no place to put code that would be used
by all implementing classes besides a utility.
On Sat, 16 Jan 2016, Andreas Beeker wrote:
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.
In the
On Mon, 4 Jan 2016, Allison, Timothy B. wrote:
Over on TIKA-1730 [0], we have a request to hide formatting info from
header/footer records for both xls and xlsx during text extraction.
When I look at the text from FooterCell's getText(), it looks like we
may want to add some parsing of the
On Fri, 8 Jan 2016, Dominik Stadler wrote:
I think something went wrong, see
https://poi.apache.org/apidocs/org/apache/poi/hslf/record/TextSpecInfoRun.html
Sorry! Hopefully looks better now?
Nick
-
To unsubscribe, e-mail:
On Tue, 29 Dec 2015, Uwe Friedel wrote:
Exception in thread "main"
org.apache.poi.openxml4j.exceptions.OpenXML4JRuntimeException: Rule M2.4
exception : this error should NEVER happen, if so please send a mail to the
developers team, thanks !
You seem to be using an older version of Apache POI
On Wed, 23 Dec 2015, Javen O'Neal wrote:
Oracle released Java 6 in 2006, ended support for Java 6 in 2013 and
released Java 7 in 2011 and ended support in 2015. Java 8 was released
in 2014.
Many of our users work for big conservative organisations, who'd much
rather throw money at a vendor
On Wed, 16 Dec 2015, David North wrote:
Artefacts for review:
https://dist.apache.org/repos/dist/dev/poi/3.14-BETA1-RC2/
Signatures and hashes look correct, contents of the archives looks right,
so I'm +1 on the release
One special thing for this time though - once the release is out we
On Wed, 16 Dec 2015, David North wrote:
Please can sombody identify the commits we want to port?
I'd suggest you just roll 3.14 beta 1 RC2 from trunk as-is, no need for a
special branch
Nick
-
To unsubscribe, e-mail:
On Tue, 8 Dec 2015, David North wrote:
- where are the maven artifacts?
We normally upload these into a /maven/ subdirectory in the
dist-dev, for people to check, then upload into Nexus + delete
before moving the binary + source releases to the main dev area.
Might need an update for the
On Tue, 8 Dec 2015, Andreas Beeker wrote:
... 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)
It's always a tough call, and a manual process, just needs to be anything
you think counts as major in
On Thu, 3 Dec 2015, Javen O'Neal wrote:
Does releasing require having a community-trusted PGP key? I haven't
outside the Apache web-of-trust (for now).
Ideally a key in the Apache WoT, but one well into an alternate WoT (eg
Debian) could work. If you let me know off-list where in the World
On Fri, 4 Dec 2015, Javen O'Neal wrote:
In FunctionEval.java [1], there's an array that maps the binary function
code used in BIFF8 to a function instance.
There's also
src/resources/main/org/apache/poi/ss/formula/function/functionMetadata.txt
I'm implementing Days [2] for bug 58468 [3],
On Fri, 4 Dec 2015, Javen O'Neal wrote:
From what I can tell, DAYS wasn't added until Excel 2013 [1]. Clearly
this means DAYS is not a recognized function in BIFF8. I developed a
solution [2] for saving unregistered functions in bug 58452, but this
gets tricky with common SS support regarding
On Mon, 30 Nov 2015, Javen O'Neal wrote:
Probably before 3.14b1, we'll want to update
* http://poi.apache.org/overview.html#components
* Bugzilla component for product=POI
for Common SL support
Both done!
For some reason when I generate javadocs on my computer, nearly every
file changes. The
On Mon, 30 Nov 2015, Javen O'Neal wrote:
On Nov 30, 2015 11:51 AM, "Nick Burch"
For the JavaDocs, it isn't the ant version nor the forrest version that
matters, only that of the JDK (and hence that of the javadoc tool)
I'm using Oracle JDK 8 on Linux x64. Are you using OpenJDK/Iced
On 27/11/15 00:53, Andreas Beeker wrote:
Would it be ok, if DataFormatter delegates much of its logic to the
org.apache.poi.ss.format
classes?
I actually ended up doing that for one case a month or so back! You
should notice a TODO at the top of both DataFormatter and CellFormat
saying they
On Fri, 27 Nov 2015, Javen O'Neal wrote:
When running "ant compile", "ant test-ooxml", or "ant test", I notice
that ant rebuilds the "compile-ooxml-xsds" target every time. Do the
ooxml-schemas-1.3.jar and ooxml-security-1.1.jar need to be rebuilt each
time I run test?
There should be an
Hi All
This may be old news for some of you, in which case you can skip the
email, but for others... StackOverflow is a programming-focused question
and answer site, with excellent google-foo, quite wide use, and growing
use. At the moment I'd say there's something like 4 new POI questions a
On Wed, 18 Nov 2015, Azfar Kazmi wrote:
I have attached a unit test and ppt file that it uses.
Any chance you could open a bug in bugzilla, and attach both their? The
mailing list tends to eat attachments is one issue, forgetting about
issues not in bugzilla is another...!
Thanks
Nick
On Tue, 17 Nov 2015, Azfar Kazmi wrote:
I am using 3.13 and noticed that SpecialPropertySet now uses hard coded
ASCII charset when it creates a new String out of byte[]. This change
was introduced in September by revision 1700677.
That was as part of the "forbidden APIs" cleanup, to get POI
On Tue, 10 Nov 2015, Jon Iles wrote:
I've been advised that one change which was made between 3.12 and 3.13
was the move from OPOIFS to NPOIFS. I'm not familiar with the internals
of POI, and I'm wondering if it is possible to switch between these two
implementations in 3.13 to see if this
On Thu, 29 Oct 2015, David North wrote:
In the 3.13 release, we had:
poi-ooxml-schemas-3.13-20150929.jar at 5.4MB. This is the 'lite' JAR
recommended for normal use, containing relevant parts of all supported
formats + security.
Which isn't quite so lite as it once was... But yes!
And if
On Mon, 26 Oct 2015, David North wrote:
How do I obtain powers to close request
https://github.com/apache/poi/pull/24, given that I've put it into SVN?
Currently, you can't directly, see discussion on the infrastructure@ and
infrastructure-dev@ lists for details on the on-going work to get
On Fri, 16 Oct 2015, David North wrote:
So, questions...
Where is the documentation on how to produce/sign a release package?
https://svn.apache.org/repos/asf/poi/site/src/documentation/release-guide.txt
There are links near the top of that to the underlying Apache policies and
release
On Fri, 2 Oct 2015, Javen O'Neal wrote:
I was thinking we should treat documentation artifacts like build
artifacts: only version control the source, host the artifacts on a regular
file server.
Consider moving documentation build artifacts to non-version-controlled web
server.
Currently, the
On Mon, 28 Sep 2015, Andreas Beeker wrote:
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 think I was going to remove HDF about 8 years ago...
However, maybe to be
On Sun, 27 Sep 2015, Andreas Beeker wrote:
please update the javadocs for 3.13 again. I've used the unofficial
windows openjdk 1.7 and it shuffles the javadocs, too.
Just tried, and it says that there are no changes, so I think we're all
good!
Thanks
Nick
On Thu, 24 Sep 2015, Patrick Bakker wrote:
I'd love to do write a simple unit test if I knew how that connected to
anything.
The way we work out what classes to pull from the large ooxml-schemas and
ooxml-security jars, into the smaller poi-ooxml-schemaes jar, is by
running the full junit
On Thu, 24 Sep 2015, Patrick Bakker wrote:
Missing classes in the poi-ooxml-schemas-3.13.beta1-20150723.jar so far are:
org.openxmlformats.schemas.wordprocessingml.x2006.main.CTSignedTwipsMeasure
org.etsi.uri.x01903.v13.AnyType
If you could provide us with a unit test that makes use of those,
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 beta 1 around
the same time, the former without
On Sat, 1 Aug 2015, Nick Burch wrote:
It hasn't been very long since our last beta, but we've managed to pack
quite a lot in that I think we want feedback on! The main thing is
obviously the SlideShow work that's come over to trunk, but also some
conditional formating updates and SXSSF basic
Hi All
We think we've now done everything for the IP Clearance of the Visio XDGF
contribution to Apache POI. The completed template can be found at:
http://incubator.apache.org/ip-clearance/poi-visio.html
Please do let us know if we've missed anything / done anything wrong!
Otherwise, we'll
On Mon, 14 Sep 2015, Dustin Spicuzza wrote:
Could you do a new dump with the updated headers? We can then review
those, and use that as the basis for the import once we're all happy
Updated dump made in a branch on github:
The diff:
On Fri, 11 Sep 2015, Dustin Spicuzza wrote:
* Finish the IP clearance template (looks like most of it is done?)
I think we only have one item left now!
* Change the copyright headers to Apache (where should I dump the code
once this is done?)
Could you do a new dump with the updated
On Sun, 13 Sep 2015, Dominik Stadler wrote:
The latest build ran on a different machine and was fast again, so it
seems to be only caused by a slow CI machine, see
https://builds.apache.org/view/POI/job/POI/buildTimeTrend for the trend.
Might be worth flagging to the builds team then, I
On Fri, 11 Sep 2015, Dominik Stadler wrote:
The two main steps are
* Build, test, binaries, javadocs, rat-check, forbidden-api-check,
...: Total time: 80 minutes 44 seconds
On my laptop, which is several years old and increasingly sulky, that all
takes single digit minutes. clean + test +
Hi All
I gather we've a fair number of Apache POI and Tika committers coming to
Budapest for ApacheCon's Europe and Big Data [1][2], in Budapest in a few
weeks time (28th Sept - 2nd Oct)
Having checked with the organisers, we can get a room one evening for a
meetup and hackathon, if we'd
Hi All
As discussed in bug #58087
https://bz.apache.org/bugzilla/show_bug.cgi?id=58087, we've had the
offer + paperwork to contribute a new POI component, XDGF, to handle visio
.vsdx files. The code for that is on github, at
https://github.com/BBN-D/poi-visio
I'm currently filling out the
On Sat, 15 Aug 2015, Andreas Beeker wrote:
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
On Sat, 15 Aug 2015, Andreas Beeker wrote:
we have several cases of NM_SAME_SIMPLE_NAME_AS_SUPERCLASS in the
findbugs reports and as the description says, this is confusing
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
On Sat, 8 Aug 2015, kiwiwi...@apache.org wrote:
Added:
poi/trunk/src/contrib/src/org/apache/
I thought we'd decided a while back to ditch the contrib area? Everything
from there either went into core / ooxml / scratchpad (useable as-is), or
example (works but normally needs changes to
On Mon, 3 Aug 2015, kiwiwings wrote:
our gump build is still failing [1] and I've tried to work around the
missing woodstox
reference in TestPPTX2PNG and PresetGeometries.
You could try asking builds@ to see if they've any idea / seen it before.
Since the build is ok on Jenkins (I believe?),
On Sun, 2 Aug 2015, Andreas Beeker wrote:
I'm currently adapting #58190 - the idea of the bug will remain, but the
implementation is actually different to the patch provided.
Sounds a good reason to wait to me! Shout when you're done :)
Nick
Hi All
It hasn't been very long since our last beta, but we've managed to pack
quite a lot in that I think we want feedback on! The main thing is
obviously the SlideShow work that's come over to trunk, but also some
conditional formating updates and SXSSF basic formula eval.
What does
On Fri, 31 Jul 2015, Gordon Pettey wrote:
For POI 3.12, the Maven artifact classifier for javadoc got an s
added, so is now -javadocs.jar. This is non-standard and breaks tools
that auto-download a javadoc classifier along with the main artifact.
The POI 3.13 snapshots have the same problem.
On Tue, 14 Jul 2015, Andreas Beeker wrote:
May I start with the next beta release?
The quick bit of Conditional Formatting stuff I've been working on this
week looks to be a bit bigger than I'd first anticipated... It's in a
stable state part-implemented, so you ought to be fine to cut a
Hi All
While we haven't done that many changes since 3.12 by number, we have done
one big change by scope, that of switching the default POIFS
implementation to NPOIFS. I think we've now ironed out all the issues with
that switch (thanks for everyone who helped test!), but I think we might
On Fri, 19 Jun 2015, Dominik Stadler wrote:
FYI, I have added a new section related projects where I listed some
projects that are related to POI in some way, primarily Tika, two
incubating that sound related and at least NPOI.
Great, thanks!
Let me know what you think? Any obvious others
On Fri, 19 Jun 2015, Henning Femmer wrote:
I now wrote a workaround to fix this issue for myself, feel free to
adapt and include it in the code, if you like:
Would you be able to raise a new bug in bugzilla, and post your code
there? Bonus marks if you could also upload a very small word file
On Wed, 3 Jun 2015, David North wrote:
Should I be able to log into bugzilla using my ASF credentials? It
doesn't seem to accept them, but obviously the account I've been
reporting bugs as previously doesn't let me edit the assignee, etc.
They have different account databases. So, just keep
On Thu, 28 May 2015, Allison, Timothy B. wrote:
As ongoing penance for my regrettable past (really it is behind me...I
hope...), I'd like to start cleaning up some of the code whenever I come
across style issues. I'll follow the guidance of fixing whitespace in
separate patches from content
On Thu, 28 May 2015, Andreas Beeker wrote:
In the context of the jackcess-discussion, I'd even more prefer, if we
split those components to separate jars having the X/H??F classes
together.
It certainly used to be the case that some users didn't want the X##F
family of documents, and didn't
On Wed, 27 May 2015, cen...@apache.org wrote:
adjust instructions for XWPF to note that scratchpad-jar is needed as well
Should that be the case though?
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
Hi All
On behalf of the Apache POI PMC, we're pleased to announce that David
North has been elected as a committer and PMC member for the project!
For anyone else thinking of getting involved, there's some information
available on the project website at http://poi.apache.org/guidelines.html
Hi All
As we've just added a new committer, and we've a few people working away
in the community who might be committer material in the future, I thought
it might be helpful to write some notes and advice for newer members. This
is a little bit of a brain-dump, so please shout if something
On Fri, 15 May 2015, David North wrote:
One change which we have in our local build of POI is the extraction of
super-interfaces to make streaming read of worksheets a bit nicer:
CellEssence is implemented by XSSFCell, HSSFCell and SXSSFCell:
RowEssence is similar and exposes CellEssences for
On Thu, 14 May 2015, Larry Wilson wrote:
Any ETA on when this will be pushed to the Maven Repository
(http://mvnrepository.com/artifact/org.apache.poi)?
It's available on the main Apache maven repo site:
https://repository.apache.org/#nexus-search;quick~org.apache.poi
And it's available on
On Mon, 11 May 2015, Dominik Stadler wrote:
I would like to fix this by moving the POIDocument member to the point
in the class-hierarchy where it is actually used, POIOLE2TextExtractor
to not pollute the classes under POIXMLTextExtractor with this.
Makes sense to me. I think we nearly did
On Tue, 12 May 2015, Andreas Beeker wrote:
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
On Mon, 11 May 2015, Dominik Stadler wrote:
I would like to keep information like this on the official poi page so
every committer can update the information and it is not distributed
across different places.
We do have one or two places listing upcoming changes, I think dating back
15
On Sat, 9 May 2015, Andreas Beeker wrote:
here is the 3rd release candidate, which is accessible under:
https://dist.apache.org/repos/dist/dev/poi/3.12-final-rc3/
keys and hashes pass, everything that should/shouldn't be there seems
correct, so I'm +1
One thing on the keys though - the gpg
On Sat, 9 May 2015, Andreas Beeker wrote:
After reading your response, I've noticed that I broaden the context a bit.
I only meant poi-src-3.12-20150511.tar.gz/.zip, not the maven source jars,
which I also prefer when working with open source.
As far as the foundation is concerned, the most
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 the most important part of the release is
On Thu, 7 May 2015, kiwiwings wrote:
Sorry, I wasn't aware that my test output files will be included in the src
package.
I find it's normally safest to build releases from a different, clean +
fresh checkout. I say this as someone having made the same mistake in the
past...
Nick
On Mon, 4 May 2015, Andreas Beeker wrote:
On 04.05.2015 22:26, Allison, Timothy B. wrote:
While working on TIKA-1315, I found a source for an NPE in
XWPFParagraph, and I'd also like to add some tests that will force
inclusion of some of the lower-level ooxml classes for paragraph
numbering.
On Mon, 27 Apr 2015, kiwiwings wrote:
Nick Burch-2 wrote
What do people think about us doing a new beta, 3.12 beta 2, fairly
soon? Worth doing now, or worth waiting for a specific bug/feature
first?
I wouldn't mind if we have a final soon.
OK, doing a final shortly then merging in the SL
On Thu, 30 Apr 2015, Allison, Timothy B. wrote:
We see advantages:
1) It just makes sense to have one centralized MSOffice parsing library
2) Increasing public awareness of each other's projects
3) sparking more cross-project, well, inner-project, collaboration among
the POI and Jackcess
101 - 200 of 685 matches
Mail list logo