[Bug 65976] java.io.IOException: Your InputStream was neither an OLE2 stream, nor an OOXML stream or you haven't provide the poi-ooxml*.jar in the classpath/modulepath - FileMagic: OOXML, having provi

2022-03-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65976

--- Comment #5 from Andreas Beeker  ---
Are you using gradle from the command line , e.g. "gradle check" or do you try
to build the project via an IDE, which might over optimize a few things?

As the same request, i.e. management asks to build all libraries from scratch,
happened also on the previous release, I wonder how you proceeded when the next
release comes out. I assume that request is based on preventing supply chain
attacks and you might need to do source reviews of POI and its dependencies.
Looks like fighting an uphill battle when you realize how often we update our
dependencies ...

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



Re: Log4j

2022-03-24 Thread Timothy Spear
Ah, then the second line in the link below states POI from 5.1.0 uses log4j
directly left myself and a few other developers confused. Probably should
have just checked the code. Did not think of that until you replied
https://poi.apache.org/components/logging.html

Thanks,

Tim

On Thu, Mar 24, 2022 at 5:00 PM PJ Fanning 
wrote:

> We do use a facade - log4j-api - you can then choose which compatible impl
> to use.
> * log4j-core is one impl
> * log4j-slf4j-impl is an impl that bridges to slf4j -
> https://github.com/pjfanning/poi-gradle-example/blob/main/build.gradle
> uses that bridge and use slf4j-simple as the log framework.
>
> https://poi.apache.org/components/logging.html has extra details.
>
>
>
>
>
>
> On Thursday 24 March 2022, 21:50:13 GMT+1, Timothy Spear 
> wrote:
>
>
>
>
>
> Curious,
>
> I could not find in any ticket, wiki or documentation. Why the switch from
> a facade like SL4J to direct log4j as the logging engine? Going direct to a
> logging engine has caused me module conflicts and classpath problems as
> multiple competing logging engines are required by separate libraries.
>
> A facade such as SLF4J eliminates most of these types of issues.
>
> Tim
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>


Re: Log4j

2022-03-24 Thread PJ Fanning
We do use a facade - log4j-api - you can then choose which compatible impl to 
use.
* log4j-core is one impl
* log4j-slf4j-impl is an impl that bridges to slf4j - 
https://github.com/pjfanning/poi-gradle-example/blob/main/build.gradle uses 
that bridge and use slf4j-simple as the log framework.

https://poi.apache.org/components/logging.html has extra details.






On Thursday 24 March 2022, 21:50:13 GMT+1, Timothy Spear  
wrote: 





Curious,

I could not find in any ticket, wiki or documentation. Why the switch from
a facade like SL4J to direct log4j as the logging engine? Going direct to a
logging engine has caused me module conflicts and classpath problems as
multiple competing logging engines are required by separate libraries.

A facade such as SLF4J eliminates most of these types of issues.

Tim

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



Log4j

2022-03-24 Thread Timothy Spear
Curious,

I could not find in any ticket, wiki or documentation. Why the switch from
a facade like SL4J to direct log4j as the logging engine? Going direct to a
logging engine has caused me module conflicts and classpath problems as
multiple competing logging engines are required by separate libraries.

A facade such as SLF4J eliminates most of these types of issues.

Tim


[Bug 65976] java.io.IOException: Your InputStream was neither an OLE2 stream, nor an OOXML stream or you haven't provide the poi-ooxml*.jar in the classpath/modulepath - FileMagic: OOXML, having provi

2022-03-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65976

--- Comment #4 from PJ Fanning  ---
the `providers: []` means no workbook provider is loaded.

You are probably missing this file:
https://github.com/apache/poi/blob/trunk/poi-ooxml/src/main/resources/META-INF/services/org.apache.poi.ss.usermodel.WorkbookProvider

They are other files like that in poi jar.

An alternative to create an XSSFWorkbook using its constructor instead of 
WorkbookFactory.create

-- 
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 65976] java.io.IOException: Your InputStream was neither an OLE2 stream, nor an OOXML stream or you haven't provide the poi-ooxml*.jar in the classpath/modulepath - FileMagic: OOXML, having provi

2022-03-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65976

--- Comment #3 from PJ Fanning  ---
Dominik - the user built the jar themselves. They are probably missing some
code or config files that appear in the release jar(s). Can't see how this is
our problem.

-- 
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 65976] java.io.IOException: Your InputStream was neither an OLE2 stream, nor an OOXML stream or you haven't provide the poi-ooxml*.jar in the classpath/modulepath - FileMagic: OOXML, having provi

2022-03-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65976

Dominik Stadler  changed:

   What|Removed |Added

   Severity|blocker |major

--- Comment #2 from Dominik Stadler  ---
Reducing severity as only one report for a version that is already released
since some time and is used successfully by many.

-- 
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 65976] java.io.IOException: Your InputStream was neither an OLE2 stream, nor an OOXML stream or you haven't provide the poi-ooxml*.jar in the classpath/modulepath - FileMagic: OOXML, having provi

2022-03-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65976

Dominik Stadler  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #1 from Dominik Stadler  ---
This usually indicates that you are missing some jar-files, especially
poi-ooxml or some other local setup issue.

Can you provide steps/tests which allow to reproduce this as otherwise there is
not much that we can do as it works for us in many other cases.

-- 
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 65976] java.io.IOException: Your InputStream was neither an OLE2 stream, nor an OOXML stream or you haven't provide the poi-ooxml*.jar in the classpath/modulepath - FileMagic: OOXML, having provi

2022-03-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65976

Rakhi Barayanan  changed:

   What|Removed |Added

   Priority|P2  |P1
 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 65976] New: java.io.IOException: Your InputStream was neither an OLE2 stream, nor an OOXML stream or you haven't provide the poi-ooxml*.jar in the classpath/modulepath - FileMagic: OOXML, having

2022-03-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65976

Bug ID: 65976
   Summary: java.io.IOException: Your InputStream was neither an
OLE2 stream, nor an OOXML stream or you haven't
provide the poi-ooxml*.jar in the classpath/modulepath
- FileMagic: OOXML, having providers: []
   Product: POI
   Version: 5.2.0-FINAL
  Hardware: PC
Status: NEW
  Severity: blocker
  Priority: P2
 Component: XSSF
  Assignee: dev@poi.apache.org
  Reporter: rakhi.naraya...@gmail.com
  Target Milestone: ---

java.io.IOException: Your InputStream was neither an OLE2 stream, nor an OOXML
stream or you haven't provide the poi-ooxml*.jar in the classpath/modulepath -
FileMagic: OOXML, having providers: []
at
org.apache.poi.ss.usermodel.WorkbookFactory.wp(WorkbookFactory.java:334)
at
org.apache.poi.ss.usermodel.WorkbookFactory.create(WorkbookFactory.java:224)
at
org.apache.poi.ss.usermodel.WorkbookFactory.create(WorkbookFactory.java:185)
at
com.peoplesoft.pt.psspreadsheet.impl.PSFTWorkBookImpl.(PSFTWorkBookImpl.java:159)
at
com.peoplesoft.pt.psspreadsheet.impl.PSFTWorkBookImpl.(PSFTWorkBookImpl.java:193)
at
com.peoplesoft.pt.psspreadsheet.WorkbookManager.openWorkbook(WorkbookManager.java:207)
cmpolsf.tpsrasetPFSraSetxeto�緬:

We created the poi-ooxml 5.2.0.jar after downloading the source code for Apache
POI from https://svn.apache.org/repos/asf/poi/tags/REL_5_2_0/

We have observed the same error as a regression in
http://people.apache.org/~centic/poi_regression/reportsAll/

Could you please confirm the fix for this is added in the SVN directory.

Please note the destributed binary of poi-ooxml 5.2.0 is not having the issue.
But we need to compile the binary from the source and use it.
So could you please help with the updated code for this exception.

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



Re: poi-ooxml-lite: Check in list of classes and xsb-files to avoid the jar-to-test dependency

2022-03-24 Thread Dominik Stadler
This is committed now, let me know if it causes issues.

Dominik


On Sun, 20 Mar 2022, 16:50 Dominik Stadler,  wrote:

> Hi Devs!
>
> I would like to get some review of a change that I prepared which would
> make working with Apache POI easier (at least for me)
>
> I propose to persist the list of classes/xsbs instead of creating them
> on-the-fly every time the build is executed.
>
> This would then be similar to how we build the Java 9 java/class files.
>
> Let's discuss details at https://github.com/apache/poi/pull/313 where I
> also put a detailed description and pros/cons.
>
> I plan to commit this in a few days if I do not get any "-1" or concerns
> about this change.
>
> Thanks... Dominik.
>


[GitHub] [poi] centic9 closed pull request #313: poi-ooxml-lite: Check in list of classes and xsb-files to avoid the jar-to-test dependency

2022-03-24 Thread GitBox


centic9 closed pull request #313:
URL: https://github.com/apache/poi/pull/313


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



[GitHub] [poi] centic9 commented on pull request #313: poi-ooxml-lite: Check in list of classes and xsb-files to avoid the jar-to-test dependency

2022-03-24 Thread GitBox


centic9 commented on pull request #313:
URL: https://github.com/apache/poi/pull/313#issuecomment-1077392569


   This is applied now via 
https://github.com/apache/poi/commit/09e464bb5f6d8880e79a2beed45760ddfafb62a7


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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