[
http://jira.codehaus.org/browse/MDEPLOY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269506#action_269506
]
Ruben Garat edited comment on MDEPLOY-48 at 6/3/11 2:20 PM:
------------------------------------------------------------
Hi, would it be reasonable to have support for an arbitrary number of attached
artifacts?
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 this but tried to solve for the
natives, and 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.
EDIT: is this request ok here, or should I create another issue?
was (Author: ruben01):
Hi, would it be reasonable to have support for an arbitrary number of
attached artifacts?
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 this but tried to solve for the
natives, and 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.
> deploy:deploy-file does not support deploying sources jars too
> --------------------------------------------------------------
>
> Key: MDEPLOY-48
> URL: http://jira.codehaus.org/browse/MDEPLOY-48
> Project: Maven 2.x Deploy Plugin
> Issue Type: Improvement
> Affects Versions: 2.3
> Reporter: Geoffrey De Smet
> Assignee: Paul Gier
> Fix For: 2.6
>
>
> deploy:deploy does, but deploy:deploy-file doesn't have a parameter to tell
> him where the sources jar is:
> mvn deploy:deploy-file -Dfile=$artifactFile -DpomFile=$pomFile -Durl=$toRepo
--
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
