Maven 2 requires write access to a read only default repository ---------------------------------------------------------------
Key: MNG-4575 URL: http://jira.codehaus.org/browse/MNG-4575 Project: Maven 2 & 3 Issue Type: Bug Components: Embedding Reporter: Costin Caraivan We have lots of Maven 2 jobs run by a Hudson CI server, each with a separate repository ("Use private repository" aka maven.repo.local). We decided to see if the separation between builds works as expected - each project gets 1 repository and no other project interferes with it. However, after making the default Maven 2 local repository read only (chmod u-w $HOME/.m2/repository), the builds start crashing. I posted this issue first in the Hudson issue tracker and according to the comments in that issue, it appears that Maven 2 needs write access to the default repository, although it is configured to not use it. In my opinion - this is a bug - why does Maven 2 need to write to: a) a repository where it shouldn't use anyway b) a repository where at most it should read (maybe to set some properties or similar) Here is the relevant issue from the Hudson tracker: http://issues.hudson-ci.org/browse/HUDSON-5751 Since Maven 2.2.1 works with this setting, I presume that it has been fixed, and that it's a bug in the embedded 2.0.4 used by Hudson. Is there any way to have a new release of the Maven embedder for Maven 2? Regards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira