On 5/24/10 1:04 PM, Ernst de Haan wrote: > Wayne, > > >>> How can I make sure the manifest file gets generated before the unit tests >>> are executed? >>> >>> - the unit tests attempt to validate that Java code, but the manifest file >>> is not generated, it's only part of the JAR >> >> Instead of running that test in this module's build, add another >> module alongside it that depends on this artifact, and run this test >> there. It will bring in the jar which, as you said, has the manifest >> in it. You will need a parent pom as well over both modules, and >> always build your project from the parent. > > Brilliant! Thank you for he advice, this is indeed what I will do, I'll add > another module. > > Note that I'm new to Maven, I typically use Ant (and an occasional shell > script). Although this approach seems the most logical, given the fixed model > Maven enforces, it does give the impression that it makes me go against the > basic principle Maven appears to herald, which is that one (sub-)project is a > contained entity, self-sufficient, including all resources required to build > and test the main codebase. > > What I find in (a few days) practice, is that I need to add an extra module > in multiple cases: > - to test code that depends on the manifest > - to test plugin code, since that needs to be compiled before the plugin can > be accessed by Maven
As an alternative to creating a separate module, you may be able to use the integration-test phase. This happens after your project is packaged, but before it is installed. Justin > > /me ponders > > But hey, thanks for giving me an easy way out that is very acceptable (at the > least). > > Cheers, > > > Ernst > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org