[jira] Commented: (MNG-1954) Need better handling of malformed poms in local cache, like check for an update every run

2006-03-15 Thread ruel loehr (JIRA)
[ http://jira.codehaus.org/browse/MNG-1954?page=comments#action_61170 ] ruel loehr commented on MNG-1954: - Agreed, this is a problem. A user shouldn't have to wipe out things in his repo to get a pom update. Another possible use case: A user runs

[jira] Commented: (MNG-1954) Need better handling of malformed poms in local cache, like check for an update every run

2006-03-17 Thread ruel loehr (JIRA)
[ http://jira.codehaus.org/browse/MNG-1954?page=comments#action_61410 ] ruel loehr commented on MNG-1954: - I made a patch which resolves the above issue. When the defaultArtifactResolver is handed an artifact to resolve, if that artifact is already located

[jira] Commented: (MNG-1954) Need better handling of malformed poms in local cache, like check for an update every run

2006-07-05 Thread Carlos Sanchez (JIRA)
[ http://jira.codehaus.org/browse/MNG-1954?page=comments#action_68994 ] Carlos Sanchez commented on MNG-1954: - This patch has a lot of formatting changes that doesn't make it very readable. > Need better handling of malformed poms in local cache, like ch

[jira] Commented: (MNG-1954) Need better handling of malformed poms in local cache, like check for an update every run

2007-06-05 Thread Brett Porter (JIRA)
[ 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. H