Could we consider keeping all the jars but ensure that no package spans jars?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional
I would like to complete an xmlbeans 3.0.2 release this week.
Can I call a vote?
The changes are listed in
https://issues.apache.org/jira/browse/XMLBEANS-520?jql=project%20%3D%20XMLBEANS%20AND%20fixVersion%20%3D%20%22Version%203.0.2%22
Here's my +1.
--
Sent from:
I've been using the Oracle 8 JDK as my default for a while but thought that
for building XMLBeans it would be better to use an older JDK since we
support JDK 6 and above. JDK 6 is not easily installed on Macs so I thought
JDK 7 was a better bet.
--
Sent from:
XMLBeans 3 has similar XML parser factory code to POI and with the reported
issues and fixes we've done for POI 4.0.1, I was hoping to release similar
fixes for XMLBeans 3.0.2.
Would it be feasible to get XMLBeans 3.0.2 reviewed?
--
Sent from:
I've uploaded new artifacts with a couple of extra changes.
Still built using the apache jenkins jdk 1.6 build.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20XMLBEANS%20AND%20fixVersion%20%3D%20%22Version%203.0.2%22
Is it time for us to look at doing a POI 4.0.1 release?
Are there any issues we would like to see completed before we proceed?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe,
Thanks everyone. There have been 4 +1s (including me). I will proceed with
the release in the coming days if there are no objections.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To
The condition is `next != -1` but the value of next appears to -1 so that
this condition is false.
Maybe the condition should `next == -1`
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To
LGTM.
2 minor typos:
conjuction
uneccessary
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail:
Could you try using DataFormatter after using the FormulaEvaluator?
https://stackoverflow.com/questions/21538481/xssf-how-to-get-anything-as-string/21550258#21550258
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
No external parties have reported bugs.
I did notify a few external projects about the release of 3.0.0 and some
upgraded to it.
If people have issues, there is enough documentation on the web that I would
expect them to be able to find the POI mailing list or the XMLBeans JIRA.
1 non-POI
Does anyone know how to delete the Jenkins job
https://builds.apache.org/job/XMLBeans-DSL-1.6/ ?
I created a new job called POI-XMLBeans-DSL-1.6 because it's easier to find
it if it's grouped with the other POI jobs.
https://builds.apache.org/view/P/view/POI/
--
Sent from:
I've created a basic build job at
https://builds.apache.org/view/P/view/POI/job/POI-XMLBeans-DSL-1.6
I downloaded the zip/tgz/jar files from the build (built using JDK 1.6).
I replaced the artifacts in the staging repos:
Thanks Andi
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
Seems useful to do a 4.0.1 soon but I think we should wait a few weeks. There
have been a few issues reported and they continue to come in at reasonable
steady pace.
None of the issues so far seem to be blockers though.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
Should we do an XMLBeans 3.0.2 release?
https://issues.apache.org/jira/browse/XMLBEANS-520?jql=project%20%3D%20XMLBEANS%20AND%20fixVersion%20%3D%20%22Version%203.0.2%22
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
Somehow you've disabled the standard transitive dependency loading mechanisms
in your maven build.
Try adding:
org.apache.poi
poi
4.0.0
But without transitive dependency loading, you're going to have to
explicitly add lots of
There were some bugs in the maven pom dependencies that we published.
We were missing commons-math3 dependency and some dependencies were listed
with old version numbers.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
Thanks for the report. Could you raise an issue in
https://bz.apache.org/bugzilla/ ?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For
For reading large documents use
https://github.com/monitorjbl/excel-streaming-reader or
https://github.com/apache/poi/blob/trunk/src/examples/src/org/apache/poi/xssf/eventusermodel/XLSX2CSV.java
If you run into issues with shared strings table being too large, you might
also want
Hi Andi,
I just added
https://issues.apache.org/jira/browse/XMLBEANS-526?jql=project%20%3D%20XMLBEANS%20AND%20fixVersion%20%3D%20%22Version%203.0.3%22
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
For me, this kind of optimisation needs to be configurable. Most users would
not need this performance optimisation and would be better off to get the
full stack trace.
I would pitch that something like XmlOptions in the XMLBeans project is a
useful model. This allows users to choose to override
The real fix is https://bz.apache.org/bugzilla/show_bug.cgi?id=62692 -
XMLBeans-519 fixes a similar issue in XMLBeans (the SAXHelper code in
XMLBeans is basically a copy/paste of POI equivalent).
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
https://bz.apache.org/bugzilla/show_bug.cgi?id=62943 fix was to bring back a
try catch block around the code that had been removed in 4.0.0.
The 4.0.0 issue seems to affect users that have very old parsers - typically
part of Application Servers that have their own non-standard parsers.
I'm happy
I found a few missing classes in poi-ooxml-schemas.jar.
We have some gaps in the XDDF testing and this leads to us not adding all
the necessary OOXML classes for XDDF to the poi-ooxml-schemas.jar.
https://github.com/apache/poi/commit/df83dab1a49900d85d9a20c0ee6d5a7a31f0eb9c
--
Sent from:
I'm +1 -- the fix can wait till 4.0.2 and there is the workaround to use full
schema jar.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For
Tim - would you be able to provide some sample files and we can add some
regression tests?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
+1
Thanks for all the hard work getting this over the line.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail:
Thanks for your contributions.
Feel free to use Mockito in any of the submodules you need to use it in.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail:
The META-INF/services files appear in xmlbeans-xpath-2.6.0.jar.
50 07-23-2012 15:42
META-INF/services/org.apache.xmlbeans.impl.store.PathDelegate.SelectPathInterface
52 07-23-2012 15:42
META-INF/services/org.apache.xmlbeans.impl.store.QueryDelegate.QueryInterface
Since that
We unit test our POI 4.0 code base with java 11.
if you are seeing issues, could you provide a lot more detail?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail:
The directoryEntry that is causing in the NullPointerException is set in the
HSSFWorkbook constructor.
Could you be passing a null into this constructor?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
Could you raise a bugzilla issue and attach an xlsb file?
https://bz.apache.org/bugzilla/
xlsb is not an active area of development, I'm afraid.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
Should we release xmlbeans 3.0.3?
https://issues.apache.org/jira/browse/XMLBEANS-532?jql=project%20%3D%20XMLBEANS%20AND%20fixVersion%20%3D%20%22Version%203.0.3%22
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
Yes, to release the jars, you just need to run the release option in the
repository.apache.org UI.
I would suggest that we leave the jars in staging for a few days, just in
case someone spots any issues.
I've changed the POI build to use the xmlbeans 3.0.3 jars from staging and
the build seems
What version are you upgrading from? That org.apache.poi.hpsf.Util class no
longer exists.
I went back nearly 2 years in code history and find no sign of such a class.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
+1
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
In the ant build, we can download different versions of bouncycastle into
different directories. The openpgp task can use the old bouncycastle jar and
the dsig can use the new one. Bouncycastle has lots of security fixes and it
seems bad to completely switch back to a very old version.
These were
Thanks Greg.
In my testing, I had to make a couple of small code changes to get things
working again but nothing big and this is an intermediate version upgrade so
that's expected.
+1
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
The code that is failing is not POI code, it is from the java runtime.
It appears the test is trying to read a png file and convert it to a jpeg in
preparation for the POI part of the test.
Maybe we should just find a jpeg file for the test instead of doing this
conversion.
--
Sent from:
I've dropped the xmlbeans staging jars.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail:
Calling the next release 3.1.0 seems sensible to me. +1
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail:
Noone that I know of is actively working on a streaming API for docx or pptx.
Contributions to POI in these areas would be welcome.
One low level approach is to read docx/pptx files as zip files. If they are
password protected, you can use POI to first create a copy of the file with
the password
https://github.com/apache/poi/pull/143
The notifications for github PRs seem not to happen any more.
I don't know a lot about the H**F foramts. Would someone be able to review
github-143?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
I'm not very familiar with the OLE specification that POIFS implements.
Right now, we have the size parameter implemented as an int which means that
we are limited to a file size of approx 2G.
I had a look at changing the int to a long but this has a knock-on effect
for lots of classes.
Is there a
We've already released some JDK 6 friendly XMLBeans releases.
With https://issues.apache.org/jira/projects/XMLBEANS/issues/XMLBEANS-541
and just to make life easier for future development, could we move to just
building with Java 8 (and newer versions)?
Here's my +1 for the change.
--
Sent
We have 4 +1s.
I will proceed with the build changes over the coming days. Ping me if there
are any objections.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail:
My personal opinion is that I'd prefer not to add this to the POI core. It is
quite possible to have a community where people have side projects that use
the core code. The core POI code is already very large and we only have a
small number of volunteers to maintain it.
If we were to add this
I didn't want to complicate the last release but I discovered that POI
signing does not work with the latest xmlsec jar.
(https://bz.apache.org/bugzilla/show_bug.cgi?id=63712)
This signing code base is not something I am very familiar with - but it
would be nice not to stuck on the old jar.
--
That class is generated from a schema.
It is a big task to regenerate those classes based on a newer version of the
schema - and fix issues and uptake extra features - so we only do this
upgrade every few years.
http://www.ecma-international.org/publications/standards/Ecma-376.htm
--
Sent
101 - 150 of 150 matches
Mail list logo