Build failed in Jenkins: POI-DSL-1.8 #347

[Apache Jenkins Server]

See 


Changes:

[fanningpj] [github-90] change default DSIG algorithm to SHA256. Thanks to Jörn 
Franke. This closes #90

--
[...truncated 143.54 KB...]
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFFormulaParser
[junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.044 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFHeaderFooterProperties
[junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.011 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFHyperlink
[junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.115 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFName
[junit] Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.065 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFOddFooter
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.002 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFOddHeader
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.002 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPicture
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.045 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPictureData
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.053 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPivotTableName
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.349 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPivotTableRef
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.258 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPrintSetup
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.032 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFRichTextString
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.02 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFRow
[junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.598 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFShape
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.033 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheet
[junit] Tests run: 95, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.797 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetAutosizeColumn
[junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.037 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetMergeRegions
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.786 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetRowGrouping
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.101 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetShiftRows
[junit] Tests run: 34, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 
27.266 sec
[junit] Running 
org.apache.poi.xssf.usermodel.TestXSSFSheetUpdateArrayFormulas
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.032 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSimpleShape
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.009 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFTable
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.104 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFTextParagraph
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.009 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFTextRun
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.004 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFVMLDrawing
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.042 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFWorkbook
[junit] Tests run: 59, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.51 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFCategoryAxis
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.006 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFChartAxis
[junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.009 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFChartLegend
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.007 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFChartTitle
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

Build failed in Jenkins: POI-DSL-OpenJDK #355

[Apache Jenkins Server]

See 


Changes:

[fanningpj] [github-90] change default DSIG algorithm to SHA256. Thanks to Jörn 
Franke. This closes #90

[fanningpj] add gradle wrapper

[fanningpj] bouncycastle 1.59

--
[...truncated 149.78 KB...]
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFFormulaParser
[junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.044 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFHeaderFooterProperties
[junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.012 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFHyperlink
[junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.118 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFName
[junit] Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.079 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFOddFooter
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.002 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFOddHeader
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.002 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPicture
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.04 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPictureData
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.052 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPivotTableName
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.311 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPivotTableRef
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.269 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPrintSetup
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.02 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFRichTextString
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.021 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFRow
[junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.693 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFShape
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.033 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheet
[junit] Tests run: 95, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.605 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetAutosizeColumn
[junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.048 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetMergeRegions
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.628 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetRowGrouping
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.19 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetShiftRows
[junit] Tests run: 34, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 
27.529 sec
[junit] Running 
org.apache.poi.xssf.usermodel.TestXSSFSheetUpdateArrayFormulas
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.032 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSimpleShape
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.009 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFTable
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.106 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFTextParagraph
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.01 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFTextRun
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.005 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFVMLDrawing
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.038 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFWorkbook
[junit] Tests run: 59, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.486 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFCategoryAxis
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.007 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFChartAxis
[junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.009 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFChartLegend
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.007 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFChartT

Re: ***UNCHECKED*** RE: adding dependencies on h2 and mockito

[Greg Woolsey]

If the goal is to allow for a very large shared strings hashtable, perhaps
a lighter weight option like MapDB [1][2] is a better fit?  It's JAR is
only 700K, and it looks quite reasonably featured (has an implementation of
HashMap) and flexible in its configuration for trading
memory/performance/scalability, including mmapped files and some level of
on-disk encryption [3].

[1] https://jankotek.gitbooks.io/mapdb/content/
[2] https://github.com/jankotek/mapdb/
[3] https://jankotek.gitbooks.io/mapdb/content/format/


On Fri, Jan 26, 2018 at 1:23 PM Dave Fisher  wrote:

> Hi -
>
> We need to be really careful not to make OOXML deployments larger.
>
> Why is H2, a database engine, being considered?
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Jan 26, 2018, at 11:55 AM, Alain FAGOT BÉAREZ 
> wrote:
> >
> > You might have heard of Hypersonic SQL, some 10 years ago. H2 is the
> second version thereof.
> >
> > ⁣Gesendet mit BlueMail ​
> >
> >
> >  Originale Nachricht 
> > Von: Greg Woolsey 
> > Gesendet: Fri Jan 26 16:42:44 GMT-03:00 2018
> > An: POI Developers List 
> > Betreff: Re: ***UNCHECKED*** RE: adding dependencies on h2 and mockito
> >
> > Total dependency size is important to my deployment, and probably others.
> > I don't use SXSSF at all, and would not need/want the dependency (which
> > I've never heard of in 20 years of database and Java development, which
> is
> > strange to me, but irrelevant).  My preference is to make it optional,
> even
> > though it's more work to code.  Default would be the current behavior,
> > which works for almost everyone, apparently, and an option would be to
> > enable this behavior and manage the package availability externally.
> >
> > I suppose one could manually exclude the package as well, if SXSSF isn't
> > used at all, since Java wouldn't try to load the classes unless a class
> > referencing them was loaded, but that behavior is always subject to
> change
> > and should not be relied upon.  Plus I wouldn't want to impose that on
> > existing users who don't need/want it.
> >
> >> On Fri, Jan 26, 2018 at 4:47 AM pj.fanning  wrote:
> >>
> >> I could make h2 a `provided` dependency in our poi-ooxml pom.
> >> The use of h2 is opt-in in the new code in my PR but I'll need to
> refactor
> >> the code to allow our code not to throw ClassNotFoundException if the h2
> >> classes are not on the runtime classpath. This is do-able but my
> concern is
> >> that this is difficult to automate tests for (checking the code works
> when
> >> the h2 jar is available and when it is not).
> >>
> >> https://mvnrepository.com/artifact/com.h2database/h2 is very common
> >> dependency, so my preference would be to have the explicit dependency
> from
> >> poi-ooxml on h2 - but I'll go with whatever the consensus is.
> >>
> >>
> >>
> >> --
> >> 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
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>

Build failed in Jenkins: POI-DSL-Windows-1.8 #122

[Apache Jenkins Server]

See 


Changes:

[fanningpj] [github-90] change default DSIG algorithm to SHA256. Thanks to Jörn 
Franke. This closes #90

[fanningpj] add gradle wrapper

[fanningpj] bouncycastle 1.59

[fanningpj] bouncycastle 1.59

--
[...truncated 149.76 KB...]
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFFormulaParser
[junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.061 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFHeaderFooterProperties
[junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.018 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFHyperlink
[junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.169 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFName
[junit] Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.062 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFOddFooter
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.004 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFOddHeader
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.005 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPicture
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.056 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPictureData
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.089 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPivotTableName
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.413 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPivotTableRef
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.307 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFPrintSetup
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.017 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFRichTextString
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.019 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFRow
[junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
3.181 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFShape
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.036 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheet
[junit] Tests run: 95, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
3.858 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetAutosizeColumn
[junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.039 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetMergeRegions
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.844 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetRowGrouping
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.21 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSheetShiftRows
[junit] Tests run: 34, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 
27.435 sec
[junit] Running 
org.apache.poi.xssf.usermodel.TestXSSFSheetUpdateArrayFormulas
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.051 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFSimpleShape
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.016 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFTable
[junit] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.14 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFTextParagraph
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.016 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFTextRun
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.007 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFVMLDrawing
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.046 sec
[junit] Running org.apache.poi.xssf.usermodel.TestXSSFWorkbook
[junit] Tests run: 59, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.515 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFCategoryAxis
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.012 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFChartAxis
[junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.015 sec
[junit] Running org.apache.poi.xssf.usermodel.charts.TestXSSFChartLegend
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.013 sec
[junit] Running org.apache.poi

Re: ***UNCHECKED*** RE: adding dependencies on h2 and mockito

[Dave Fisher]

Hi -

We need to be really careful not to make OOXML deployments larger.

Why is H2, a database engine, being considered?

Regards,
Dave

Sent from my iPhone

> On Jan 26, 2018, at 11:55 AM, Alain FAGOT BÉAREZ  wrote:
> 
> You might have heard of Hypersonic SQL, some 10 years ago. H2 is the second 
> version thereof. 
> 
> ⁣Gesendet mit BlueMail ​
> 
> 
>  Originale Nachricht 
> Von: Greg Woolsey 
> Gesendet: Fri Jan 26 16:42:44 GMT-03:00 2018
> An: POI Developers List 
> Betreff: Re: ***UNCHECKED*** RE: adding dependencies on h2 and mockito
> 
> Total dependency size is important to my deployment, and probably others.
> I don't use SXSSF at all, and would not need/want the dependency (which
> I've never heard of in 20 years of database and Java development, which is
> strange to me, but irrelevant).  My preference is to make it optional, even
> though it's more work to code.  Default would be the current behavior,
> which works for almost everyone, apparently, and an option would be to
> enable this behavior and manage the package availability externally.
> 
> I suppose one could manually exclude the package as well, if SXSSF isn't
> used at all, since Java wouldn't try to load the classes unless a class
> referencing them was loaded, but that behavior is always subject to change
> and should not be relied upon.  Plus I wouldn't want to impose that on
> existing users who don't need/want it.
> 
>> On Fri, Jan 26, 2018 at 4:47 AM pj.fanning  wrote:
>> 
>> I could make h2 a `provided` dependency in our poi-ooxml pom.
>> The use of h2 is opt-in in the new code in my PR but I'll need to refactor
>> the code to allow our code not to throw ClassNotFoundException if the h2
>> classes are not on the runtime classpath. This is do-able but my concern is
>> that this is difficult to automate tests for (checking the code works when
>> the h2 jar is available and when it is not).
>> 
>> https://mvnrepository.com/artifact/com.h2database/h2 is very common
>> dependency, so my preference would be to have the explicit dependency from
>> poi-ooxml on h2 - but I'll go with whatever the consensus is.
>> 
>> 
>> 
>> --
>> 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
>> 
>> 


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

Re: ***UNCHECKED*** RE: adding dependencies on h2 and mockito

[Alain FAGOT BÉAREZ]

You might have heard of Hypersonic SQL, some 10 years ago. H2 is the second 
version thereof.

⁣Gesendet mit BlueMail ​


 Originale Nachricht 
Von: Greg Woolsey 
Gesendet: Fri Jan 26 16:42:44 GMT-03:00 2018
An: POI Developers List 
Betreff: Re: ***UNCHECKED*** RE: adding dependencies on h2 and mockito

Total dependency size is important to my deployment, and probably others.
I don't use SXSSF at all, and would not need/want the dependency (which
I've never heard of in 20 years of database and Java development, which is
strange to me, but irrelevant).  My preference is to make it optional, even
though it's more work to code.  Default would be the current behavior,
which works for almost everyone, apparently, and an option would be to
enable this behavior and manage the package availability externally.

I suppose one could manually exclude the package as well, if SXSSF isn't
used at all, since Java wouldn't try to load the classes unless a class
referencing them was loaded, but that behavior is always subject to change
and should not be relied upon.  Plus I wouldn't want to impose that on
existing users who don't need/want it.

On Fri, Jan 26, 2018 at 4:47 AM pj.fanning  wrote:

> I could make h2 a `provided` dependency in our poi-ooxml pom.
> The use of h2 is opt-in in the new code in my PR but I'll need to refactor
> the code to allow our code not to throw ClassNotFoundException if the h2
> classes are not on the runtime classpath. This is do-able but my concern is
> that this is difficult to automate tests for (checking the code works when
> the h2 jar is available and when it is not).
>
> https://mvnrepository.com/artifact/com.h2database/h2 is very common
> dependency, so my preference would be to have the explicit dependency from
> poi-ooxml on h2 - but I'll go with whatever the consensus is.
>
>
>
> --
> 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
>
>

Re: ***UNCHECKED*** RE: adding dependencies on h2 and mockito

[Greg Woolsey]

Total dependency size is important to my deployment, and probably others.
I don't use SXSSF at all, and would not need/want the dependency (which
I've never heard of in 20 years of database and Java development, which is
strange to me, but irrelevant).  My preference is to make it optional, even
though it's more work to code.  Default would be the current behavior,
which works for almost everyone, apparently, and an option would be to
enable this behavior and manage the package availability externally.

I suppose one could manually exclude the package as well, if SXSSF isn't
used at all, since Java wouldn't try to load the classes unless a class
referencing them was loaded, but that behavior is always subject to change
and should not be relied upon.  Plus I wouldn't want to impose that on
existing users who don't need/want it.

On Fri, Jan 26, 2018 at 4:47 AM pj.fanning  wrote:

> I could make h2 a `provided` dependency in our poi-ooxml pom.
> The use of h2 is opt-in in the new code in my PR but I'll need to refactor
> the code to allow our code not to throw ClassNotFoundException if the h2
> classes are not on the runtime classpath. This is do-able but my concern is
> that this is difficult to automate tests for (checking the code works when
> the h2 jar is available and when it is not).
>
> https://mvnrepository.com/artifact/com.h2database/h2 is very common
> dependency, so my preference would be to have the explicit dependency from
> poi-ooxml on h2 - but I'll go with whatever the consensus is.
>
>
>
> --
> 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
>
>

CVE-2017-12626 – Denial of Service Vulnerabilities in Apache POI < 3.17

[Tim Allison]

Title: CVE-2017-12626 – Denial of Service Vulnerabilities in Apache POI < 3.17

Severity: Important

Vendor: The Apache Software Foundation

Versions affected: versions prior to version 3.17

Description:   
    Apache POI versions prior to release 3.17 are vulnerable to Denial of 
Service Attacks:
    * Infinite Loops while parsing specially crafted WMF, EMF, MSG and macros
          (POI bugs 61338 [0] and 61294 [1])
    * Out of Memory Exceptions while parsing specially crafted DOC, PPT and XLS 
          (POI bugs 52372 [2] and 61295 [3])


Mitigation:  Users with applications which accept content from external or 
untrusted sources are advised to upgrade to Apache POI 3.17 or newer.

-Tim Allison

on behalf of the Apache POI PMC

 

[0] https://bz.apache.org/bugzilla/show_bug.cgi?id=61338
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=61294
[2] https://bz.apache.org/bugzilla/show_bug.cgi?id=52372
[3] https://bz.apache.org/bugzilla/show_bug.cgi?id=61295

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

Re: poi .classpath file

[Alain FAGOT BÉAREZ]

In other projects, it is recommended NOT to version control IDE configurations.

For this reason, I use the Git global ignore configuration in order not to 
accidentally commit my changes.

+1



 Originale Nachricht 
Von: "pj.fanning" 
Gesendet: Fri Jan 26 09:49:08 GMT-03:00 2018
An: dev@poi.apache.org
Betreff: poi .classpath file

Is it ok to delete this and just have Eclipse users create the Eclipse
workspace using `gradle eclipse`?
Just makes for fewer places where we need to manage the jar version numbers.



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

[Bug 62050] Java throws me the WARNING

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=62050

Sergei  changed:

   What|Removed |Added

 OS||All

-- 
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 62050] New: Java throws me the WARNING

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=62050

Bug ID: 62050
   Summary: Java throws me the WARNING
   Product: POI
   Version: 4.0-dev
  Hardware: PC
Status: NEW
  Severity: normal
  Priority: P2
 Component: XWPF
  Assignee: dev@poi.apache.org
  Reporter: sergei.visot...@gmail.com
  Target Milestone: ---

Created attachment 35699
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35699&action=edit
WARNING

Hello,

I was trying to export data from .xlsx document to the console in Intellij IDEA
IDE, but Java throws me this warning: 
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.poi.openxml4j.util.ZipSecureFile$1
(file:/D:/Users/Sergei/Documents/JavaProjects/171rdb043/src/poi-3.17/poi-ooxml-3.17.jar)
to field java.io.FilterInputStream.in
WARNING: Please consider reporting this to the maintainers of
org.apache.poi.openxml4j.util.ZipSecureFile$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release

I'm using JDK 9 and JRE 9.
There is no problem in Intellij IDEA.
Could you explain me what may cause this problem?
I found that it might be probably bug in your API.
Screenshot in attachment.

Thanks,
Sergei

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

[GitHub] poi pull request #90: Replace default insecure SHA1 hash algorithm

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/poi/pull/90


---

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

poi .classpath file

[pj.fanning]

Is it ok to delete this and just have Eclipse users create the Eclipse
workspace using `gradle eclipse`?
Just makes for fewer places where we need to manage the jar version numbers.



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

***UNCHECKED*** RE: adding dependencies on h2 and mockito

[pj.fanning]

I could make h2 a `provided` dependency in our poi-ooxml pom.
The use of h2 is opt-in in the new code in my PR but I'll need to refactor
the code to allow our code not to throw ClassNotFoundException if the h2
classes are not on the runtime classpath. This is do-able but my concern is
that this is difficult to automate tests for (checking the code works when
the h2 jar is available and when it is not).

https://mvnrepository.com/artifact/com.h2database/h2 is very common
dependency, so my preference would be to have the explicit dependency from
poi-ooxml on h2 - but I'll go with whatever the consensus is.



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

RE: adding dependencies on h2 and mockito

[Murphy, Mark]

Could the functionality be written to use H2 if it exists in the classpath, but 
stick with the current process if it does not?

-Original Message-
From: Dominik Stadler [mailto:dominik.stad...@gmx.at] 
Sent: Friday, January 26, 2018 5:10 AM
To: POI Developers List 
Subject: Re: adding dependencies on h2 and mockito

Hi,

Mockito for testing is fine for me, H2 as requirement for everybody sounds a 
bit heavy, would we still keep it optional unless somebody actually uses this 
functionality? I.e. if you have Maven/Gradle dependencies it wouldn't be 
dragged in by default?

Thanks... Dominik.

On Fri, Jan 26, 2018 at 9:03 AM, pj.fanning  wrote:

> Are there any objections to me adding dependencies on h2 jar 
> dependency for
> https://github.com/apache/poi/pull/85 and a test dependency on mockito?
> I think mockito would be useful for allowing us to test edge cases.
> An example is  https://svn.apache.org/viewvc?
> view=revision&revision=1822253
> where creating an XSLFTextRun with a null Font Size is not straightforward.
> With mockito, it is very easy to produce such an instance.
>
>
>
> --
> 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
>
>

Re: adding dependencies on h2 and mockito

[Dominik Stadler]

Hi,

Mockito for testing is fine for me, H2 as requirement for everybody sounds
a bit heavy, would we still keep it optional unless somebody actually uses
this functionality? I.e. if you have Maven/Gradle dependencies it wouldn't
be dragged in by default?

Thanks... Dominik.

On Fri, Jan 26, 2018 at 9:03 AM, pj.fanning  wrote:

> Are there any objections to me adding dependencies on h2 jar dependency for
> https://github.com/apache/poi/pull/85 and a test dependency on mockito?
> I think mockito would be useful for allowing us to test edge cases.
> An example is  https://svn.apache.org/viewvc?
> view=revision&revision=1822253
> where creating an XSLFTextRun with a null Font Size is not straightforward.
> With mockito, it is very easy to produce such an instance.
>
>
>
> --
> 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
>
>

adding dependencies on h2 and mockito

[pj.fanning]

Are there any objections to me adding dependencies on h2 jar dependency for
https://github.com/apache/poi/pull/85 and a test dependency on mockito?
I think mockito would be useful for allowing us to test edge cases.
An example is  https://svn.apache.org/viewvc?view=revision&revision=1822253
where creating an XSLFTextRun with a null Font Size is not straightforward.
With mockito, it is very easy to produce such an instance.



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