How can I make sure the manifest file gets generated before the unit tests are 
executed?

My use case is:
- a Java code base, under src/main/java
- unit tests under src/test/java
- pom.xml specifies packaging "jar" - JUnit 4.8.1 is a dependency
- Java code uses a property from the manifest to determine meta data (library 
version)
- Maven automatically generates the correct manifest file
- the unit tests attempt to validate that Java code, but the manifest file is 
not generated, it's only part of the JAR

Any suggestions?

Note that I'm new to Maven, but I used shell scripts and Ant build files a lot.

FYI, here is the actual code and POM:
http://github.com/znerd/logdoc/blob/master/base/src/main/java/org/znerd/logdoc/Library.java
http://github.com/znerd/logdoc/blob/master/base/src/test/java/org/znerd/logdoc/LibraryTest.java
http://github.com/znerd/logdoc/blob/master/base/pom.xml

Cheers,


Ernst de Haan

Reply via email to