[
http://jira.codehaus.org/browse/MSHADE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189956#action_189956
]
Mark Struberg commented on MSHADE-54:
-------------------------------------
I did few tests first to figure out how the current behaviour is (all with
shadedArtifactAttached=false for now)
fN-build: finalName in the <build> section
fN-shace: finalName in the <configuration> section of the shade plugin
{noformat}
fN-build fN-shade target repo
empty empty 'shaded'.jar + original-xx.jar 'shaded'.jar
MyBuildName empty MyBuildName.jar + shaded with unshaded with 'standard'
artifact name
'standard' artifact name
MyBuildName OtherBuildName MyBuildName.jar + shaded with unshaded with
'standard' artifact name
OtherBuildName
MyBuildName MyBuildNamne shaded "MyBuildName.jar" + SHADED with 'standard'
artifact name
"original-MyBuildName.jar"
empty MyBuildNamne shaded "MyBuildName.jar" + unshaded with 'standard' artifact
name
UNshaded with 'standard'
artifact name
{noformat}
However, if I set shadedArtifactAttached=true the
ShadeMojo#shadedArtifactFile(); and ShadeMojo#replaceFile(..) will not be
called anyway.
> <finalName> not respected when generating the package
> -----------------------------------------------------
>
> Key: MSHADE-54
> URL: http://jira.codehaus.org/browse/MSHADE-54
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.2.1
> Reporter: Sean McRae
>
> Specifying the final name of the package is not respected by the plugin,
> instead the default name for the package is always used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
