Dear Sirs,

this is a feature that always worked well on hudson. I migrated our integration system to jenkins this week and I figured out that the new builds did not apply the maven build.finalName to the downloadable artifacts of each build.

We have this section in our master pom which activates the integration specific naming style:

<profile>
<id>jenkins</id>
<activation>
<property>
<name>SVN_REVISION</name>
</property>
</activation>
<build>
<finalName>${artifactId}-${version}-r${buildNumber}</finalName>
</build>
</profile>

When I dive into the job's workspace section I can see the final name applied to each artifact compiled into the target folder. This seems to be always the buildNumer of the last run. But with hudson, when browsing to the job's individual build numbers and then picking out any artifact from the list, the finalName was also applied to the download links from there. In jenkins this is not the case anymore. The artifacts have only standart convention like <artifactId>-<version>-SNAPSHOT. See the difference in the screenshots.

I would really appreciate that the old behavior would be available again and I think this can only be a bug, because I see no reason why this feature should have been intentionally turned off.

I'm not shure where this issue concerns to from your view, I assigned the component entry to maven2, maybe this must be relocated.

With kind regards,
Oliver