-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Platform: PC, OS: Linux
When Hudson does a Maven2 build it checks to see if ~/.m2 exists and tries to
create it. If this fails, the build aborts.
In our case we expect each build to have the repository in the workspace and
this check is superfluous. Because Hudson aborts the job anyway, we have created
this directory but removed all access rights. Not a real showstopper for us.
- is related to
-
JENKINS-11843 hudson.maven.RedeployPublisher trying to create ~/.m2 on master to deploy artifacts to Maven repository
- Open