> -----Original Message----- > From: Rafal Krzewski [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 30, 2003 6:42 PM > To: Maven Users List > Subject: Re: Two requests > > > Joshua Spiewak wrote: > > > I was wondering if the latest Jakarta Taglibs standard/jstl jars > > (version 1.0.3) could be uploaded to ibiblio. > > The procedure of upload requests is described in Maven docs, can't > remember where though. Try you luck with site search. > > > Also, is there any plan for site:deploy to be able to use ftp? My web > > host company does not give me shell access, so I will either > need to ftp > > by hand, or if no one is currently working on ftp perhaps I can > take it up. > > FTP and few other deployment methods are implemented in the 'artifact' > plugin. Plugging them into 'jar' and site 'plugins' should be really > straightforward task, but Michal (the author of artifact plugin) decided > (or was told to) to wait until the deployers get some amount of testing > through war/ear plugins.
There is one more issue to which I want to resolve before I would use this plugin for deploying sites: I want to make smarter SCP deployer which after receiving a list of files to deploy will : a) create a zip file (locally) b) deploy c) unzip (remotely) This can be completely transparent (internally hidden in SCP/SSH deployer) but will result is huge improvement of performance (usual instead of coping MB it will just copy KB) This is pretty much the same what site:deploy goal does . This should be rather simple to implement (hope to this during weekend) But surly this will be supported only by SCP deployer. >I don't know how long are these tests about > to last. AFAICT no problems with war/ear deployments were reported > lately - either because they work perfecly, or nobody uses them. > could be second option :) What I really need to finish artifact plugin are Windows/(Li/U)nix scripts. I want to have scripts which a) open SSH tunnel/session (1st script) b) start maven session which will deploy c) maven will deploy using SSH session open in step a) (2nd script) So authentication is done completely outside maven ( I have class which I call External Deployer for that) This is needed by those who don't want to compromise their security by keeping passwords in open text (forget please about the fact that FTP/HTTP/PROXY authentication is not secure at all) If somebody ___HAS__ such scripts ....I will have more time to read books during weekends (so maybe I will be a bit smarter...) I had very many ideas how to make it simple and secure but non of them was any good I doubt if such solution exists. E.g. I was thinking about something like password store which will be similar to java key store but will keep all the passwords which maven might need. This store will be protected by one password (maybe even by session passwords like in banks? :) ) But back to reality ... the key requirement for me is to make this process a) secure b) automated ( no human interaction is needed so e.g. continuous integration system can do the work) At the moment I fail to see a possibility of implementing it without using long-living processes or external security infrastructure. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
