After searching the docs and mailing list, I was unable to come up with a way to get Axis2 to stop making what looks like "tmp" versions of all my jars (i.e. axis<somenumber>myjar.jar) in /var/tmp, each time I deploy a new version of my .aar files.
This problem is being multiplied exponentially by multiple developers working on the same host, so if anyone has come up with a handy way of either having axis2 write to, perhaps, /dev/null, or cleaning itself up, or not doing it all, it would be appreciated. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
