| The issue I noticed didn't involve a Gradle project. I was able to reproduce this in an SBT / Scala project where the name setting and the last node in the oragnization were the same name. for example: name := "myproject" organization := "com.myproject" in this case jenkins will create the artifact as workspace_2.11-01-SNAPSHOT.jar (instead of the expected myproject_2.11-0.1-SNAPSHOT). It will also publish the artifact in the directory /com/myproject/workspace_2.11/0.1-SNAPSHOT (instead of the expected /com/myproject/myproject_2.11/0.1-SNAPSHOT). Oddly enough just running the sbt build locally on the in a develop environment will generate the jar by its correct name So I suspect the root cause is that jenkins can't handle the situation where the artifact name is the same as the last node of the organization |
