[ http://jira.codehaus.org/browse/MNG-461?page=comments#action_40943 ] Brett Porter commented on MNG-461: ----------------------------------
on the first statement - currently we create dummy poms in the repo anyway, so this wouldn't be any different. I don't quite understand the second point. If it is not found, then it would be faked, if it was found it would be used. It's going to be consistent across environments. The main problem is that it would have to check for it every time, or write a local copy of the fake pom, which would yield the situation you talked about. However, we already have that situation when we fix metadata in the remote repository, so maybe that is ok and we need focus on a way of getting that updated (maybe a confidence level on a POM that dictated whether it got update checks even if it weren't a snapshot), or just encourage a pom flush from the local repo regularly? > warn, but don't fail, on a missing POM in the repository > -------------------------------------------------------- > > Key: MNG-461 > URL: http://jira.codehaus.org/browse/MNG-461 > Project: Maven 2 > Type: Improvement > Components: maven-artifact > Reporter: Brett Porter > > -- 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]
