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
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
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
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
