Zitat von "Mark H. Wilkinson" <[EMAIL PROTECTED]>: > 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.
Exactly that's my problem... > [..] > > So the solution is probably to relax the XML Schema to specify the > minimum requirements for a project.xml file to be syntactically valid as > a self-contained unit, then to apply the remaining validation rules to > the internal project model using Java code once the <extend> has been > processed. Possibly alternatively one could extend the XML to have a _top-level_ <extend> tag instead of a top-level <project> and then have two schemas for the two different situations. But maybe this requires too much changes inside maven... Martin ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
