<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 11, 2012, at 2:13 PM, ceki wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br><br>On 11.03.2012 19:38, Les Hazlewood wrote:<br><blockquote type="cite">Hi Ceki,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Would you be open to using a Nexus repository manager built for this<br></blockquote><blockquote type="cite">kind of stuff (granting/removing access, promoting artifacts to Maven<br></blockquote><blockquote type="cite">Central when you specify), etc?<br></blockquote><br>Hi Les,<br><br>The current approach where artifacts are pushed during 'mvn deploy' to<br>a private repo and then having Maven Central automatically pickup<br>changes is an *automated*, simple and very convenient process. I would<br>not want to change in favor of a process with no identified upside<br>(assuming shell accounts are needed for integrating with the<br>web-site anyhow).<font class="Apple-style-span" color="#007429"><br></font></div></blockquote><br></div><div><div>You might want to look at how the ASF's Nexus repo works if you haven't already. Projects do a mvn deploy to a staging repository and then after it is reviewed Nexus "publishes it" to its live repository where Maven Central then retrieves it. Specific user's can have permissions for only specific repositories within Nexus.</div><div><br></div><div>Ralph</div></div></body></html>