Am 2023-08-02 um 18:49 schrieb Delany:
Listed as "won't do"
https://issues.apache.org/jira/browse/MNG-5773
Is it possible as a future XSD change, or should I rather pursue an
enforcer rule? Or both?
Maven does not use the schema to validate the POM content. This is done
in Java. If you can pr
Listed as "won't do"
https://issues.apache.org/jira/browse/MNG-5773
Is it possible as a future XSD change, or should I rather pursue an
enforcer rule? Or both?
Delany
On Wed, 2 Aug 2023 at 18:22, Michael Osipov wrote:
> This is known, search JIRA and Plexus issue trackers.
>
>
This is known, search JIRA and Plexus issue trackers.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Great question!
Please create a JIRA to not have this lost and forgotten... and assign it
to some upcoming 4.x version, so we for sure stumble upon it down the road.
Maven 3.x will probably remain unchanged in this aspect.
T
On Wed, Aug 2, 2023 at 3:49 PM Delany wrote:
> When will the https://m
When will the https://maven.apache.org/pom.html schema be up for
modification?
I notice that a duplicate property made its way into one of my pom.xml
Can often happen when resolving conflicts.
42.5.0
42.6.0
...
Since XML allows this, as does the schema, the enforcer plugin has no rule
fo
