Hi, I figured as this has come up I would provided a little background on symlinks and Ibiblio.
First, there is generally some confusion relating to the deploy goals. This stems from lack of documentation but the default goals were really only ever intended for our purposes of pushing artifacts to ibiblio. There is a taglib which includes a <deploy:artifact/> tag which can be used for general artifact deployment using ssh and to the file system. But in these default goals are the use of symlinks. We do this out of courtesy when using Ibiblio because they archive everything on the face of the planet and there is no reason to duplicate artifacts when a symlink does the trick. This may not be suitable for your situation but it suits out purposes when deploying to ibiblio. There are at about 5 TB of storage so we don't need to be duplicating everything. There are some java ssh, ftp and httpclient deployers coming and in conjunction with some docs on the deployment taglib you will basically be able to deploy in any fashion you like. We can probably work together to make a flexible deployment taglib for general repository population but again this is not to be confused with what we use to populate the central repository. I'm sorry for this confusion but the deploy taglib went in undocument and the defaults never should have been the one's for ibiblio. I'll try to clean this up asap and certainly before the 1.0 release which I hope will be inside of 8 weeks. -- 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]
