Maven Deploy Plugin
  1. Maven Deploy Plugin
  2. MDEPLOY-48

deploy:deploy-file does not support deploying sources jars too

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.3
    • Fix Version/s: 2.6
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      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

        Issue Links

          Activity

          Hide
          Paul Gier added a comment -

          Added basic site docs in r1073533.

          Show
          Paul Gier added a comment - Added basic site docs in r1073533 .
          Hide
          Paul Gier added a comment -

          Reopening for some additional changes

          Show
          Paul Gier added a comment - Reopening for some additional changes
          Hide
          Paul Gier added a comment -

          Finished re-factoring to work with Maven 2.x in r1074207.

          Show
          Paul Gier added a comment - Finished re-factoring to work with Maven 2.x in r1074207 .
          Hide
          Ruben Garat added a comment - - edited

          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?

          Show
          Ruben Garat added a comment - - edited 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?
          Hide
          Paul Gier added a comment -

          Hi Ruben, you should create a new issue since this one is already closed.

          Show
          Paul Gier added a comment - Hi Ruben, you should create a new issue since this one is already closed.

            People

            • Assignee:
              Paul Gier
              Reporter:
              Geoffrey De Smet
            • Votes:
              10 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: