Re: [m2] weird surefire test failure while all tests succeed
Has anybody figured this issue out? I'm experiencing the exact same problem and I looked at the surefire reports and did not find any failures... Also I have over 1200 unit tests so trying to isolate one is not feasible (plus I do not believe there are actually any failures). Any help would be appreciated. Thanks, Sujan tomiq wrote: Hi everyone there is some weird surefire test issue running on my computer. The problem is that I have 5 nonFailing(!) TestCase tests. When I run mvn test on the project surefire first runs the tests with no failure (Tests run: 95, Failures: 0, Errors: 0, Skipped: 0) then writes There are test failures. so the build fails too (even if -fn or -fae are enabled - I need the project's maven package). [EDIT] surefire tests pass only if lt;testFailureIgnoregt;truelt;/testFailureIgnoregt; is set in the maven-surefire-plugin's configuration. I encounred CHECKSUM FAILED warning while downloading some maven plugins from repository : org/apache/maven/surefire/surefire-providers/2.0/surefire-providers-2.0.pom, but it happens on every mirror I tried. I also tried to redownload the whole repository - nothing works. I'm using maven2.0.4 on sunJava1.5_06 on winXPsp2 (and I can provide detail info if it is needed). So post if you have something to say about the matter. Thanx tomas r btw: some mvn output is attached: http://www.nabble.com/file/629/error.log error.log -- View this message in context: http://www.nabble.com/weird-surefire-test-failure-while-all-tests-succeed-tf2116002s177.html#a9436237 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ? Must I install modules before compiling an other modules
This is excellent information, I've been wondering about this for so long but never knew an answer existed until now. Of course this leads me to another question :) Does this only work for compile? If I run mvn test from the parent directory, will the unit tests have the correct classpath with all of the submodules's classes included? Thanks so much for this information, Sujan Wayne Fay wrote: Places to run mvn compile: /projects/torsten/ -- success with nothing installed /projects/torsten/submoduleA, no dependencies -- success with nothing installed /projects/torsten/submoduleB, depends on A -- A must be installed for compile to be successful /projects/torsten/submoduleC, depends on B -- B must be installed for compile to be successful As a result, I generally run mvn compile from the parent directory, so I don't have to worry about what's installed and what isn't. Wayne On 1/17/07, Dan Tran [EMAIL PROTECTED] wrote: When you are INSIDE a module/project, the only way that maven can locate the dependencies is via local repository. An therefor all your dependent module must be installed.. However if you use the parent to build all modules, you dont have to run maven install but maven compile would do since maven is aware of all module's classes directory -Dan On 1/17/07, Dipl.-Ing. Torsten Liermann [EMAIL PROTECTED] wrote: (Sorry, I can not speak english). My question: Must I install modules before compiling an other module with dependcies to modules? Or is there a way without installing modules and start compilation within modules directory? The compilation from the parent directory works fine... Thanks, Torsten - 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] -- View this message in context: http://www.nabble.com/--Must-I-install-modules-before-compiling-an-other-modules-tf3027788s177.html#a8415795 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Plugin not using project dependencies
All, I'm having a problem where the plugins are not using the project-level dependencies. I have to redeclare the dependency within the plugin.../plugin for it to find the classes it needs. I would like to have the dependency declared once for the project and have the plugins see these dependencies. For example, I'm using the sql-maven-plugin to execute some sql statements. It needs a database driver to be able to do this :) I have declared a dependency on the jtds jar at the top of my pom.xml, like this: project ... dependencies ... dependency groupIdnet.sourceforge.jtds/groupId artifactIdjtds/artifactId version1.2/version scopecompile/scope /dependency /dependencies ... /project Unless I redeclare the dependency to jtds in the plugin declaration like this build plugins plugin ... dependencies dependency groupIdnet.sourceforge.jtds/groupId artifactIdjtds/artifactId version1.2/version /dependency /dependencies executions /executions /plugin /plugins /build the plugin doesn't work. When the plugin executes, I get Driver class not found: net.sourceforge.jtds.jdbc.Driver. If I redeclare the plugin as shown above, then it works. Can anybody shed some light on this? Thank your for your time, Sujan -- View this message in context: http://www.nabble.com/Plugin-not-using-project-dependencies-tf2091709.html#a5765700 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin not using project dependencies
All, If anyone can shed light on this problem I would appreciate it. I would rather not redeclare the dependencies in my plugin section if the project (pom) already has declared them at the top. Thanks, Sujan kapadia wrote: All, I'm having a problem where the plugins are not using the project-level dependencies. I have to redeclare the dependency within the plugin.../plugin for it to find the classes it needs. I would like to have the dependency declared once for the project and have the plugins see these dependencies. For example, I'm using the sql-maven-plugin to execute some sql statements. It needs a database driver to be able to do this :) I have declared a dependency on the jtds jar at the top of my pom.xml, like this: project ... dependencies ... dependency groupIdnet.sourceforge.jtds/groupId artifactIdjtds/artifactId version1.2/version scopecompile/scope /dependency /dependencies ... /project Unless I redeclare the dependency to jtds in the plugin declaration like this build plugins plugin ... dependencies dependency groupIdnet.sourceforge.jtds/groupId artifactIdjtds/artifactId version1.2/version /dependency /dependencies executions /executions /plugin /plugins /build the plugin doesn't work. When the plugin executes, I get Driver class not found: net.sourceforge.jtds.jdbc.Driver. If I redeclare the plugin as shown above, then it works. Can anybody shed some light on this? Thank your for your time, Sujan -- View this message in context: http://www.nabble.com/Plugin-not-using-project-dependencies-tf2091709.html#a5767675 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
