Re: POM parser in 1.1+1 for me too! I was under the impression that hopefully these types of problems would be automatically fixed when bumping the version? Same for changing to the <artifactId/> and <groupId/> structure as well?
Eric -----Original Message----- From: Trygve Laugst�l [mailto:[EMAIL PROTECTED] Sent: Saturday, September 18, 2004 3:03 PM To: Maven Developers List; [EMAIL PROTECTED] Subject: Re: POM parser in 1.1 On Sat, Sep 18, 2004 at 04:27:33PM +1000, Brett Porter wrote: > I'm working on replacing the POM parser in Maven 1.1, and POMS that > previously parsed with things like this: > <resources> > <resource> > <directory>../../../../src/messages</directory> > <includes>**/*.properties</includes> > </resource> > </resources> > Now fail because the includes format is not legal. It should be: > <includes> > <include>**/*.properties</include> > </includes> > > Anyone have a strong objection to these POMs no longer parsing? As this > is probably a common error (it's in the m1 test cases :), that silently > failed before, we can address it in an FAQ. +1 for the change. It should be pretty easy to make a better POM validator/fixer. There is quite a few issues with the existing poms that should be adressed and tried fixed with a better validator. This will also help pom version migration. -- Trygve > > - Brett > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
