[
https://issues.apache.org/jira/browse/MNG-8157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872359#comment-17872359
]
Tamas Cservenak commented on MNG-8157:
--------------------------------------
Try to add classifier=tests and type=jar? As I see this is a problem in
m-dep-p... but what changed that triggered this?
> 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)