[
https://issues.apache.org/jira/browse/MDEPLOY-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965607#comment-17965607
]
Olivier Lamy commented on MDEPLOY-71:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#229|https://github.com/apache/maven-deploy-plugin/issues/229].
> DeployFile Mojo Does Not Handle Non-Core Artifact Types
> -------------------------------------------------------
>
> Key: MDEPLOY-71
> URL: https://issues.apache.org/jira/browse/MDEPLOY-71
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: deploy:deploy-file
> Affects Versions: 2.3
> Reporter: Britton Isbell
> Priority: Minor
> Attachments: deploy-plugin-tests.zip, mdeploy-handler.patch
>
>
> I have a problem where I am trying to deploy .NET artifact but the deploy
> file Mojo treats packaging and extension as equivalent because the .NET
> artifact handler is not defined within the plugin. I've added an "extension"
> field to the Mojo configuration that will dynamically create and add an
> artifact handler to the artifact handler manager. This is a general patch and
> not .NET specific.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
