RE: Apache POI 4.0/Java 8 - new packages?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

RE: Apache POI 4.0/Java 8 - new packages?

Allison, Timothy B.
Speaking of new packages...  It looks like there's some interest in moving Tika's mostly bean free/pure-SAX extractors for pptx/docx to POI.  What would people think of having an entirely bean-free ooxml extraction-only module; this could allow for a very lightweight module.  Downside is potential duplication of code, with current codebase, of course...

How would this play with: the newer XMLBeans version in https://github.com/pjfanning/xmlbeans/releases/tag/2.6.2 ?

-----Original Message-----
From: Murphy, Mark [mailto:[hidden email]]
Sent: Friday, September 15, 2017 8:12 AM
To: 'POI Developers List' <[hidden email]>
Subject: RE: Apache POI 4.0/Java 8

Here is a somewhat radical idea, and maybe too hard to implement, but maybe we should package this a bit differently like poi-core, poi-ss, poi-wp, poi-misc. And then apply semantic versioning to each package separately so poi-core and poi-ss would be at 4.0.0 and poi-wp and poi-misc might still be at 0.4.0 as they are still experimental. I know that the binary formats are ahead of the xml formats in the wp world, so maybe this would still need to be thought out. I wouldn't want too many packages.

-----Original Message-----
From: Allison, Timothy B. [mailto:[hidden email]]
Sent: Friday, September 15, 2017 7:07 AM
To: POI Developers List <[hidden email]>
Subject: RE: Apache POI 4.0/Java 8

Thank you, Dominik!!!

So, speaking of 4.0...should we move to semantic versioning: 4.0.0?

-----Original Message-----
From: Dominik Stadler [mailto:[hidden email]]
Sent: Thursday, September 14, 2017 1:39 PM
To: POI Developers List <[hidden email]>
Subject: Apache POI 4.0/Java 8

Hi,

FYI, as 3.17 is out and we agreed to work on 4.0/Java 8 now, I have done a bunch of changes locally which switch to Java 8 and 4.0 and also use some newer third party libs. I would like to do some more local testing on it and then commit it tomorrow.

Just FYI so we don't duplicate efforts here.

Dominik.
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB��[��X��ܚX�KK[XZ[
�]�][��X��ܚX�P�K�\X�K�ܙ�B��܈Y][ۘ[��[X[��K[XZ[
�]�Z[�K�\X�K�ܙ�B�B

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Apache POI 4.0/Java 8 - new packages?

Murphy, Mark
The thing that I see that most caused code duplication is that we read and process individual formats HSSF, XSSF, HWPF, XWPF, as is rather than having a reader that converts the format to POJOs, and a writer to convert the POJOs to the desired format. This causes the user code to be fairly tightly coupled to the format, and makes it hard to implement new formats. Note that we are still using the first edition OOXML spec because upgrading to the most recent edition is too disruptive.

-----Original Message-----
From: Allison, Timothy B. [mailto:[hidden email]]
Sent: Friday, September 15, 2017 9:04 AM
To: POI Developers List <[hidden email]>
Subject: RE: Apache POI 4.0/Java 8 - new packages?

Speaking of new packages...  It looks like there's some interest in moving Tika's mostly bean free/pure-SAX extractors for pptx/docx to POI.  What would people think of having an entirely bean-free ooxml extraction-only module; this could allow for a very lightweight module.  Downside is potential duplication of code, with current codebase, of course...

How would this play with: the newer XMLBeans version in https://github.com/pjfanning/xmlbeans/releases/tag/2.6.2 ?

-----Original Message-----
From: Murphy, Mark [mailto:[hidden email]]
Sent: Friday, September 15, 2017 8:12 AM
To: 'POI Developers List' <[hidden email]>
Subject: RE: Apache POI 4.0/Java 8

Here is a somewhat radical idea, and maybe too hard to implement, but maybe we should package this a bit differently like poi-core, poi-ss, poi-wp, poi-misc. And then apply semantic versioning to each package separately so poi-core and poi-ss would be at 4.0.0 and poi-wp and poi-misc might still be at 0.4.0 as they are still experimental. I know that the binary formats are ahead of the xml formats in the wp world, so maybe this would still need to be thought out. I wouldn't want too many packages.

-----Original Message-----
From: Allison, Timothy B. [mailto:[hidden email]]
Sent: Friday, September 15, 2017 7:07 AM
To: POI Developers List <[hidden email]>
Subject: RE: Apache POI 4.0/Java 8

Thank you, Dominik!!!

So, speaking of 4.0...should we move to semantic versioning: 4.0.0?

-----Original Message-----
From: Dominik Stadler [mailto:[hidden email]]
Sent: Thursday, September 14, 2017 1:39 PM
To: POI Developers List <[hidden email]>
Subject: Apache POI 4.0/Java 8

Hi,

FYI, as 3.17 is out and we agreed to work on 4.0/Java 8 now, I have done a bunch of changes locally which switch to Java 8 and 4.0 and also use some newer third party libs. I would like to do some more local testing on it and then commit it tomorrow.

Just FYI so we don't duplicate efforts here.

Dominik.
B KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB  [  X  ܚX KK[XZ[
 ] ][  X  ܚX P K \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[
 ] Z[ K \X K ܙ B B

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]