[
https://issues.apache.org/jira/browse/COMPRESS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923722#comment-17923722
]
Hiren Babariya commented on COMPRESS-694:
-----------------------------------------
[~ggregory] thanks for your response. However, the solution you provided seems
to address a different issue than the one I'm facing. I’ve attached file the
full dependency tree for reference.
Apologies for my mistake—I accidentally mentioned version *1.27.2* in the
ticket instead of {*}1.27.1{*}.
Could you please suggest a *compatible version* of {{commons-compress}} that
works well with *Spring Boot 3.3.4* and is {*}free from known
vulnerabilities{*}?
> java.lang.NoSuchMethodError: ZipArchiveOutputStream.putArchiveEntry
> --------------------------------------------------------------------
>
> Key: COMPRESS-694
> URL: https://issues.apache.org/jira/browse/COMPRESS-694
> Project: Commons Compress
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.21, 1.22, 1.25.0, 1.26.0, 1.26.1, 1.26.2, 1.27.1
> Environment: On local and server also
> Reporter: Hiren Babariya
> Priority: Major
> Attachments: Screenshot 2025-02-04 at 4.30.21 PM.png, compress Error
> bootjar.txt
>
>
> while spring boot upgrade 3.1.7 to 3.3.51 , I am facing below issue while
> building jar
> Errors :
> > Task :bootJar FAILED == FAILURE: Build failed with an exception. * What
> > went wrong: Execution failed for task ':bootJar'. > 'void
> > org.apache.commons.compress.archivers.zip.ZipArchiveOutputStream.putArchiveEntry(org.apache.commons.compress.archivers.zip.ZipArchiveEntry)'
> Caused by: java.lang.NoSuchMethodError: 'void
> org.apache.commons.compress.archivers.zip.ZipArchiveOutputStream.putArchiveEntry(org.apache.commons.compress.archivers.zip.ZipArchiveEntry)'
>
> Dependancy use -
> implementation 'org.apache.commons:commons-compress:1.26.0' or
> implementation 'org.apache.commons:commons-compress:1.26.2' or
> implementation 'org.apache.commons:commons-compress:1.27.2'
> 1.21 , 1.22 . 1.25.0 also same issue facing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
