Hi,
I would like to push a release for POI 3.11-beta2, because we have some
important changes missing in beta1. Please commit your changes in the next 24
to 36 hours, so I can start with the release process in 2 days.
Thanks,
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http
, 2014-08-18.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
Hi,
Just a friendly reminder: Please check and test the release artifacts!
Many thanks,
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Uwe Schindler [mailto:u...@thetaphi.de]
Sent: Thursday
pass. ASC files verify and MD5/SHA1 are correct. Docs look fine.
Here is my +1 to release the above artifacts and deploy to Maven Central, Uwe
P.S.: The vote keeps open for 72hrs, 2014-08-21, 0:00 UTC, planned release
announcement date is Friday, 2014-08-22.
-
Uwe Schindler
H.-H.-Meier
Hi,
Thanks to all, this vote has passed.
I will publish the artifacts and Maven now.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Nick Burch [mailto:n...@apache.org]
Sent: Sunday, August 17
java 1.4+.
This will also happen with the bug fix release 3.10.1. There is nothing we can
do; upgrade to newer XERCES, which is compliant to newer Java versions.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message
severe there, because
DocumentHelper is only used for Excel Import/Export in OOXML, not for openxml
DOMs.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Dominik Stadler [mailto:dominik.stad
2.6.1 is 10 (!!!) years
old and was released before Java 5, which added
DoucmentBuilderFactory#setFeature().
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Uwe Schindler [mailto:u...@thetaphi.de]
Sent
Hi,
I will add a line to the 3.10.1 release notes in a moment, which is already on
Maven Central and most mirrors.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: David kerber [mailto:dcker
, PowerPoint, Visio and
Word. Since POI 3.5, the new OOXML (Office Open XML) formats introduced in
Office 2007 have been supported.
See http://poi.apache.org/ for more details
On behalf of the Apache POI PMC,
Uwe
-
Uwe Schindler
uschind...@apache.org
Apache Lucene PMC Member / Committer
Apache POI
at this time.
If somebody wants to give additional votes, he should do now :-)
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Uwe Schindler [mailto:u...@thetaphi.de]
Sent: Sunday, August 17, 2014 2
the Maven
artifacts, to make the Apache TIKA committers happy.
I may announce the release tomorrow (although the date in the ZIP files is Aug
22) or should I better wait till Friday (Aug 22). Any suggestions?
Thanks to all for voting!
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
and
writing Microsoft Office file formats, such as Excel, PowerPoint, Word,
Visio, Publisher and Outlook. It supports both the older (OLE2) and
new (OOXML - Office Open XML) formats.
See http://poi.apache.org/ for more details
On behalf of the Apache POI PMC,
Uwe
-
Uwe Schindler
uschind...@apache.org
your classpath up! If you use
Maven, exclude the useless dependencies on xml-apis.jar or stax-apis.jar with
an exclude. Also make sure you use latest versions of XML parsers.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
I fixed the forbiddenapis issue. The problem was incomplete classpath.
Forbiddenapis used the javadoc.classpath, which did not include the
excelant.classpath which has the ANT jar files as downloaded from Maven Central.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http
singleton, so no speed improvement at all!
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: virtu...@apache.org [mailto:virtu...@apache.org]
> Sent: Monday, October 19, 2015 4:56 PM
&
are doing. And maybe add a
comment why you do this. The same applies for Locales or Charsets. E.g., At
some places in Lucene we explicitely use the charset of the console, so we use
Charset.getDefault() at all those places.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http
This was fast :-) I was about to patch this.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: cen...@apache.org [mailto:cen...@apache.org]
> Sent: Wednesday, September 30, 2015 10:00 PM
&
Hi,
> I think we should switch to Java 7 post-3.14, I don't think any of those
> things will reduce code size a lot, but most of these are quite useful as
> soon as you get used to them.
Most of them can be applied automatically using Eclipse (e.g. diamonds).
Multi-catch is very useful. Also
"-m" (only show modified stuff) and "-o" and "-n" to specify the
old and new JAR file. After that you can grep on something like DEPRECATED.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Origina
Hi,
> 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?
Needs to be "java.awt.**"; same syntax like Ant for cross directory file
matches.
Uwe
that on Java 9 you have to write your application using the module
system or pass an additional command line option to java
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
Hi,
In addition, Java 9 does not ship with JAXB enabled by default (see my previous
mail about that). You have to pass a command line arg to enable the Java EE
modules (next to CORBA and other J2EE stuff).
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
gets(Project.java:1405)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1376)
> at
>org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1260)
> at org.apache.tools.ant.Main.runBuild(Main.java:857)
> at org.apache.tools.ant.Main.startAnt(Main.java:236)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:287)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:113)
>
>Total time: 21 minutes 12 seconds
>Build step 'Invoke Ant' marked build as failure
>Skipping publisher since build result is FAILURE
>Archiving artifacts
>[Fast Archiver] No prior successful build to compare, so performing
>full copy of artifacts
>Skipping publisher since build result is FAILURE
>Recording test results
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
>For additional commands, e-mail: dev-h...@poi.apache.org
--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
package names is important,
too.
So better get it out of attic!
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: pj.fanning [mailto:fannin...@yahoo.com]
> Sent: Tuesday, February 20, 2018 2:26 PM
by the
last try/catch block and saved as a warning for "UNMAP_UNSUPPORTED". Or did you
hack the code to get the full stack trace?
Uwe
-
Uwe Schindler
uschind...@apache.org
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
https://lucene.apache.org/
> -Original Messag
Hi,
> I currently try to understand, how to call the Cleaner in Java 14 (or 9+)
> without
> adding the --add-opens JVM options.
Yeah, your code won't work correctly with Java 9 at all. You may fix it with
some opens, but still types of internal calsses changed, so its just risky
(everything
s shielded by the module system. Because of this
it falls back to the Java 8 code, which won't work at all (causing the
exceptions).
Uwe
-
Uwe Schindler
uschind...@apache.org
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
https://lucene.apache.org/
> -Original Message-
> From: U
:
https://svn.apache.org/viewvc/poi/trunk/src/java/org/apache/poi/poifs/nio/CleanerUtil.java?view=markup#l99
And step through the code? It might fall through to the catch block and java 8
code.
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
(there it works) or on modulepath
(won't work without importing jdk.unsupported).
In both cases, if everything is declared correctly in JAR file no
exports/imports or command line options are needed.
Lucene does not support Modules at all, so it's no issue for us.
Uwe
-
Uwe Schindler
uschind
king code.
> -
> Uwe Schindler
> uschind...@apache.org
> ASF Member, Apache Lucene PMC / Committer
> Bremen, Germany
> https://lucene.apache.org/
>
> > -----Original Message-
> > From: Uwe Schindler
> > Sent: Friday, August 7, 2020 6:16 PM
the JRE reacts, if you use classpath mode in
>Java 9+.
>I guess it ignores the module-info modules and the patched
>multi-release class, effectively running the Java 8 code.
>So we need both versions with that fallback mechanism.
>TL;DR: don't change CleanerUtil.
>
>
>
&g
was to release with Java 8, so I need to save the .class file
>when compiling with Java 9+ before.
>
>Andi
>
>
>On 07.08.20 23:07, Uwe Schindler wrote:
>> CleanerUtil dies not need to be multireleased. Just leave as is.
>>
>> The problem was only the missing import
33 matches
Mail list logo
