Once a pom for a dependency has been copied to the local repo, it is never updated.
For those of you who maintain a company internal repo, do you ever have the situation where a dependency pom in your internal repo differs from the corresponding pom in the public repo? (e.g. you want to record additional info such as license information, or the public pom is not correctly defined). The problem I see is that it is difficult to ensure that a user is using the correct pom. For example, if a user downloads maven, builds something with it, his local repo gets populated. Then, if the user tries to build my app, and I have defined a thirdparty pom in my own internal repo that differs from the public one, the original public version will be used (even if my app includes a maven distro and a settings.xml specifying my own repo). Any ideas on how to work around this? I feel like I need control over the repo, but cannot ensure that the user hits my repo first. Appropriate jira issue is here: http://jira.codehaus.org/browse/MNG-1954 Ruel Loehr JBoss QA --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
