Hi Richard, > I can see it both ways... If it runs at > the packaging phase, it'll start (by default) by processing the packaged > artifact created by the default packaging and either overwriting the > artifact or creating a new one with a classifier (e.g. "<artifact>-small"). > If it runs at the pre-packaging phase, I'd have it start processing on the > output folder from the compile phase.
without taking a stance on which of the two options is better/more Maven-like, I would also add an option 3: obfuscate the class files in the process-classes phase [1]. That way the unit tests run against the obfuscated classes, which may expose problems due to the obfuscation that would otherwise go unnoticed. Hope that helps. Andreas [1] <http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
