Noticed some warnings in the Jenkins logs, regarding a no associated file found for MavenArtifact.

Pom file is archived but the packaging file extension throws the warning, because is not created (as expected) during mvn test.

May 09, 2017 10:32:29 AM WARNING org.jenkinsci.plugins.pipeline.maven.reporters.GeneratedArtifactsReporter listArtifacts
listArtifacts: Project MavenArtifact{com.xxx:My_Project::my_version}: no associated file found for MavenArtifact{com.xxx:My_Project:My_file_extension:my_version}

Build log also showing:

[withMaven] Can't archive maven artifact with no file attached: MavenArtifact{com.xxx:My_Project:My_file_extension:my_version }

The file extension is a custom one, that is basically a zip file with other files inside.

Adding the workaround to skip the reports clears the warnings in Jenkins and Console logs.

Using mvn install works correctly with no warnings and files being archived.

Could it be related with JENKINS-43678 ?