Re: jar goal depending on test goal
Frederic Gedin wrote: Hi Is there any good reason for having the jar:jar depend on test:test? The problem I have with that is that, even if I make a very little change and want to check it on the application, I need to have the whole unit test suite executed for nothing. In addition, I can't get the jar file if all the tests do not succeed which is not very convenient on a developing phase. On the other way, I can accept the responsibility of ensuring that my test suite is fully executed before releasing the application jar file. I have the same comment regarding the site goal which will rerun all the tests, the coverage and so on even though nothing has changed. A very convenient feature should be to have some tunable which will allow me to execute a goal event if some of the dependencies have not been verified. An other solution should be to have some persistence on goals state, for example do not rerun the unit test suite if no source file has changed. Regards Frédéric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Try setting the property maven.test.skip=true to skip running the tests and maven.test.failure.ignore=true to ignore failures in testing. Documented on the test plugin page http://maven.apache.org/reference/plugins/test/properties.html -- Erik Husby Team Lead for Software Quality Automation Broad Institute of MIT and Harvard Rm. 2192 320 Charles St Cambridge, MA 02141-2023 mobile: 781.354.6669, office: 617.258.9227, [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jar goal depending on test goal
Frederic, 1. Configure you POM to invoke a dummy test. 2. Create a testsuit to include all your test cases. 3 Invoke test:single goal against testsuite in step 2 as needed. This might do the trick. -Dan - Original Message - From: Frederic Gedin [EMAIL PROTECTED] To: Maven Users List [EMAIL PROTECTED] Sent: Friday, June 04, 2004 10:02 AM Subject: jar goal depending on test goal Hi Is there any good reason for having the jar:jar depend on test:test? The problem I have with that is that, even if I make a very little change and want to check it on the application, I need to have the whole unit test suite executed for nothing. In addition, I can't get the jar file if all the tests do not succeed which is not very convenient on a developing phase. On the other way, I can accept the responsibility of ensuring that my test suite is fully executed before releasing the application jar file. I have the same comment regarding the site goal which will rerun all the tests, the coverage and so on even though nothing has changed. A very convenient feature should be to have some tunable which will allow me to execute a goal event if some of the dependencies have not been verified. An other solution should be to have some persistence on goals state, for example do not rerun the unit test suite if no source file has changed. Regards Frédéric - 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]
Re: jar goal depending on test goal
On Fri, 2004-06-04 at 13:02, Frederic Gedin wrote: Hi Is there any good reason for having the jar:jar depend on test:test? Of course, in a default mode of operation why on earth would allow a JAR that might be distributed with running the tests. The problem I have with that is that, even if I make a very little change and want to check it on the application, I need to have the whole unit test suite executed for nothing. maven -Dmaven.test.skip=true and your tests won't be executed. In addition, I can't get the jar file if all the tests do not succeed which is not very convenient on a developing phase. On the other way, I can accept the responsibility of ensuring that my test suite is fully executed before releasing the application jar file. The default mode is that which makes most sense to us which is making sure a JAR doesn't get built that hasn't been tested. If you want to juggle shotguns then you can skip the tests with the simple setting of a property or you can turn the testing off by default and use a property to turn them on. I have the same comment regarding the site goal which will rerun all the tests, the coverage and so on even though nothing has changed. You can customize the reports and configure testing as mentioned above. A very convenient feature should be to have some tunable which will allow me to execute a goal event if some of the dependencies have not been verified. An other solution should be to have some persistence on goals state, for example do not rerun the unit test suite if no source file has changed. Certainly. More conveniences like that could be added. But for the most part all the issues you raised are already dealt with in the current version you are using. Regards Frédéric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jar goal depending on test goal
Thanks for your answer and also for the others. I promise next time to have a better look on the documentation. The option based on maven.skip.test is fine for me. Regards Frederic Jason van Zyl a écrit : On Fri, 2004-06-04 at 13:02, Frederic Gedin wrote: Hi Is there any good reason for having the jar:jar depend on test:test? Of course, in a default mode of operation why on earth would allow a JAR that might be distributed with running the tests. The problem I have with that is that, even if I make a very little change and want to check it on the application, I need to have the whole unit test suite executed for nothing. maven -Dmaven.test.skip=true and your tests won't be executed. In addition, I can't get the jar file if all the tests do not succeed which is not very convenient on a developing phase. On the other way, I can accept the responsibility of ensuring that my test suite is fully executed before releasing the application jar file. The default mode is that which makes most sense to us which is making sure a JAR doesn't get built that hasn't been tested. If you want to juggle shotguns then you can skip the tests with the simple setting of a property or you can turn the testing off by default and use a property to turn them on. I have the same comment regarding the site goal which will rerun all the tests, the coverage and so on even though nothing has changed. You can customize the reports and configure testing as mentioned above. A very convenient feature should be to have some tunable which will allow me to execute a goal event if some of the dependencies have not been verified. An other solution should be to have some persistence on goals state, for example do not rerun the unit test suite if no source file has changed. Certainly. More conveniences like that could be added. But for the most part all the issues you raised are already dealt with in the current version you are using. Regards Frédéric - 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]
