> It would appear that there is a bug in the JVM that has been around for 6+
> years now. Apparently the JVM determines the value of user.home by which
> should point at the root of the users profile directory by looking at the
> registry key: [HKEY_CURRENT_USER\Software\ customer
> \Windows\Curren
Thanks for your help, I think I've figured out what the problem is.
I omitted to mention that I also re-homed my Desktop folder at the same time
I re-homed my documents folder as I didn't think it was relevant.
It would appear that there is a bug in the JVM that has been around for 6+
years now. A
> on the root folder of the user account by default. Is it possible to force
> use c:\users\me\.m2 again as builds are now much slower since it has to drag
> all the jar's over the network each time?
You can adjust the location of your repo in settings.xml, and it will
use c:\... instead.
As for
USERPROFILE=C:\Users\Graham Smith
HOMEDRIVE=C:
HOMEPATH=\Users\Graham Smith
Exactly as I would expect. I'm running Win 7 btw.
D:\Development\NetBeansProjects\core>
On 11 April 2011 19:47, Wayne Fay wrote:
> > Today I decided to re-home my Documents folder onto the company NAS. So I
> > right c
> Today I decided to re-home my Documents folder onto the company NAS. So I
> right click on the folder select location and change it to h:\documents.
> Much file copying later and everything is moved over. Since file compilation
> would be too slow over the network I move the NetBeans projects fol
Hi folks,
I've just come across what seems to be some very strange behaviour in Maven.
I'll try to explain as best I can the situation but it's a bit involved. So,
I started out with this set up working which was working perfectly:
maven 3.0.2 installed in d:\development\maven
maven projects inst
