[CONTINUUM-1253] Allow to deploy artifact without timestamps

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.0.3
• Component/s: Core system, Integration - Maven 2, Web - UI
• Assignee: Emmanuel Venisse
• Reporter: Damian Golda
• Created: 24/Apr/07 04:13
• Updated: 12/May/08 19:15
• Resolved: 31/Jul/07 17:04

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: CONTINUUM-1693 Continuum fills our server disk with SNAPSHOTs.