[ http://jira.codehaus.org/browse/MNG-229?page=all ] Kenney Westerhof reopened MNG-229: ----------------------------------
Doesn't work in the following case: - settings.xml defines a custom repository, hosting a plugin (id=central2-plugins, snapshots enabled) - settings.xml defines another custom repository (id=central2, snapshots enabled)(actually the same), hosting that plugins dependencies. - the plugin is a snapshot - it's dependency is also a snapshot the plugin gets resolved, but its dependencies don't. The ResolutionException only specifies repo1.maven.org. It should also have the repo specified in the settings.xml. Even with the custom repo specified, and the plugin already in the local repo, that remote repo isn't searched for the dependency. I've tried to get a testcase setup using a file:// repo but even though the artifacts exists there, they aren't found. (tried relative/absolute paths, all kinds of file:, file:/, file://, file:///...) > plugin repository separation mixup > ---------------------------------- > > Key: MNG-229 > URL: http://jira.codehaus.org/browse/MNG-229 > Project: Maven 2 > Type: Bug > Components: maven-core > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 2.0-beta-1 > > > currently, dependences of plugins are resolved from the list of plugin > repositories. This is most likely incorrect, and only works because it > happens to be the same. -- 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]
