apache / apache/maven

[MNG-8157] Suite file is not a valid file error starting from Maven 3.9.3

Open
#10,605 5 comments 0 reactions 0 assignees View on GitHub
bug priority:major
Dominant language
Java
Stars
5.3k
Forks
3.1k
Avg merge
20h 42m
Merged PRs (30d)
297

Description

**[Sergey Beryozkin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=sergey_beryozkin)** opened **[MNG-8157](https://issues.apache.org/jira/browse/MNG-8157?redirect=false)** and commented

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.

---

**Affects:** 3.9.3

Contributor guide

Open the contributing guide

Research direction

Start with the referenced testsuite/tck/pom.xml lines 100-125 and reproduce the failure with Maven 3.9.3 against the unpacked tck-base-suite.xml. Trace where the unpacked resource is validated, then define and verify an option that disables strict verification for these resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.