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

Clark Richey commented on HTTPCLIENT-2181:
------------------------------------------

Well, tell that to the spring boot class loader. My project does NOT import the 
package. It’s pulled in through other dependencies and does cause conflicts on 
the class loader. 

Sent from my iPhone



> packaging commons codes causes conflicts
> ----------------------------------------
>
>                 Key: HTTPCLIENT-2181
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2181
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>    Affects Versions: 4.5.13
>            Reporter: Clark Richey
>            Priority: Major
>
> the direct bundling of org.apache.commons code comes into direct conflict 
> when projects are importing other dependencies that use commons-codes 
> directly. This results in errors like the following:
>  
> _An attempt was made to call a method that does not exist. The attempt was 
> made from the following location:_
> _org.springframework.security.saml2.provider.service.web.Saml2AuthenticationTokenConverter.<clinit>(Saml2AuthenticationTokenConverter.java:49)_
> _The following method did not exist:_
> _'void org.apache.commons.codec.binary.Base64.<init>(int, byte[], boolean, 
> org.apache.commons.codec.CodecPolicy)'_
> _The method's class, org.apache.commons.codec.binary.Base64, is available 
> from the following locations:_
> _jar:file:/E:/Projects/Bee12/bee12-api/build/libs/bee12-api.jar!/BOOT-INF/lib/httpclient-osgi-4.5.13.jar!/org/apache/commons/codec/binary/Base64.class_
>  
> _jar:file:/E:/Projects/Bee12/bee12-api/build/libs/bee12-api.jar!/BOOT-INF/lib/commons-codec-1.15.jar!/org/apache/commons/codec/binary/Base64.class_



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to