a picture speak thousand words. I've tried to build my own project externally (maven 2.0.7) and everything seems to work as expected. I get the test error hyperlinked in output, I get the test failure stacktrace hyperlinked, I even get the JUnit window output if I trigger the "Test project" action.
So there must be something different about your setup in comparison to mine. Please file a bug at jira.codehaus.org/browse/MEVENIDE with a sample project demonstating the problem attached or with detailed description of your setup. Milos Kleint On Nov 29, 2007 10:39 AM, Stephen Connolly <[EMAIL PROTECTED]> wrote: > have a look in target/surefire-reports/*.txt > > On Nov 28, 2007 8:02 PM, Lally Singh <[EMAIL PROTECTED]> wrote: > > That fixes my pom problem, but it leaves me in the same state as > > before: no JUnit results. The JUnit integration doesn't work with an > > external maven. > > > > I just get a pass/fail result, but nothing to tell me why the test > > failed (e.g. stack traces). > > > > Is there a way to tell maven to give me more output about what failed > > in my tests? > > > > > > Thanks, > > > > -ls > > > > On 11/28/07, Milos Kleint <[EMAIL PROTECTED]> wrote: > > > project.basedir might have been introduced after 2.0.4 (which is what > the > > > embedded maven version is). > > > http://mevenide.codehaus.org/m2-site/faq.html#question4 > > > or perhaps something to do with groovy plugin? not sure, never tried > myself. > > > please try setting the project to use command line maven for building, > that > > > should make the problem go away. Project/Properties to mark the > project as > > > buildable by command line and Tools/Options for setting the path to > maven > > > itself. > > > > > > If it's not working then, please file a bug report at > > > jira.codehaus.org/browse/MEVENIDE > > > > > > Milos > > > > > > On Nov 28, 2007 8:00 PM, Lally Singh <[EMAIL PROTECTED]> wrote: > > > > > > > I've got this little snippet in my POM: > > > > <executions> > > > > <execution> > > > > <id>testdata_upload_vto</id> > > > > <phase>test-compile</phase> > > > > <goals><goal>operation</goal></goals> > > > > <configuration> > > > > <type>CLEAN_INSERT</type> > > > > <src>${project.basedir}/src/test/data/db_vto.xml</src> > > > > <url>jdbc:mysql://testsql.iddl.vt.edu/vto</url> > > > > </configuration> > > > > </execution> > > > > <execution> > > > > > > > > I get this bit from running my tests in NB: > > > > > > > > [groovy:execute {execution: default}] > > > > > ------------------------------------------------------------------------ > > > > [ERROR]BUILD ERROR > > > > > ------------------------------------------------------------------------ > > > > src/test/data/db_vto.xml (No such file or directory) > > > > > ------------------------------------------------------------------------ > > > > For more information, run Maven with the -e switch > > > > > > > > I change the file name to db_vtoF.xml in my POM, save the POM, > > > > reloaded the project, and hit test again. The error message > referred > > > > to db_vto.xml, not db_vtoF.xml. > > > > > > > > Btw, the file's there, and this part of the test process runs fine > > > > from the command line. But in NB, the error shows up. When the > right > > > > POM loads, I'll figure out what to put between those ${}. > > > > > > > > Thanks, > > > > > > > > -ls > > > > > > > > > > > > On 11/28/07, Milos Kleint <[EMAIL PROTECTED]> wrote: > > > > > 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] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > H. Lally Singh > > > > Ph.D. Candidate, Computer Science > > > > Virginia Tech > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > > H. Lally Singh > > Ph.D. Candidate, Computer Science > > Virginia Tech > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
