This isn't a hard and fast rule, but we generally like to see that the entire enclosure is available on Central. You would need to introduce not just the pluginRepo, but probably a regular repo and that's where problems start. That repo then pollutes the downstream resolution for other artifact lookups and this is what causes people problems.
-----Original Message----- From: Peter Niederwieser [mailto:pnied...@gmail.com] Sent: Thursday, April 02, 2009 8:55 AM To: users@maven.apache.org Subject: Why are projects deploying to repo1.maven.org not allowed to use plugins from other repositories? Say I need a plugin for my release process that's not available from repo1.maven.org. How would the inclusion of a plugin repository affect the users of my artifact? Or why else is it not allowed to add a plugin repository? Cheers, Peter -- View this message in context: http://www.nabble.com/Why-are-projects-deploying-to-repo1.maven.org-not- allowed-to-use-plugins-from-other-repositories--tp22847197p22847197.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
