what do you mean by old version of POM? netbeans will update the project
definition if you changed the project's own pom, it will not currently do
automatically when changing something in the chain of parent poms. Use the
Reload action on project's popup. However for build execution there is no
caching, what is on disk is always used.

are you using netbeans 5.5 or 6.0? if 6.0, are you using the maven support
from default update center? that one shall open the regular JUnit window if
you run the "Test project" action. If you use just Build/Rebuild, it shall
underline the errors in output and create a hyperlink to the  stacktraces.

Could be a bug.

Milos

On Nov 28, 2007 7:45 PM, Lally Singh <[EMAIL PROTECTED]> wrote:

> Hey all,
>
>  I've got a testcase that I'm trying to get working, but I've got a
> little dilemma:
>
> - In Netbeans, I can usually get a stacktrace for JUnit errors.  But
> NB's using a bad (old?) version of my POM.  E.g. I changed my pom and
> I continue to get an error mesage from the old version.  NB's using
> some ancient version of my POM (probably from the initial project
> import), and I can't get it to use the new version.
>
> - Maven will (obviously) use the latest pom, but I don't know how to
> get any sort of failure report from my junit tests.  Just a count & a
> list of the failed tests, but no stack traces or other diagnostics.
>
> Any idea how to fix either/both problems?
>
> Thanks in advance,
>
> -ls
>
> --
> H. Lally Singh
> Ph.D. Candidate, Computer Science
> Virginia Tech
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to