Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Trivial
-
Resolution: Fixed
-
Affects Version/s: 1.1-beta-1
-
Fix Version/s: 1.1-rc1
-
Component/s: plugin manager
-
Labels:None
-
Environment:Windows XP, network profile
-
Number of attachments :
Description
Using nework profile with top level directory of the profile without privilege to create new directoriew, makes maven to fail on first startup with a bit cryptic message:
org.apache.maven.MavenException: Unable to extract plugin: C:\Maven 1.1-beta-1\plugins\maven-nsis-plugin-1.1.jar
at org.apache.maven.plugin.PluginManager.unpackPlugin(PluginManager.java:1097)
...
— Nested Exception —
java.io.FileNotFoundException: \\server\username$\.maven\cache\maven-nsis-plugin-1.1\META-INF\MANIFEST.MF (The system cannot find the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at org.apache.maven.util.Expand.extractFile(Expand.java:147)
at org.apache.maven.util.Expand.expandFile(Expand.java:85)
at org.apache.maven.util.Expand.execute(Expand.java:67)
at org.apache.maven.plugin.PluginManager.unpackPlugin(PluginManager.java:1093)
...
The reason for failure is not that plugin is corrupted but that .maven directory can't be created.
Work around is to set MAVEN_HOME_LOCAL to point somewhere in the user space.
We'll try to create the directory before to extract the plugin. If we can't we'll throw a message about it.