The real POM has to be checked against a schema, that's sure. If we want to check also the generated model I'm ok with that, but as a new feature (sanitity test).
On 10/6/05, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > I am a bit sceptical about that. I don't know in detail how the > PomRewriter class works but it constructs a new pom from a maven model. > That means it gets transformed on the way, I did a few tests and noticed > that attributes get stripped, the order of elements changed, ...? > > It would be safer to have a simple node-by-node merge of xml files, I > don't know if there exists a convenient tool for this. > > > But then, with a merged pom it would be hard to track errors since we > don't know where a particular error came from... > > Any thoughts? > > Lukas > > > > Arnaud HERITIER wrote: > > Actually, it's the real POM which is tested, thus it's not possible to add > > a minimum set of elements. > > But I just finished to commit a new tag in the artifact plugin which allow > > to generate an aggregated pom which resolves inheritence, > > jelly variables, versions override, and we could use it to test the POM. > > > > WDYT ? > > > > Arnaud > > > > > --------------------------------------------------------------------- > 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]
