[ http://jira.codehaus.org/browse/MNG-1276?page=comments#action_49889 ]
Jorg Heymans commented on MNG-1276: ----------------------------------- minor nitpick -> "does not appear to be valid" could be shortened to "is invalid" I don't know why you insist on the newlines here : getLogger().debug( "\n\nReason: " + e.getMessage() + "\n\n" ); thanks for looking into this. > warning too verbose for invalid poms > ------------------------------------ > > Key: MNG-1276 > URL: http://jira.codehaus.org/browse/MNG-1276 > Project: Maven 2 > Type: Improvement > Versions: 2.0 > Reporter: Jorg Heymans > Assignee: Edwin Punzalan > Fix For: 2.0.1 > Attachments: MNG-1276-maven-project.patch > > > Basically , per module we get about 10-15 of these flying by : > [WARNING] POM for: 'avalon-logkit:avalon-logkit:pom:2.1' does not appear to > be valid. Its will be ignored for artifact resolution. > Reason: Invalid POM (not v4.0.0 modelVersion) > We have 65 modules, i'm sure you get the picture :-) > see also http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/28826 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
