Continuum
  1. Continuum
  2. CONTINUUM-1253

Allow to deploy artifact without timestamps

    Details

    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      In our organisation we don't use unique names of jars in repository. So we have set uniqueVersion to false in pom.xml:

      <distributionManagement>
      <repository>
      <id>maven2-repo</id>
      <name>Maven2 Repository</name>
      <url>file://$

      {repoPath}

      </url>
      <uniqueVersion>false</uniqueVersion>
      </repository>
      </distributionManagement>

      And it works while running mvn from command line.

      But when we build project from continuum, it deploys built jar into Deployment Repository Directory and unfortunately always adds timestamps to filename.

      The reason is that in org.apache.maven.continuum.core.action.DeployArtifactContinuumAction is specified "true" as uniqueVersion parameter of ArtifactRepositoryFactory.createDeploymentArtifactRepository method:

      ArtifactRepository deploymentRepository =
      artifactRepositoryFactory.createDeploymentArtifactRepository( "deployment-repository", location,
      repositoryLayout, true );

      PLEASE, change it, and allow to set required behavior by admin in Edit Configuration page.

      We have strange problems with hundreds of fat jars in repository, caused by unique names of them.

      I think it's needed to:
      -add to Configuration new field, for example DeployWithUniqueVersion
      -change DeployArtifactContinuumAction, to uset that field instead of hard-coded true
      -add new field to EditContinuumConfiguration.vm
      -add some code to ConfigurationAction and InitializationChecker

        Issue Links

          Activity

          Hide
          Emmanuel Venisse added a comment -

          use mvn deploy instead

          Show
          Emmanuel Venisse added a comment - use mvn deploy instead
          Hide
          George Gastaldi added a comment -

          This occurs in 1.1-beta 2 also. mvn deploy does not work. Please, see this ASAP.

          Show
          George Gastaldi added a comment - This occurs in 1.1-beta 2 also. mvn deploy does not work. Please, see this ASAP.
          Hide
          Wendy Smoak added a comment -

          Use of the deployment repository is optional. Currently, If used, it will always contain timestamped snapshots.

          A better solution is to set up your own internal repository, and use 'mvn deploy' + distributionManagement with uniqueVersion=false.

          I'm not opposed to adding a 'uniqueVersion' checkbox on the deployment repository, if someone would like to work on it and contribute a patch.

          Show
          Wendy Smoak added a comment - Use of the deployment repository is optional. Currently, If used, it will always contain timestamped snapshots. A better solution is to set up your own internal repository, and use 'mvn deploy' + distributionManagement with uniqueVersion=false. I'm not opposed to adding a 'uniqueVersion' checkbox on the deployment repository, if someone would like to work on it and contribute a patch.

            People

            • Assignee:
              Emmanuel Venisse
              Reporter:
              Damian Golda
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: