stevenschlansker commented on issue #11760: URL: https://github.com/apache/maven/issues/11760#issuecomment-4111768579
I struggled to find any documentation on `combine.children` in the first place, and `mvn:combine.children` seems to be even less documented. I based the original change on some generated AI slop - but of course I then verified the answer seemingly accurately describes the behavior. I wish I could point to the Maven 4 docs describing this change but I never found anything authoritative looking. AI slop below, which appears to be true to the best of my admittedly limited Maven abilities: > It sounds like you've run into one of the "clean-up" hurdles in the transition to Maven 4. While Maven 3 was fairly forgiving with custom attributes like combine.children, Maven 4 has tightened the screws on XML validation to ensure the POM stays predictable. >The short answer is: Maven 4 has moved these merging instructions into a specific namespace. > In Maven 3, combine.children and combine.self were "magical" attributes handled by the underlying Plexus configuration. In Maven 4, the parser expects the POM to follow a stricter schema. If it sees an attribute it doesn't recognize (like combine.children), it throws a validation error. The Solution: Use the Maven 4 Namespace > To fix this, you must add xmlns:mvn="http://maven.apache.org/POM/4.0.0"; and change the attribute to mvn:combine.children. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
