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

Andreas Lehmkühler resolved PDFBOX-5446.
----------------------------------------
    Resolution: Fixed

I thought for a long time about what solution to take.

On one hand there wasn't any implementation of RandomAccessWrite but the one 
which was moved and on the other hand this implementation is used for 
COSStreams only.

I've decided to choose the easy way and to move everything to the new package 
instead of creating a new java package such as {{org.apache.pdfbox.cos.io}}. 
I'm thinking about removing or replacing the scratchfile stuff with something 
different. But that's not on my 3.0.0-TODO list.

[~axh] thanks again for the report

> Split package org.apache.pdfbox.io
> ----------------------------------
>
>                 Key: PDFBOX-5446
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-5446
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 3.0.0 PDFBox
>            Reporter: Axel Howind
>            Assignee: Andreas Lehmkühler
>            Priority: Major
>             Fix For: 3.0.0 PDFBox
>
>
> Recently a new Maven module 'io' has been created to remove duplicated code. 
> This module contains the package 'org.apache.pdfbox.io'. However, the 
> 'pdfbox' module also contains classes in the same package. This makes it 
> impossible to use pdfbox in a modularized (Jigsaw) project since it is 
> forbidden to have packages split between different modules and produces the 
> following error:
> {noformat}
> the unnamed module reads package org.apache.pdfbox.io from both 
> org.apache.pdfbox and org.apache.pdfbox.io
> {noformat}
> The remaining classes in said üackage should also be moved to the new 'io' 
> module to solve this.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Reply via email to