On Tue, 2003-02-18 at 04:59, Rafal Krzewski wrote: > 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).
I actually have a Java-based ssh2, FTP and HTTP (using httpclient) deployers. They got lost in the plugin shuffle done a couple weeks ago but they will definitely go back in. I'm also working on deployment to maven.org so that any project can deploy to the repository (not directly, but the artifacts will make their way there). > 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. Yup, all in the works. For some time actually. > > R. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
