Avoid empty body warnings imposed by default activation of expandEmptyElements

[Pankraz76]

Closes #2519.

[Goooler]

Would you mind adding tests for this?

[Pankraz76]

Would you mind adding tests for this?

no of course not, will impose QA.

[Pankraz76]

missing format. Im used to maven and quarkus fixing itself, not having to run the goal manually.

Can we impose this here as well plz?

Run apply goal, ideally on dev machine only, like we want to do in:

• [core] add IDE agnostic configuration pmd/pmd#5651

[Pankraz76]

is it a feature then, or dont we need convention commits on this?

[jbduncan]

is it a feature then, or dont we need convention commits on this?

Nah, we don't use conventional commits in this project. :)

[jbduncan]

missing format. Im used to maven and quarkus fixing itself, not having to run the goal manually.

Oh, how so? How do Maven and Quarkus do this?

[Pankraz76]

missing format. Im used to maven and quarkus fixing itself, not having to run the goal manually.

Oh, how so? How do Maven and Quarkus do this?

thanks for interest. please see here:

• apply spotlessApply on dev environment #2525
• apply spotlessApply on dev environment #2528
• https://github.com/apache/maven-parent/blob/f4ab7c2eb04865071186c57a263243c72b6e8d52/pom.xml#L1419

[nedtwigg]

I'm not a maven user - does this affect end-user behavior enough that we should note it in the CHANGELOG.md?

[Pankraz76]

Might not be important enough to warrant urgent attention.

On the other hand, many of these cases may now be obsolete, since the Convention over Configuration principle is now fixed and no longer needs to be overridden, from outside.

Ideally, a new build should even fail, given attention that the config has now changed, as the relevant client code is now redundant/wrong:

<expandEmptyElements>false</expandEmptyElements>

https://github.com/apache/maven-parent/blob/f4ab7c2eb04865071186c57a263243c72b6e8d52/pom.xml#L1236

If you want me to add some notes, let me know.