[Bug 60184] Saved file that uses a XSSFFont without a specifically set FontFamily won't open in Excel
https://bz.apache.org/bugzilla/show_bug.cgi?id=60184 Marek Branickychanged: What|Removed |Added OS||All Severity|normal |blocker -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project ooxml-schemas has an issue affecting its community integration. This issue affects 5 projects. The current state of this project is 'Failed', with reason 'Build Timed Out'. For reference only, the following projects are affected by this: - ooxml-schemas : POI - org.apache.poi : POI - poi : POI - poi-ooxml-schemas : POI - poi-test : POI Full details are available at: http://vmgump.apache.org/gump/public/poi/ooxml-schemas/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [ooxml-schemas-[0-9]*[0-9T].jar] identifier set to project name -INFO- Failed with reason build timed out -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/poi/ooxml-schemas/gump_work/build_poi_ooxml-schemas.html Work Name: build_poi_ooxml-schemas (Type: Build) Work ended in a state of : Failed Elapsed: 1 hour 3 secs Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only -Dant.build.clonevm=true org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml compile-ooxml-xsds [Working Directory: /srv/gump/public/workspace/poi] CLASSPATH: /usr/lib/jvm/java-8-oracle/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/poi/ooxml-lib/curvesapi-1.04.jar:/srv/gump/public/workspace/poi/ooxml-lib/xmlbeans-2.6.0.jar.orig:/srv/gump/public/workspace/poi/compile-lib/bcpkix-jdk15on-1.54.jar:/srv/gump/public/workspace/poi/compile-lib/bcprov-ext-jdk15on-1.54.jar:/srv/gump/public/workspace/poi/compile-lib/slf4j-api-1.7.12.jar - Buildfile: /srv/gump/public/workspace/poi/build.xml check-jars: fetch-jars: check-ooxml-jars: fetch-ooxml-jars: init: [echo] Using Ant: Apache Ant(TM) version 1.10.0alpha compiled on September 29 2016 from ${ant.home}, Ant detected Java 1.8 (may be different than actual Java sometimes...) [echo] Using Java: 1.8.0_60/1.8.0_60-b27/25.60-b23/Java HotSpot(TM) 64-Bit Server VM from Oracle Corporation on Linux: 3.13.0-66-generic [echo] Using Findbugs: 3.0.1 for Java 1.8.0_60 check-ooxml-xsds: fetch-ooxml-xsds: [get] Getting: http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%201st%20edition%20Part%204%20(PDF).zip [get] To: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part4.zip [get] Getting: http://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%201st%20edition%20Part%202%20(PDF).zip [get] To: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part2.zip [get] Getting: https://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd [get] To: /srv/gump/public/workspace/poi/ooxml-lib/xmldsig-core-schema.xsd [get] Getting: http://uri.etsi.org/01903/v1.3.2/XAdES.xsd [get] To: /srv/gump/public/workspace/poi/ooxml-lib/XAdES.xsd [get] Getting: http://uri.etsi.org/01903/v1.4.1/XAdESv141.xsd [get] To: /srv/gump/public/workspace/poi/ooxml-lib/XAdESv141.xsd [unzip] Expanding: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part4.zip into /srv/gump/public/workspace/poi/ooxml-lib [unzip] Expanding: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part2.zip into /srv/gump/public/workspace/poi/ooxml-lib [unzip] Expanding: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-Part4.zip into /srv/gump/public/workspace/poi/ooxml-lib check-compiled-ooxml-xsds: compile-ooxml-xsds: [mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-xsds [mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-sources [mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-classes [copy] Copying 2 files to /srv/gump/public/workspace/poi/build/xmlbean-xsds [copy] Copying 87 resources to /srv/gump/public/workspace/poi/build/xmlbean-xsds [xmlbean] Time to build schema type system: 6.146 seconds [xmlbean] Time to generate code: 10.0 seconds [copy] Copying 7 files to /srv/gump/public/workspace/poi/build/xmlbean-sources [javac] Compiling 4575 source
[Bug 59734] Named range creation & lookup are linear in the number of ranges
https://bz.apache.org/bugzilla/show_bug.cgi?id=59734 --- Comment #5 from Greg Woolsey--- Where is the new dependency tracked for end users? The change log? For people who don't use Maven or Ivy, it make come as a surprise that running their code suddenly fails with a NoClassDefFound error (it just did for me, running a local project with a local build of POI as a dependency). I missed the commit message, and had to go find this issue. It doesn't seem that hard to implement using a normal HashMap, where the desired name is upper or lower-cased between the user call and the map lookup. It could be a Map > construct, where the outer Map is by sheet name. Global names would be mapped under the null entry. Request sheet and table names would be looked up in the internal map by upper or lower case cannonicalization (null aware for sheets), and no special tuple or Commons Collections class would be needed. Was simplicity the only reason for adding the package dependency? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 59857] Password protected files with "Microsoft Enhanced Cryptographic Provider v1.0"
https://bz.apache.org/bugzilla/show_bug.cgi?id=59857 Andreas Beekerchanged: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #7 from Andreas Beeker --- Patch for applied with r1762726 this also contains the mentioned encrpytion routines. Up till now I couldn't fix the xor obfuscation bug. Apart of the encryption routines, I needed to tweak the little endian stream classes to be real In-/OutputStreams, but that change effect only the closed resources warning, which were ignored in the original version -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 60184] New: Saved file that uses a XSSFFont without a specifically set FontFamily won't open in Excel
https://bz.apache.org/bugzilla/show_bug.cgi?id=60184 Bug ID: 60184 Summary: Saved file that uses a XSSFFont without a specifically set FontFamily won't open in Excel Product: POI Version: 3.15-FINAL Hardware: PC Status: NEW Severity: normal Priority: P2 Component: XSSF Assignee: dev@poi.apache.org Reporter: a...@vaadin.com Steps to reproduce: * open a spreadsheet created with Excel. * create a new cell style with workbook.createCellStyle() * create a new XSSFFont with workbook.createFont() * add the font to the new style * add the style to one cell * save the sheet to a new file * try to open the created file in Excel If you add FontFamily to the new font, the resulting file opens without issues. Otherwise it complains about corrupted style. The issue is apparently also present in some sheets with pre-existing styling that are simply loaded to POI and then saved into another sheet. See https://dev.vaadin.com/ticket/20180 for example files and more details. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
Fwd: Accuration Bug
Forwarding to the right place. Mark Forwarded Message Subject:Accuration Bug Date: Wed, 28 Sep 2016 10:00:47 + From: Sun, RickyReply-To: tradema...@apache.org To: webmas...@foo.com , webmas...@toddsbeer.org , tradema...@apache.org Dear Sirs, Thank you for your poi jars working on Excel. I’m using it to develop project using java. I got an bug about accurate calculation. The result from java is 0.07 base on the formula in Excel, but actually, the result is 0.06 in Excel. I think the bug can be fixed by using BigDecimal type to calculate formula in java. Thanks, Ricky test.xlsx Description: MS-Excel 2007 spreadsheet package com.fmr.svc.auto.score.dda; import java.text.ParseException; import org.apache.poi.xssf.usermodel.XSSFCell; import org.apache.poi.xssf.usermodel.XSSFWorkbook; public class Test extends TestCalculation { public static void main(String[] args) { try { get(); } catch (Exception e) { e.printStackTrace(); } } public static void get() throws Exception { String excelPathFile = "..\\yourexcel\\test.xlsx"; XSSFWorkbook workbook = getWorkBook(excelPathFile); // refresh excel tool engine workbook.getCreationHelper().createFormulaEvaluator().evaluateAll(); double value = test(getCellByRowCol(workbook, "abc", 5, 0)); System.out.println(value); } public static double test(XSSFCell cell) throws ParseException { System.out.println(cell.getCellFormula()); double cellValue = cell.getNumericCellValue(); return cellValue; } } - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org