This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version = NetBeans IDE Dev (Build 201306112301) Operating System = Windows 8 version 6.2 running on amd64 Java; VM; Vendor = 1.7.0_21 Runtime = Java HotSpot(TM) 64-Bit Server VM 23.21-b01 In our institute, we use windows, with profiles and user dirs stored on a file server. Till NB 7.3.1 (dev), this had be no problem. But with the current development version, almost everything is a mess: Cpuld not install as standard user (issue 230809). Could not create a project on unc path (workarround: use local path) And now, cannot create maven projects, because NB cannot access the local repo any more: cd D:\Projects\TestJSF; "JAVA_HOME=C:\\Program Files\\Java\\jdk1.7.0_21" "\"C:\\Program Files\\NetBeans Dev 201306112301\\java\\maven\\bin\\mvn.bat\"" --non-recursive clean Could not create local repository at \\Fileserver1\User$\muellermi\.m2\repository -> [Help 1] To see the full stack trace of the errors, re-run Maven with the -e switch. Re-run Maven using the -X switch to enable full debug logging. For more information about the errors and possible solutions, please read the following articles: [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LocalRepositoryNotAccessibleException
Created attachment 135664 [details] IDE log
I just downloaded final 7.3.1: No such problem. Hopefully this can be solved in Dev (current Build 201306112301) soon.
\\Fileserver1\User$\muellermi\.m2\repository is a correct path? Especially the User$ part.. also does your 7.3 build use the same JDK and maven? there have been quite a few Runtime.exec()/ProcessBuilder related security fixes in jdk 7u21 and that's what appears to be manifesting here as well.. because the error comes from the maven JVM that we spawn using ProcessBuilder only. It's important both what JVM the IDE is using and what also what JVM is maven running on.
Yep, the share is valid. If you use windows explorer to browse your network, you may see a couple of shares. You'll never see shares like c$ (drive c:), which exist by default. Try to explore \\yourserver\c$, and you'll get it. Be default you need some administrative rights. In the same way, it is possible to hide shares, where a normal user has access rights. Just append the "$" when assigning a name for this share. And yesterday, I downloaded and installed the final version of NB 7.3.1. No problem on the same machine(s). See issue 220809, installer problem. It seems to have the same cause. There must be a library for unc path inthe dev version, which has been changed some days or weeks ago.
Issue has a typo. Correct one is issue 230809.
(In reply to comment #4) > > See issue 220809, installer problem. It seems to have the same cause. There > must be a library for unc path inthe dev version, which has been changed some > days or weeks ago. but the error Could not create local repository at \\Fileserver1\User$\muellermi\.m2\repository -> [Help 1] is coming from the maven JVM. There are no netbeans originating unc path library that we would inject into maven's JVM. Please verify that both 7.3.1 and dev builds are running on the same JVM. Can you build using maven (same version, same JDK used) on the cmd line?
Hm, I haven't tried from the command line yet, nor will have time this week :( But, fresh installation of NB 7.3.1 yesterday on the same machine, using the same JVM has no such problem.
(In reply to comment #7) > Hm, I haven't tried from the command line yet, nor will have time this week :( > But, fresh installation of NB 7.3.1 yesterday on the same machine, using the > same JVM has no such problem. Ok, please test and also attach the IDE log files from 7.3.1 and dev builds. I've double checked that both 7.3.1 and dev are using the same maven 3.0.5.
please reopen with the 7.3.1 log file. also with regard to issue 230809 - have you tried to reproduce this issue with a build that has the given issue resolved? The current problem could be a result of a mis-installation
There seems to be no such problem in current version anymore.
ok, changing to worksforme, please reopen if the problem resurfaces