FATAL ERROR: id can not be null

2009-05-20 Thread Algie Morgan
I apologize if this question has already been asked. I have searched the recent archives and did not find it. I have a project that compiled fine under Maven 2.0.6. I recently upgraded to Maven 2.1.0 and it returned this error when I tried to compile: [INFO] Copying 10 resources [INFO]

Re: FATAL ERROR: id can not be null

2009-05-20 Thread Olivier Lamy
Hi, Maybe a repository/mirror declared in ~/.m2/settings.xml without any id. -- Olivier 2009/5/20 Algie Morgan morga...@iodp.tamu.edu: I apologize if this question has already been asked.  I have searched the recent archives and did not find it. I have a project that compiled fine under

Re: FATAL ERROR: id can not be null

2009-05-20 Thread Algie Morgan
Olivier, Thanks for your fast response, but that is not the problem. I checked the ~/.m2/settings.xml and that all checks out fine. There were only a few entries there for a jetspeed project I am experimenting with. I tried commenting out most of that file and I still get the error. But,

RE: FATAL ERROR: id can not be null

2009-05-20 Thread Martin Gainty
. Date: Wed, 20 May 2009 16:27:39 -0500 From: morga...@iodp.tamu.edu To: users@maven.apache.org Subject: Re: FATAL ERROR: id can not be null Olivier, Thanks for your fast response, but that is not the problem. I checked the ~/.m2/settings.xml and that all checks out fine. There were