Jenkins build is back to normal : POI » POI-DSL-Windows-1.16 #304

2021-10-20 Thread Apache Jenkins Server 
See 



-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Build failed in Jenkins: POI » POI-DSL-Windows-1.8 #320

2021-10-20 Thread Apache Jenkins Server 
See 


Changes:

[PJ Fanning] get proper xmlbeans 5.0.2 release

[Andreas Beeker] sonar fixes

[PJ Fanning] ant 1.10.12

[PJ Fanning] hs-err file location


--
[...truncated 37.99 KB...]
> Task :poi-examples:processResources NO-SOURCE
> Task :poi-examples:classes
> Task :poi-examples:jar

> Task :poi:compileTestJava
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\record\TestFormulaRecord.java:90:
 warning: [deprecation] getCode() in org.apache.poi.ss.usermodel.CellType has 
been deprecated
assertEquals(CellType.ERROR.getCode(), record.getCachedResultType());
   ^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\record\TestFormulaRecord.java:90:
 warning: [deprecation] getCachedResultType() in 
org.apache.poi.hssf.record.FormulaRecord has been deprecated
assertEquals(CellType.ERROR.getCode(), record.getCachedResultType());
 ^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestBugs.java:2362:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.STRING);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestHSSFCell.java:385:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.STRING);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestHSSFCell.java:389:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.BOOLEAN);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestHSSFCell.java:391:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.BOOLEAN);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestHSSFCell.java:394:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.BOOLEAN);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestHSSFCell.java:398:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.BOOLEAN);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestHSSFCell.java:399:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.STRING);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestHSSFCell.java:400:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.ERROR);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestHSSFCell.java:401:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.STRING);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\hssf\usermodel\TestHSSFCell.java:403:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
cell.setCellType(CellType.STRING);
^
F:\jenkins\jenkins-home\712657a4\workspace\POI\POI-DSL-Windows-1.8\poi\src\test\java\org\apache\poi\ss\usermodel\BaseTestSheetUpdateArrayFormulas.java:277:
 warning: [deprecation] setCellType(org.apache.poi.ss.usermodel.CellType) in 
org.apache.poi.ss.usermodel.Cell has been deprecated
scell.setCellType(CellType.STRING);
 ^

[jira] [Commented] (XMLBEANS-579) SampleXmlUtil misses root element with only one child

2021-10-20 Thread PJ Fanning (Jira) 


[ 
https://issues.apache.org/jira/browse/XMLBEANS-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432142#comment-17432142
 ] 

PJ Fanning commented on XMLBEANS-579:
-

added r1894429

> SampleXmlUtil misses root element with only one child
> -
>
> Key: XMLBEANS-579
> URL: https://issues.apache.org/jira/browse/XMLBEANS-579
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 5.0.1
>Reporter: Alexander Pinske
>Assignee: PJ Fanning
>Priority: Major
> Fix For: Version 5.0.3
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When generating a sample, usually the top-level-element is xml-fragment. But 
> when the type contains only one child-element, it becomes the root.
> {code:java}
> import org.apache.xmlbeans.SchemaTypeSystem;
> import org.apache.xmlbeans.XmlBeans;
> import org.apache.xmlbeans.XmlException;
> import org.apache.xmlbeans.XmlObject;
> import org.apache.xmlbeans.XmlOptions;
> import org.apache.xmlbeans.impl.xb.xsdschema.SchemaDocument;
> import org.apache.xmlbeans.impl.xsd2inst.SampleXmlUtil;
> public class SchemaTest {
>   private static String generateXml(String xsdString) throws XmlException 
> {
>   XmlOptions options = new 
> XmlOptions().setDocumentSourceName("a.xsd");
>   XmlObject xsd = SchemaDocument.Factory.parse(xsdString, 
> options);
>   SchemaTypeSystem schema = XmlBeans.compileXsd(new XmlObject[] { 
> xsd }, XmlBeans.getBuiltinTypeSystem(), options);
>   return 
> SampleXmlUtil.createSampleForType(schema.globalElements()[0].getType());
>   }
>   public static void main(String[] args) throws Exception {
>   String xml = generateXml(
>   " encoding=\"utf-8\"?> targetNamespace=\"x\" xmlns=\"http://www.w3.org/2001/XMLSchema\;>"
>   + " " //
>   + " 
> " //
>   + " 
> " //
>   + " 
> " //
>   + " 
> " //
>   + " 
> " //
>   + " " //
>   + "");
>   System.out.println(xml);
>   }
> }
> {code}
> Generates:
> {code:xml}
> 
>   string
> 
> {code}
> Expected:
> {code:xml}
> 
>   
> string
>   
> 
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[jira] [Assigned] (XMLBEANS-579) SampleXmlUtil misses root element with only one child

2021-10-20 Thread PJ Fanning (Jira) 


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

PJ Fanning reassigned XMLBEANS-579:
---

Assignee: PJ Fanning

> SampleXmlUtil misses root element with only one child
> -
>
> Key: XMLBEANS-579
> URL: https://issues.apache.org/jira/browse/XMLBEANS-579
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 5.0.1
>Reporter: Alexander Pinske
>Assignee: PJ Fanning
>Priority: Major
> Fix For: Version 5.0.3
>
>
> When generating a sample, usually the top-level-element is xml-fragment. But 
> when the type contains only one child-element, it becomes the root.
> {code:java}
> import org.apache.xmlbeans.SchemaTypeSystem;
> import org.apache.xmlbeans.XmlBeans;
> import org.apache.xmlbeans.XmlException;
> import org.apache.xmlbeans.XmlObject;
> import org.apache.xmlbeans.XmlOptions;
> import org.apache.xmlbeans.impl.xb.xsdschema.SchemaDocument;
> import org.apache.xmlbeans.impl.xsd2inst.SampleXmlUtil;
> public class SchemaTest {
>   private static String generateXml(String xsdString) throws XmlException 
> {
>   XmlOptions options = new 
> XmlOptions().setDocumentSourceName("a.xsd");
>   XmlObject xsd = SchemaDocument.Factory.parse(xsdString, 
> options);
>   SchemaTypeSystem schema = XmlBeans.compileXsd(new XmlObject[] { 
> xsd }, XmlBeans.getBuiltinTypeSystem(), options);
>   return 
> SampleXmlUtil.createSampleForType(schema.globalElements()[0].getType());
>   }
>   public static void main(String[] args) throws Exception {
>   String xml = generateXml(
>   " encoding=\"utf-8\"?> targetNamespace=\"x\" xmlns=\"http://www.w3.org/2001/XMLSchema\;>"
>   + " " //
>   + " 
> " //
>   + " 
> " //
>   + " 
> " //
>   + " 
> " //
>   + " 
> " //
>   + " " //
>   + "");
>   System.out.println(xml);
>   }
> }
> {code}
> Generates:
> {code:xml}
> 
>   string
> 
> {code}
> Expected:
> {code:xml}
> 
>   
> string
>   
> 
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[jira] [Resolved] (XMLBEANS-495) StackOverflowError when parsing a large number of characters in an XML element

2021-10-20 Thread PJ Fanning (Jira) 


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

PJ Fanning resolved XMLBEANS-495.
-
Resolution: Fixed

> StackOverflowError when parsing a large number of characters in an XML element
> --
>
> Key: XMLBEANS-495
> URL: https://issues.apache.org/jira/browse/XMLBEANS-495
> Project: XMLBeans
>  Issue Type: Bug
>  Components: Validator
>Affects Versions: Version 2.6
> Environment: All
>Reporter: Mandy Warren
>Assignee: PJ Fanning
>Priority: Major
> Fix For: Version 5.0.2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When XMLBeans validates a very long XML String (4000 or so chars), it 
> generates a StackOverFlowError as shown below. In the schema for this element 
> I have defined a pattern and a min/max length but XMLBeans is applying the 
> pattern first before checking the length. The solution is the fix applied to 
> the class RegularExpression in xerces - see 
> https://issues.apache.org/jira/browse/XERCESJ-589 which went into version 
> 2.11. 
>   
>   
>   
>   
>   
>   
>   
> Exception in thread "main" java.lang.StackOverflowError
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1662)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)
>   at 
> org.apache.xmlbeans.impl.regex.RegularExpression.matchString(RegularExpression.java:1872)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[jira] [Resolved] (XMLBEANS-569) support disallow-doctype-decl setting on XML parser

2021-10-20 Thread PJ Fanning (Jira) 


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

PJ Fanning resolved XMLBEANS-569.
-
Resolution: Fixed

> support disallow-doctype-decl setting on XML parser
> ---
>
> Key: XMLBEANS-569
> URL: https://issues.apache.org/jira/browse/XMLBEANS-569
> Project: XMLBeans
>  Issue Type: New Feature
>  Components: DOM
>Affects Versions: Version 5.0.1
>Reporter: PJ Fanning
>Assignee: PJ Fanning
>Priority: Major
> Fix For: Version 5.0.2
>
>
> https://xerces.apache.org/xerces2-j/features.html#disallow-doctype-decl
> XmlOptions will support this:
> options.setDisallowDocTypeDeclaration(true);



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[jira] [Resolved] (XMLBEANS-566) Configuration property "quiet" in the maven plugin is spelled wrong

2021-10-20 Thread PJ Fanning (Jira) 


 [ 
https://issues.apache.org/jira/browse/XMLBEANS-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

PJ Fanning resolved XMLBEANS-566.
-
Resolution: Fixed

> Configuration property "quiet" in the maven plugin is spelled wrong
> ---
>
> Key: XMLBEANS-566
> URL: https://issues.apache.org/jira/browse/XMLBEANS-566
> Project: XMLBeans
>  Issue Type: Bug
>Affects Versions: Version 5.0.0, Version 5.0.1
>Reporter: Travis Schneeberger
>Assignee: PJ Fanning
>Priority: Minor
> Fix For: Version 5.0.2
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The configuration property "quiet" is spelled as "quite" in the new maven 
> plugin introduced in version 5.0.0.
> {code:java}
> 
>   org.apache.xmlbeans
>   xmlbeans
>   5.0.1
>   
>     false
>   
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Jenkins build is back to normal : POI » POI-DSL-1.17 #55

2021-10-20 Thread Apache Jenkins Server 
See 



-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[RESULT] [VOTE] Apache XmlBeans 5.0.2 release (RC2)

2021-10-20 Thread PJ Fanning 
The vote has carried with 3 +1s from PMC members.

I will start the process of releasing to maven and will follow up with the 
distribution and docs.

Aim is to announce on Friday.






On Friday 15 October 2021, 07:37:59 IST, Dominik Stadler 
 wrote: 





Hi,

Thanks for the changes, this looks good now when comparing 5.0.2 to 5.0.1
binaries and sources!

And using the binaries directly from the Jenkins job is a good idea, then
we avoid local variations and have a canonical environment which produces
releases! Not sure how much is missing so we can also do this for POI
itself?


+1 from me!


Thanks... Dominik.



On Thu, Oct 14, 2021 at 11:10 PM Andreas Beeker 
wrote:

> Thank you again for providing the RC2 immediately.
>
> As we provide the module-info, the Automatic-Module-Name is probably not
> needed.
>
> So +1 from me.
>
> Andi
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Build failed in Jenkins: POI » POI-DSL-1.17 #54

2021-10-20 Thread Apache Jenkins Server 
See 

Changes:


--
[...truncated 33.82 KB...]
:394:
 warning: [deprecation] setCellType(CellType) in Cell has been deprecated
cell.setCellType(CellType.BOOLEAN);
^
:398:
 warning: [deprecation] setCellType(CellType) in Cell has been deprecated
cell.setCellType(CellType.BOOLEAN);
^
:399:
 warning: [deprecation] setCellType(CellType) in Cell has been deprecated
cell.setCellType(CellType.STRING);
^
:400:
 warning: [deprecation] setCellType(CellType) in Cell has been deprecated
cell.setCellType(CellType.ERROR);
^
:401:
 warning: [deprecation] setCellType(CellType) in Cell has been deprecated
cell.setCellType(CellType.STRING);
^
:403:
 warning: [deprecation] setCellType(CellType) in Cell has been deprecated
cell.setCellType(CellType.STRING);
^
:312:
 warning: [removal] SecurityManager in java.lang has been deprecated and marked 
for removal
SecurityManager sm = System.getSecurityManager();
^
:312:
 warning: [removal] getSecurityManager() in System has been deprecated and 
marked for removal
SecurityManager sm = System.getSecurityManager();
   ^
:313:
 warning: [removal] setSecurityManager(SecurityManager) in System has been 
deprecated and marked for removal
System.setSecurityManager(new NoExitSecurityManager());
  ^
:319:
 warning: [removal] setSecurityManager(SecurityManager) in System has been 
deprecated and marked for removal
System.setSecurityManager(sm);
  ^
:363:
 warning: [removal] SecurityManager in java.lang has been deprecated and marked 
for removal
private static class NoExitSecurityManager extends SecurityManager {
   ^
:90:
 warning: [deprecation] getCode() in CellType has been deprecated
assertEquals(CellType.ERROR.getCode(), record.getCachedResultType());
   ^
:90:
 warning: [deprecation] getCachedResultType() in FormulaRecord has been 
deprecated
assertEquals(CellType.ERROR.getCode(), record.getCachedResultType());
 ^
:154:
 warning: [removal] SecurityManager in java.lang has been deprecated and marked 
for removal
SecurityManager sm = System.getSecurityManager();
^
:154:
 warning: [removal] getSecurityManager() in System has been deprecated and 
marked for removal
SecurityManager sm = System.getSecurityManager();
   ^
:156:
 warning: [removal] SecurityManager in java.lang has been deprecated and marked 
for removal
System.setSecurityManager(new SecurityManager() {
  ^

Jenkins build is back to normal : POI » POI-DSL-1.17 #52

2021-10-20 Thread Apache Jenkins Server 
See 



-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 65640] org.apache.poi.ooxml.POIXMLException on parsing docx file

2021-10-20 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65640

--- Comment #4 from PJ Fanning  ---
The only workaround I can think of is for the user who has corrupt files like
this to parse the docx zip and to rename any footer*.xml files that have hdr
root elements as header *.xml -- but the user would probably need to update the
rels (relationships file) to record the rename.

Adding extra parsing overhead and the wasted CPU cycles for all users to fix
files that have this corruption in a small number of files is probably not
worth it. Unless we discover that this form of corrupted file is very common
and there is no hope of getting the producing software fixed, then we might
need to bite the bullet.

-- 
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 65639] org.apache.poi.util.RecordFormatException: Tried to allocate an array of length 4276190, but 1000000 is the maximum for this record type

2021-10-20 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65639

Nick Burch  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #4 from Nick Burch  ---
4mb of font metadata feels very high and likely broken, but if it is actually
holding the full font with lots of hinting/design then that might be
reasonable. If it is holding multiple fonts, 4mb seems quite likely.

Anyone have 15 minutes to find the relevant link to the MS docs on this kind of
font record, to check if it is just metadata or can contain full embedded
fonts?

-- 
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 65639] org.apache.poi.util.RecordFormatException: Tried to allocate an array of length 4276190, but 1000000 is the maximum for this record type

2021-10-20 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65639

--- Comment #3 from PJ Fanning  ---
It would seem odd to have a font config that is so big. It's my opinion that it
is not worth changing the POI default in this case. Someone else might have a
different opinion.

-- 
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 65639] org.apache.poi.util.RecordFormatException: Tried to allocate an array of length 4276190, but 1000000 is the maximum for this record type

2021-10-20 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=65639

redmanmale+apa...@gmail.com changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #2 from redmanmale+apa...@gmail.com ---
I've already use setByteArrayMaxOverride and it fixed problem for me.

But there's a comment in this method to open an issue if you're using it.
>>and please open up issues on POI's bugzilla to bump values for specific 
>>records.

That's it.

-- 
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