I'm a schema newbie, and I've done a lot of the changes to the xsd file, hence it's fairly basic.
The plan for the <extends> case was to change pom:validate to check if the pom extended another, combine them and produce a new .xml file to be validated. -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au Incze Lajos <[EMAIL PROTECTED]> wrote on 03/06/2003 10:42:20 PM: > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
