You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by on 2003/02/28 19:01:27 UTC
Cryptic error messages
When I try to generate plugin docs for xdoc, I get:
maven-jxr-plugin:report:
[echo]
javadocdir:null
BUILD FAILED
null:74:29: <jxr:jxr> null
Total time: 21 seconds
What is the best way to decode the string "null:74:29: <jxr:jxr> null" into
something that could point me towards the source of the error?
Thanks
--------
Tim O'Brien
RE: Cryptic error messages
Posted by .
Thanks for the explanation, it has been added to the Wiki FAQ.
--------
Tim O'Brien
> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: Sunday, March 02, 2003 5:58 AM
> To: Turbine Maven Developers List
> Subject: Re: Cryptic error messages
>
>
> short, dumb explanation follows:
>
> null:74:29: <jxr:jxr> null
>
> - The first null means that it's not a script loaded from a
> file, it's
> from a plugin.
> - The 74:29 is the line:column where the error occurred
> - <jxr:jxr> is the tag that caused the exception
> - null is the message of that exception.
>
> So, it's an NPE in the jxr plugin at line 74, column 29 of it's
> plugin.jelly, on the <jxr:jxr> tag
>
> HTH,
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
> Mike Bowler <mb...@GargoyleSoftware.com> wrote on
> 01/03/2003 05:51:46
> AM:
>
> > > null:74:29: <jxr:jxr> null
> >
> > > What is the best way to decode the string "null:74:29: <jxr:jxr>
> > > null"
> into
> > > something that could point me towards the source of the error?
> >
> > I find that the -e option will often give me enough information to
> > figure out the problem.
> >
> > For example, maven -e site:deploy
> >
> >
> > --
> > Mike Bowler
> > Principal, Gargoyle Software Inc.
> > Voice: (416) 822-0973 | Email : mbowler@GargoyleSoftware.com
> > Fax : (416) 822-0975 | Website: http://www.GargoyleSoftware.com
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > turbine-maven-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> turbine-maven-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> turbine-maven-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> turbine-maven-dev-help@jakarta.apache.org
>
Re: Cryptic error messages
Posted by di...@multitask.com.au.
short, dumb explanation follows:
null:74:29: <jxr:jxr> null
- The first null means that it's not a script loaded from a file, it's
from a plugin.
- The 74:29 is the line:column where the error occurred
- <jxr:jxr> is the tag that caused the exception
- null is the message of that exception.
So, it's an NPE in the jxr plugin at line 74, column 29 of it's
plugin.jelly, on the <jxr:jxr> tag
HTH,
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Mike Bowler <mb...@GargoyleSoftware.com> wrote on 01/03/2003 05:51:46
AM:
> > null:74:29: <jxr:jxr> null
>
> > What is the best way to decode the string "null:74:29: <jxr:jxr> null"
into
> > something that could point me towards the source of the error?
>
> I find that the -e option will often give me enough information to
> figure out the problem.
>
> For example, maven -e site:deploy
>
>
> --
> Mike Bowler
> Principal, Gargoyle Software Inc.
> Voice: (416) 822-0973 | Email : mbowler@GargoyleSoftware.com
> Fax : (416) 822-0975 | Website: http://www.GargoyleSoftware.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-maven-dev-help@jakarta.apache.org
>
Re: Cryptic error messages
Posted by Mike Bowler <mb...@GargoyleSoftware.com>.
> null:74:29: <jxr:jxr> null
> What is the best way to decode the string "null:74:29: <jxr:jxr> null" into
> something that could point me towards the source of the error?
I find that the -e option will often give me enough information to
figure out the problem.
For example, maven -e site:deploy
--
Mike Bowler
Principal, Gargoyle Software Inc.
Voice: (416) 822-0973 | Email : mbowler@GargoyleSoftware.com
Fax : (416) 822-0975 | Website: http://www.GargoyleSoftware.com
Re: Cryptic error messages
Posted by Kasper Nielsen <ne...@kav.dk>.
O'brien, Tim wrote:
> When I try to generate plugin docs for xdoc, I get:
>
> maven-jxr-plugin:report:
> [echo]
> javadocdir:null
>
> BUILD FAILED
> null:74:29: <jxr:jxr> null
> Total time: 21 seconds
>
>
> What is the best way to decode the string "null:74:29: <jxr:jxr> null" into
> something that could point me towards the source of the error?
>
> Thanks
there are some issues with beta-8 upgrade to the stuff in cvs and make
sure your <sourceDirectory> is set correct.
- Kasper