[ 
http://jira.codehaus.org/browse/MNG-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98547
 ] 

Brett Porter commented on MNG-1954:
-----------------------------------

agree checking every time is bad, but we should be dealing with malformed POMs 
better. Happy to leave this specific one closed and leave it as an 
architectural goal for maven-artifact

> Need better handling of malformed poms in local cache, like check for an 
> update every run
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-1954
>                 URL: http://jira.codehaus.org/browse/MNG-1954
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0
>            Reporter: Steve Loughran
>             Fix For: 2.1.x
>
>         Attachments: MNG-1954.txt
>
>
> If a pom has a typo in it, it is downloaded and parsed with a (misspelled) 
> error message printed
> [m2:libraries] [WARNING] POM for 
> 'org.hibernate:hibernate-tools:pom:3.1.0.beta2' is invalid. It will be 
> ignored for artifact resolution. Reason: Parse error reading POM. Reason: 
> expected > to finsh end tag not < from line 7 (position: TEXT seen 
> ...</dependency>\r\n  </dependencies\r\n<... @29:2) 
> but if the pom is corrected in the source repository, the local system doesnt 
> check for a change, it just goes with what is there.
> Invalid pom files should be remembered and replacements looked for, because 
> there is no value in retaining them. 

-- 
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

        

Reply via email to