You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2024/06/20 06:47:00 UTC
[jira] [Commented] (MNG-8157) Suite file is not a valid file error starting from Maven 3.9.3
[ https://issues.apache.org/jira/browse/MNG-8157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856400#comment-17856400 ]
Tamas Cservenak commented on MNG-8157:
--------------------------------------
What is the failure? Can we get some reproducer? Or it is enough to build jwt with 3.9.3+?
> Suite file is not a valid file error starting from Maven 3.9.3
> --------------------------------------------------------------
>
> Key: MNG-8157
> URL: https://issues.apache.org/jira/browse/MNG-8157
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.9.3
> Reporter: Sergey Beryozkin
> Priority: Major
>
> Starting from Maven 3.9.3, the build fails after a test suite is unpacked with https://github.com/smallrye/smallrye-jwt/blob/8e926f01755c185151934293c405c1cf733f2aa3/testsuite/tck/pom.xml#L100-L125.
> In this case, `/testsuite/tck/target/tck-suite/suites/tck-base-suite.xml` is reported to be invalid.
> Assuming that is is due to a stricter verification now being enforced: it will be quite hard (time consuming due to the specification release process constraints) to release the next version of the related test jar which would contain some extra XML directives in that file. In this case, if possible, having an option for to disable the strict verification of the unpacked resources would be great.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)