I'm about to roll out Maven as *the* build tool for a large company that uses ClearCase. We have to store Maven (core + plugins) in ClearCase, and that brings up some problems:
For the users, ClearCase behaves as a read-only file system. Plain users will not be able to modify or create files in the place where we plan to store Maven (in a ClearCase VOB). I have been able to hack the driver.properties file so that the local repository is built on the regular hard drive of each developer's machine, and not next to the plugins dir. Something like this: c:\ +--maven +--repository z:\ (ClearCase) +--maven +--plugins This separation works fine. However, I still have a problem, because Maven wants to write the various *.cache files in the same folder as the plugins. That fails, since everything under z:\ here is read-only. What I would like to see is an option to override where cache files should be written and read. I want them in c:\maven. In order to add support for this to Maven I have figured two things are needed: 1) A new get/setCacheDir() in PluginCacheManager. 2) A new property in driver.properties This is a rather small patch that I can contribute. -But I'd like to hear what others think about it first. Cheers, Aslak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
