jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Continuum
  • CONTINUUM-1253

Allow to deploy artifact without timestamps

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.0.3
  • Fix Version/s: None
  • Component/s: Core system, Integration - Maven 2, Web - UI
  • Labels:
    None
  • Complexity:
    Intermediate

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

relates to

Bug - A problem which impairs or prevents the functions of the product. CONTINUUM-1693 Continuum fills our server disk with SNAPSHOTs.

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Emmanuel Venisse added a comment - 31/Jul/07 5:04 PM

use mvn deploy instead

Show
Emmanuel Venisse added a comment - 31/Jul/07 5:04 PM use mvn deploy instead
Hide
Permalink
George Gastaldi added a comment - 16/Sep/07 11:09 PM

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

Show
George Gastaldi added a comment - 16/Sep/07 11:09 PM This occurs in 1.1-beta 2 also. mvn deploy does not work. Please, see this ASAP.
Hide
Permalink
Wendy Smoak added a comment - 12/May/08 7:15 PM

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 - 12/May/08 7:15 PM 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
Vote (0)
Watch (2)

Dates

  • Created:
    24/Apr/07 4:13 AM
    Updated:
    12/May/08 7:15 PM
    Resolved:
    31/Jul/07 5:04 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.