You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Required fields lead to non required element in XSDΒ #162
The reason for this behaviour seems to be driven by pom.xml specifics, i.e. POMs are merged with their parents before they need to be valid. As this is definitely an edge case Modello should have a flag for enabling/disabling that behaviour.
By default it is reasonable to assume that the XML is not requiring post-processing before validating it against the schema.
The reason for this behaviour seems to be driven by pom.xml specifics, i.e. POMs are merged with their parents before they need to be valid. As this is definitely an edge case Modello should have a flag for enabling/disabling that behaviour. By default it is reasonable to assume that the XML is not requiring post-processing before validating it against the schema.
Activity
michael-o commentedon Jan 9, 2022
Please link the spot in question. I have provided it in the JIRA issue.
kwin commentedon Jan 9, 2022
This seems to be caused by
modello/modello-plugins/modello-plugin-xsd/src/main/java/org/codehaus/modello/plugin/xsd/XsdGenerator.java
Lines 245 to 247 in 8467ab8
kwin commentedon Oct 18, 2022
The reason for this behaviour seems to be driven by pom.xml specifics, i.e. POMs are merged with their parents before they need to be valid. As this is definitely an edge case Modello should have a flag for enabling/disabling that behaviour.
By default it is reasonable to assume that the XML is not requiring post-processing before validating it against the schema.
michael-o commentedon Oct 18, 2022
I fully agree with that.
Optionally enforce required elements in XSDs
Optionally enforce required elements in XSDs (#263)