|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I wonder if this is specific to Maven artifacts? Do you have the "archive the artifacts" option checked on the job configuration? Typically Maven jobs do not require that option, because they automatically archive the build artifacts based on what the Maven POM decides should be archived (usually the POM and .jar).
I don't know when I'll be able to get around to fixing this, but I have a feeling that is probably the reason. I had not tested the plugin with a Maven project. Perhaps trying to enable that option might fix it as a workaround?