We have a private central repository on our network that engineers are allowed to contribute to. They can contribute both their own artifacts as well as third-party artifacts that they feel would be useful to others. In the latter case, they simply ftp to the repository, create the necessary folders and put the necessary files. Recently, I configured Maven to deploy a jar to a group folder created by another person. There were no group/other write perms on that folder. When it got to removing the old pom file, I expected to get Permission Denied and Build Failed. Instead, it simply stopped.
So I have two questions. 1) Is this a bug? 2) My real problem is permissions, so should I just change everyone's umask to give group write perms, or is there a better practice someone knows of? Yoway Buorn Software Engineer Imagery Systems Engineering GENERAL DYNAMICS Advanced Information Systems "Cockfighting has always been my idea of a great sport- two armed entr�es battling to see who'll be dinner." -- P.J. O'Rourke
