I had another idea on how I could approach this.
Would it be possible to set up some sort of global initialization goal which would manually copy all the test classes to the separate test directory structure defined to maven, and then proceed with the normal maven goals?
This definitely seems possible to me, but I don't know if maven would have problems if the test dir tree did not exist or was not populated at maven startup time.
Is there some sort of built-in hook point that occurs very early in maven initialization, which I could use to trigger this copying and have it automatically happen before all other goals? Even if it's not automatic, I could make a hardcoded goal, and then always use other hardcoded "wrapper" goals to ensure that the test-copying goal is always invoked before the real goal.
This obviously isn't an optimal approach, but it would definitely be a workaround to get maven working and accepted by the team before I begin lobbying to move all the unit tests.
If this works, I could even see this being made into a plugin to help others in my same situation. I could even take a shot at it. Even though I've never done a plugin, maybe I could give a little back to the maven community.
Any input from the mavengurus on whether I can/cannot should/shouldn't take this approach to my problem?
Thanks, Chad
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
