> Sorry, I obviously wasn't clear enough. The problem is that the current > maven-project.xsd is really too strict for project.xml files that use > <extend>: if you're extending another project.xml there are elements > that the schema says are required that you really want to pull in from > the <extend>ed project.xml.
The XSD is rich enough to express the situation: if you have an <extends> tag then some elements become optional. It's clear that if the parent POM was valid, the child POM will be valid, too even if it was virtually empty. So, the solution seems to branch the POM XSD at <extends>, making the required elements optional in the extends tag present branch. incze --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
