Line numbers in exception

Hi all,
   I am trying to debug my cosmo extension - when I get an
exception, I
don't see a line number of the cosmo source java file in
the stack
trace. I see line numbers for all the other java files
including
jackrabbit, etc.

Is there any configuration that will allow me to see the
line number of
the cosmo source file which caused the exception?

_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On 7/27/06, Vinubalaji Gopal <vinuosafoundation.org>
wrote:
> Hi all,
>    I am trying to debug my cosmo extension - when I get
an exception, I
> don't see a line number of the cosmo source java file
in the stack
> trace. I see line numbers for all the other java files
including
> jackrabbit, etc.
>
> Is there any configuration that will allow me to see
the line number of
> the cosmo source file which caused the exception?

i don't know what causes this. one theory is if something
uses
reflection or introspection (i can never remember which is
which) to
execute cosmo code. but i'm not really sure. most of the
time i
actually do get line numbers, so i haven't looked into it.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On Thu, 2006-07-27 at 13:41 -0700, Brian Moseley wrote:
> i don't know what causes this. one theory is if
something uses
> reflection or introspection (i can never remember which
is which) to
> execute cosmo code. but i'm not really sure. most of
the time i
> actually do get line numbers, so i haven't looked into
it.

hm I have never the line numbers before. Will note it when I
get an
exception next time, probably its my development environment
issue.


_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On 7/27/06, Vinubalaji Gopal <vinuosafoundation.org>
wrote:
> Hi all,
>    I am trying to debug my cosmo extension - when I get
an exception, I
> don't see a line number of the cosmo source java file
in the stack
> trace. I see line numbers for all the other java files
including
> jackrabbit, etc.
>
> Is there any configuration that will allow me to see
the line number of
> the cosmo source file which caused the exception?

i don't know what causes this. one theory is if something
uses
reflection or introspection (i can never remember which is
which) to
execute cosmo code. but i'm not really sure. most of the
time i
actually do get line numbers, so i haven't looked into it.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On Thu, 2006-07-27 at 13:41 -0700, Brian Moseley wrote:
> i don't know what causes this. one theory is if
something uses
> reflection or introspection (i can never remember which
is which) to
> execute cosmo code. but i'm not really sure. most of
the time i
> actually do get line numbers, so i haven't looked into
it.

hm I have never the line numbers before. Will note it when I
get an
exception next time, probably its my development environment
issue.


_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On Thu, 2006-07-27 at 13:48 -0700, Vinubalaji Gopal wrote:
> On Thu, 2006-07-27 at 13:41 -0700, Brian Moseley wrote:
> > i don't know what causes this. one theory is if
something uses
> > reflection or introspection (i can never remember
which is which) to
> > execute cosmo code. but i'm not really sure. most
of the time i
> > actually do get line numbers, so i haven't looked
into it.
> 
> hm I have never the line numbers before. Will note it
when I get an
> exception next time, probably its my development
environment issue.

Seems like its a configurable option in maven. 

Changing the following option in project.properties will
cause maven to
compile with debug options and hence the line numbers will
be visible in
the log files.
maven.compile.debug=on

Thanks to Bobby for pointing this out .

You might need to clean the build with maven clean to ensure
that it
works. 

_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev