Hi, I'm new to this plugin. I'm trying to use build-helper:attach-artifact to publish a jar. It fails because the artifact does not exists. Is there a way to skip the attempt to publish if the artifact does not exists?
Here is my scenario. I'm using the plugin to publish clover instrumented jar files. My project is composed of several modules of which the top level project does not have any source code. Potentially some modules may not have source code. Clover tries to compile the source code and creates a clover.jar file for each module it finds. The plugin has been setup to then publish this jar file but because some modules don't have source code, a jar file is not produced by clover. But the plugin will try to publish it anyways. Because the file does not exist, the plugin fails and hence my maven project fails. How can the plugin handle the situation in where the artifact does not exist in a multi module project? Thanks, Fernando -- View this message in context: http://old.nabble.com/build-helper-attach-artifact-fails-tp32855607p32855607.html Sent from the mojo - user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
