[ 
https://issues.apache.org/jira/browse/PDFBOX-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17772266#comment-17772266
 ] 

Andreas Lehmkühler commented on PDFBOX-5687:
--------------------------------------------

[~rombert] You missed the following one in 
{{org.apache.pdfbox.pdmodel.encryption.SecurityProvider.getProvider()}}
{code}
               Class<Provider> providerClass = (Class<Provider>) Class
                        
.forName("org.bouncycastle.jce.provider.BouncyCastleProvider");
{code}
I've removed it as well, see PDFBOX-5693 for further details

> PDFBox 3.0 OSGi bundle requires sun.java2d.cmm.kcms package
> -----------------------------------------------------------
>
>                 Key: PDFBOX-5687
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-5687
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 3.0.0 PDFBox
>            Reporter: Robert Munteanu
>            Assignee: Andreas Lehmkühler
>            Priority: Major
>             Fix For: 3.0.1 PDFBox, 4.0.0
>
>
> We consume PDFBox in the Apache Sling project and recently attempted to 
> upgrade to 3.0.0 . Sling uses OSGi and a new required import appeared in the 
> 3.0.0 bundles: sun.java2d.cmm.kcms .  Our PR is at 
> https://github.com/apache/sling-org-apache-sling-starter/pull/212 .
> This prevents us from on applying the update. I looked at the desired usage 
> for kcms and it seems like it is an optional feature.
> I suspect this addition was triggered by a version update of the 
> maven-bundle-plugin, which added support for transforming "Class.forName" 
> calls as OSGi package imports - 
> https://bnd.bndtools.org/instructions/noclassforname.html .
> I would suggest that this import is removed by disabling the specified bnd 
> instruction.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to