[
https://issues.apache.org/jira/browse/MDEPLOY-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965677#comment-17965677
]
Olivier Lamy commented on MDEPLOY-134:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#336|https://github.com/apache/maven-deploy-plugin/issues/336].
> mvn deploy:deploy-file should allow to add an arbitrary number of attached
> artifacts not only sources and javadoc
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-134
> URL: https://issues.apache.org/jira/browse/MDEPLOY-134
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: deploy:deploy-file
> Reporter: Ruben Garat
> Assignee: stephenconnolly
> Priority: Major
> Fix For: 2.7
>
>
> I have to deploy some artifacts that have the main jar, javadoc, sources, and
> different artifacts for natives for different OS using classifiers to
> indicate the OS.
> In this case I still have the same problem that #MDEPLOY-48 tried to fix by
> allowing to deploy sources and javadoc with the main jar in one step but with
> the native artifacts, there is no good solution that supports maven 2 and
> maven 3 for deploying this artifacts as separate steps (if I use
> uniqueVersions=false then maven 3 doesn't update the snapshots even when
> forcing it, if I use uniqueVersion=true then when using maven 2 it fails to
> resolve the main jar because the pom has a different timestamp than the jar)
> something like:
> -attached classifier:artifactpath
> and allowing this command to be repeated would work I think.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
