[
https://jira.codehaus.org/browse/MDEPLOY-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gili closed MDEPLOY-165.
------------------------
Resolution: Not A Bug
Fix Version/s: 2.8
Sorry. I discovered that (no such method) when I tried formulating a patch. I
misunderstood what was going on on my binary server and incorrectly assumed
that the POM should contain a <classifier> field. As you mentioned, there is no
such field.
I'm closing this issue as "not a bug". Sorry for the false alarm.
> deploy-file ignores classifier
> ------------------------------
>
> Key: MDEPLOY-165
> URL: https://jira.codehaus.org/browse/MDEPLOY-165
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy-file
> Affects Versions: 2.7
> Reporter: Gili
> Priority: Critical
> Fix For: 2.8
>
>
> MDEPLOY-19's implementation is incomplete. If a user specifies a
> {{classifier}} then {{generatePom}} fails to take the classifier into
> consideration and uploads a POM file that omits the classifier.
> The fix is simple:
> Add the following line to {{DeployFileMojo.generateModel()}}:
> {{model.setClassifier( classifier );}}
--
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
