> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stephen,
> However, for two of our Windows systems, when we try and build the
> project using Maven 2, we get the
> following error. We are able to perform an "mvn clean" successfully on
> those machines, and also
> Java compilation succeeds. It'
Sent: Wednesday, March 22, 2006 3:26 PM
To: 'users@maven.apache.org'
Subject: FW: Problem with M2 on Windows Servers - running tests
-Original Message-
From: Gest, Stephen B
Sent: Wednesday, March 22, 2006 2:29 PM
To: 'users@maven.apache.org'
Subject: Problem with M
ROTECTED]
Sent: Wednesday, March 22, 2006 3:34 PM
To: Maven Users List
Subject: Re: FW: Problem with M2 on Windows Servers - running tests
Have you tried building these same exact projects etc on another system
ie Linux, Unix, or Mac OS X? If not, can you please try this, to ensure
that your problems
Settings\...
D:\Maven 202\...
Wayne
On 3/22/06, Gest, Stephen B <[EMAIL PROTECTED]> wrote:
>
> -Original Message-
> From: Gest, Stephen B
> Sent: Wednesday, March 22, 2006 2:29 PM
> To: 'users@maven.apache.org'
> Subject: Problem with M2 on Windows Servers - r
-Original Message-
From: Gest, Stephen B
Sent: Wednesday, March 22, 2006 2:29 PM
To: 'users@maven.apache.org'
Subject: Problem with M2 on Windows Servers - running tests
Hello,
Here is additional information regarding the error:
Executing "mvn -X install"
Hello,
We have a Java-based maven multi-project for which we've been using
Maven 1.0 successfully for several months.
We've recently upgraded to Maven 2.0.2, and for some of our systems, the
upgrade went successfully.
However, for two of our Windows systems, when we try and build the
project usin
Tanks,
The bootstrap really continues and everything seems to be ok. It was
just a bit confusing :).
Jan
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, November 11, 2005 5:35 PM
To: Maven Users List
Subject: Re: Problem with M2 build
-BEGIN PGP SIGNED
wrote:
| Hi,
|
| I'm affraid that there's a problem with m2 build. I checked out m2 from
| repository, executed m2-bootstrap-all.bat and it failed with the
| following error:
|
| org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
| in the plugin manager ex
Hi,
I'm affraid that there's a problem with m2 build. I checked out m2 from
repository, executed m2-bootstrap-all.bat and it failed with the
following error:
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
in the plugin manager execu
On Fri, 21 Oct 2005 11:42:22 +0100, Ross Bamford <[EMAIL PROTECTED]>
wrote:
Can anyone suggest a workaround, short of manually finding and
installing the missing jars?
Okay I think I found what I need now in the docs, and I can manually do
the remainder. I wasn't fully appreciating the im
On Fri, 21 Oct 2005 11:28:50 +0100, Edwin Punzalan <[EMAIL PROTECTED]>
wrote:
H
icu4j is not in central repo... the name could be incorrect or the
developers have not given their artifacts yet.
That's what I guessed. So the question is - is everyone who installs M2 on
a fresh mac
H
icu4j is not in central repo... the name could be incorrect or the
developers have not given their artifacts yet.
Ross Bamford wrote:
On Fri, 21 Oct 2005 10:19:00 +0100, Edwin Punzalan
<[EMAIL PROTECTED]> wrote:
Sun jars like servletapi and jta are not in central repo...
you sh
On Fri, 21 Oct 2005 10:19:00 +0100, Edwin Punzalan <[EMAIL PROTECTED]>
wrote:
Sun jars like servletapi and jta are not in central repo...
you should download them from sun website and install in your repo using
install:install-file.
My project doesn't use Servlet API of any description,
(apologies if this post is duped - I sent from incorrect address first
time and it didn't come up)
On Fri, 21 Oct 2005 10:19:00 +0100, Edwin Punzalan <[EMAIL PROTECTED]>
wrote:
Sun jars like servletapi and jta are not in central repo...
you should download them from sun website and instal
Sun jars like servletapi and jta are not in central repo...
you should download them from sun website and install in your repo using
install:install-file.
The download of artifacts is not sorted in any way so each run, you
download of artifacts is different. The build will download artifacts
Hi,
Hope this is the correct list for M2?
I downloaded the 2.0 release yesterday, but am having some problems
getting it to work - when I try to run a build it bombs out with missing
dependencies on stuff that (I assume) must be plug-in dependencies,
notably some xerces jars, the Servlet 2
You must upgrade to the Maven 2.0 RC build.
- Brett
On 10/15/05, Bill Siggelkow <[EMAIL PROTECTED]> wrote:
> I am new user of Maven 2 (and have only dabbled with Maven 1). I was
> following the instructions from the getting started page and ran into
> the following error when I tried to run 'm2 c
I am new user of Maven 2 (and have only dabbled with Maven 1). I was
following the instructions from the getting started page and ran into
the following error when I tried to run 'm2 clean:clean package' on
the webapp archetype I created. I am using the maven-2.0-beta-3.
Here's the stack tr
24 matches
Mail list logo
