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 fro
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.
--
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 code
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: dev-unsubscr
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 fro
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
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
-
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
--
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
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
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: dev-h
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 fi
For xmlbeans, I would recommend getting the release jars and zips from
https://builds.apache.org/view/P/view/POI/job/POI-XMLBeans-DSL-1.6/lastSuccessfulBuild/artifact/build/
This guarantees the jars were built with Java 6.
For the nexus release, I follow this guide:
https://central.sonatype.org/p
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: dev-h...@poi.apache.o
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: http:
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 p
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
---
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 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 https://github.co
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 addit
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: dev-unsubscr
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 ja
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
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 t
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: dev-unsubscr...@poi.
+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:
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 t
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
For
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
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: http:/
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 unsubs
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, e-mai
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 unsubscribe,
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
https://repository.apache.org/content/repositories/staging/org/apach
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: dev-h...@poi.apa
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: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f23
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
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
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: http://apache-poi.104
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:
https://repository.apache.org/content/repositories/staging/org/apache/xmlbe
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 person
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: http://apache-poi.1045710.n5.nabble.
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: http://apache-poi.1045710.n5.n
I have pushed xmlbeans 3.0.2 release candidate to:
https://repository.apache.org/content/repositories/staging/org/apache/xmlbeans/xmlbeans/3.0.2/
https://dist.apache.org/repos/dist/dev/poi/xmlbeans/
--
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
-
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
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 dependencies
I'm not sure why you need to load poi differently from xmlbeans. The xmlbeans
is correct but your poi dependencies are nothing like anything I've ever
seen.
Could you use the standard pom settings?
org.apache.poi
poi-ooxml
4.0.0
--
Sent from
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
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
-
To
I would like to see our CI build publish regular snapshots to Apache Nexus.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional com
Piccolo is no longer used or supported.
--
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.o
+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
Hi Andi,
I'm not sure how to sign an announce email. It also doesn't seem to be
common on https://lists.apache.org/list.html?annou...@apache.org to have
signed emails.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
--
I'd prefer if we rename the NPOIFS classes to POIFS but also keep deprecated
NPOIFS subclasses to reduce the impact on users who will be upgrading from
POI 3 to 4.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
---
Hi Andi,
I've done most of the pieces for the release.
The items that are incomplete are:
* Regenerating the xmlbeans site html using Forrest
* Announcing the release
I'm not sure of the exact command to use Forrest in the xmlbeans setup.
I'm also not sure what `Announcing the release` entails.
I have a look at doing all the items on the release list at the weekend.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional comman
I'd prefer not to wait for INFRA-14923. Even Sonatype's Nexus only adds md5
and sha1 digests.
These are generated by Nexus, as opposed to publisher's adding their own
digest files.
I have done some checking on maven central and in the cross section I
checked, no jars had sha256 or sha512 digests.
Hi Andi,
Would you be able to put the jaxb build changes in a patch file or in a
github branch?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.o
+1 for the release
--
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
The DataFormatter class has been like this for a number of years, so it would
not be a good idea to make big changes to its behaviour. Plenty of people
rely on it working the way it works right now.
We could add a 2nd DataFormatter that behaves the way you want it to - but
right now, we are busy wi
I've updated the staged artifacts for xmlbeans 3.0.1.
https://repository.apache.org/content/repositories/staging/org/apache/xmlbeans/xmlbeans/3.0.1/
and https://dist.apache.org/repos/dist/dev/poi/xmlbeans/
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
--
PS xmlbeans 3.0.1 is staged at
https://repository.apache.org/content/repositories/staging/org/apache/xmlbeans/xmlbeans/3.0.1/
and https://dist.apache.org/repos/dist/dev/poi/xmlbeans/
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
---
I'm +1 for an xmlbeans 3.0.1 release.
I changed tack a little and am now using new XmlOptions instead of system
properties to control the xmlbeans xml parser setup.
I had to undo the decrease in the default entity expansion limit due to
failing xmlbeans tests. The hardcoded limit was 4096 and the
I can do an xmlbeans 3.0.1 release in the coming days if there is PMC
approval.
With xmlbeans 3.0.0, I copied over the XML parser code from Apache POI and
the aim with 3.0.1 is to add the recent POI changes to XMLBeans.
XMLBeans is intended for broader use - ie to continue to facilitate non-POI
u
My opinion is that it would be good to release 4.0.0 soon and that we should
do a feature freeze shortly.
The upgrading of the schema seems like a nice-to-have as opposed to a
must-have for 4.0.0.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
--
+1 for 4.0.0 change
--
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
Hi Tim,
I don't think there is anything delaying a 4.0.0 release other than getting
the regression suites tested and any fixing any bugs that are found.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
Would it be possible to start pushing regular snapshots to maven
(https://repository.apache.org/content/repositories/staging/org/apache/poi/)
in the run up to the 4.0.0 release ?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
http://people.apache.org/~centic/poi_regression/reportsAll/download.oldindex/br.com.conhecadeus.www_Plano_Divino_Revelado_Homens_Apresentacao_11_O_Glorioso_Aparecimento_Cristo_Vers_C3_A3o2007.pptx
This document causes a NPE in the poi regression tests.
I added a fix to make the NPE go away but the
The current code blows up because the 4th param is empty (resulting in a
MissingArgEval issue) - the code will pass is the 4th param is set to the
true (the default for this param)
https://www.techonthenet.com/excel/formulas/vlookup.php
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI
I'm doing a little work on trying to change the XSSF streaming APIs to accept
a SharedStringsTable interface instead of a concrete implementation. We
currently have 3 different SharedStringsTable implementations and it would
be nice to be able to share code between the implementations and to allow
+1 for removal of unmaintained docs
--
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
Would it be possible to provide links to some of the more worrying regression
cases highlighted in
http://apache-poi.1045710.n5.nabble.com/XMLBeans-3-0-0-release-vote-td5730932.html#a5730965
?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
--
I checked in some artificial tests that load some of the ooxml-schemas
classes that are missing.
I was able to get the ooxml build and tests to work locally after
regenerating poi-ooxml-schemas with the extra classes.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
] Compiling 541 source files to
/Users/pj.fanning/svn/poi/build/ooxml-classes
[javac]
/Users/pj.fanning/svn/poi/src/ooxml/java/org/apache/poi/xddf/usermodel/chart/XDDFChart.java:67:
error: cannot find symbol
[javac] import
org.openxmlformats.schemas.drawingml.x2006.chart.CTSurface;
[javac
Thanks for the suggestions.
I've tried a few thing with XmlCursors and recreating the XmlBeans for
scratch but keep hitting new issues.
I suspect the best the approach is to create an XSSFSheet2 implementation
that has no XMLBeans in it - start by creating a sheet initialised from the
XMLBeans she
I've been looking at
https://github.com/apache/poi/blob/trunk/src/ooxml/testcases/org/apache/poi/xssf/usermodel/TestUnfixedBugs.java#L344
The test fails with: java.lang.AssertionError: Row 3 (1-based) is not in
ascending order; previously saw 5
After shifting the xssf rows as part of the test, th
I'm seeing some issues with poi-ooxml-schemas where it is missing inner
classes that implement Lists.
An example is this:
java.lang.NoClassDefFoundError:
org/openxmlformats/schemas/spreadsheetml/x2006/main/impl/CTSheetDataImpl$1RowList
at
org.openxmlformats.schemas.spreadsheetml.x2006.main
Thanks Andreas for all the work on the XMLBeans release announcement and all
the web site updates.
With the XMLBeans release process soon to be completed, are we in a position
to move onto pushing out the POI 4.0.0 release?
I've done some testing with the nightly builds and tried them out with som
Thanks Dominik, that makes sense, that type erasure in Java collections would
mean that the CTPhoneticRun is not necessarily loaded.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe,
Hi Dominik,
I cleaned out the workspace on the DSL-1.8 build plan and ran a build and
downloaded the bin zip from
https://builds.apache.org/view/P/view/POI/job/POI-DSL-1.8/ws/build/dist/
The CTPhoneticRun class is still missing from poi-ooxml-schemas jar though.
--
Sent from: http://apache-poi.
Thanks Andi for updating the xmlbeans.apache.org site.
Would it make sense to change the links on
https://xmlbeans.apache.org/community/index.html to point to the POI mailing
lists - the XMLBeans lists haven't been reactivated?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312
I updated https://poi.apache.org/ based on the latest documentation in poi
svn.
--
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 made a change[1] to try to gat an extra generated class included in
poi-ooxml-schemas jar.
The latest nightly jars did not end up including it and I've tried local
builds but do not get it included either.
Would someone be able to review the change to see if I've made a mistake?
[1]
https://gith
Would it be possible to get the https://poi.apache.org/ pages updated?
I added some notes in src/documentation about the XMLBeans 3.0.0 release.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To
I'm happy to discuss alternatives.
The XMLBeans SAXHelper was lifted directly from POI.
https://github.com/apache/poi/blob/trunk/src/ooxml/java/org/apache/poi/ooxml/util/SAXHelper.java
But with setEntityExpansionLimit being used too, it's probably safe to not
have the ignoring entity resolver.
Some of the github pull request builds failed and I wasn't sure what was
causing the issue. Conceptually, the POI build no longer needs any piccolo
manipulation because xmlbeans 3.0.0 removes the support for piccolo
entirely.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f231286
github is a read only mirror of the poi svn - we use pull requests on github
to demonstrate proposed changes but those pull requests need to be merged
using svn commits (by POI committers)
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
--
Can I ask for a vote on releasing XMLBeans 3.0.0?
This branch builds and tests POI with a pre-release version of XMLBeans.
https://github.com/apache/poi/pull/113
Releasing this jar to Maven Central should just be a click of a button in
Nexus.
https://issues.apache.org/jira/browse/XMLBEANS-517?jq
I found a bug in the xmlbeans build that I had accidentally added, that meant
some important classes were being omitted from the xmlbeans jar.
http://svn.apache.org/viewvc?view=revision&revision=1833948
I rebuilt my xmlbeans 3.0.0 candidate and removed the older 2.7.0-rc1
candidate.
The candidate
I think there's been a reasonable consensus on:
A +1
B: 1.6
C: +1
The 2.7.0-rc1 candidate is pretty close to what I would like to release. I
can produce a new version as a candidate for 3.0.0.
I have been using a very similar XMLBeans code base in production
applications for close to a year a
Can I get votes on the following?
A. Stop supporting Java 1.4
B. If we stop supporting Java 1.4, do set Java 1.6 or Java 1.8 as the
minimum?
C. Do we call the next release 3.0.0?
It's inconvenient to keep supporting Java 1.4 builds.
We don't need to use Java APIs that have been introduced after J
I have already upgraded xmlbeans from jdk 1.4 to jdk 1.6.
This was more because I can't find a jdk that will build jdk 1.4 compatible
binaries on my Mac.
I guess this means we'll need to call the next release 3.0.0.
I'm not convinced that we need to build against newer JDKs than 1.6. Running
appli
I published to https://dist.apache.org/repos/dist/dev/poi/xmlbeans/
I used svn to publish.
The maven dir is based on what is in Nexus.
The src and bin are based on artifacts that the xmlbeans ant build produces.
The asc files are based on my public PGP key.
--
Sent from: http://apache-poi.10
I do have the RC jars uploaded on Nexus (they are not released yet).
https://repository.apache.org/content/repositories/orgapachexmlbeans-1002/org/apache/xmlbeans/xmlbeans/2.7.0-rc1/
Is this enough?
I'm not sure how to push jars into https://dist.apache.org. I used the Nexus
UI (https://reposito
I have an RC1 build ready for release based on these changes:
https://issues.apache.org/jira/browse/XMLBEANS-517?jql=project%20%3D%20XMLBEANS%20AND%20fixVersion%20%3D%20%22Version%202.7.0%22
Can I call a vote on whether to proceed with an
org.apache.xmlbeans:xmlbeans:2.7.0-rc1 release?
My vote i
Could you raise an issue at https://bz.apache.org/bugzilla/enter_bug.cgi ?
It would be useful to attach a file that demonstrates the issue.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubs
1 - 100 of 154 matches
Mail list logo