Konstantin Priblouda wrote: > This will not help for certain plugins - like release > - its hardwired to ibiblio... at least for resolving > snapshots.
This apparently needs fixing. There are more shortcomings to the deploy plugin though. In the future, there should be support for various deployment mechanisms including local filesystem, ftp, http (webdav), scp (the current method). We need to develop a mechanism for publishing artifacts without human interaction, but with strong security mechanism. An idea from the top of my head is delivering artifact + it's descriptor (including publishing organization's signature) with one of the aforementioned mechanisms to an 'incoming' directory. There would be a cron job running on the repository machine that would pick up incoming artifacts, verify the signatures using organizations' public keys stored in the repo and move artifacts into their proper place. R. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
