Re: CVS version problem printing 'null' to console

[Ben Walding]

Whenever I get confronted by mysterious things, I run the pom:validate target. It's not perfect, but it has solved some oddities before (where I was doing something that worked by accident and then it was fixed so it only worked the correct way).


J. Matthew Pryor wrote:

Well I tracked it down in fact to an XML element import directive
&entity; that works just fine under beta-7 but dies with this mysterious
'null' under beta-8
I have no idea why

jmp

------------------------------------------------------------
j. matthew pryor <[EMAIL PROTECTED]>
versata, inc. <www.versata.com>


-----Original Message-----
From: J. Matthew Pryor [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 12:05 PM
To: 'Turbine Maven Users List'
Subject: CVS version problem printing 'null' to console

Hi I am trying to use a CVS build from Friday and am getting a strange
error from maven.bat

It just prints null to the console. I can't get it to give me any better
diagnostics

Forehead seems to run OK, but I can't tell how far into Maven I am
getting or who is printing the 'null'

I have tried maven -g, maven -X they both give the same result

Can anyone give me any tips on getting some better diagnostics out of
forehead or early maven bootstrapping

Thanks,
Matthew


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>