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]
