[ http://jira.codehaus.org/browse/MNG-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4491. ---------------------------------- Resolution: Won't Fix Assignee: Benjamin Bentmann Invalid = existent but unusuable, for any more details the debug log can be consulted. > Maven3 reports warnings about POM problems in very spurious way > --------------------------------------------------------------- > > Key: MNG-4491 > URL: http://jira.codehaus.org/browse/MNG-4491 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Errors > Affects Versions: 3.0-alpha-5 > Reporter: Tamás Cservenák > Assignee: Benjamin Bentmann > > In relation to issue MNG-4490, Maven3 reported the following on CLI: > {noformat} > [WARNING] Invalid artifact metadata for > org.sonatype.nexus:nexus-proxy:jar:1.4.1-SNAPSHOT, transitive dependencies > (if any) will not be available, enable debug logging for more details > {noformat} > This is due to the issue above (the branch i worked on completely revamped > the dependencies in aggregator poms, hence the module pom became "invalid", > since it contained dependencies that would be "filled in" from dependency > management section, but they were not, hence by Maven3 they were considered > "invalid"). > What I was thinking, that maybe we should distinguish between "corrupt" POMs > in way like: > * syntactical broken, which is like unparseable POM (usually corrupted during > transport or proxy issues) > * semantically broken -- this is what Maven3 tried to tell me -- a POM that > was not "correct" in validation sense (in this case, depepndency had no > "version" declared) -- 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