continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1253) Allow to deploy artifact without timestamps
Date Tue, 13 May 2008 00:17:28 GMT


Wendy Smoak commented on CONTINUUM-1253:

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.

> Allow to deploy artifact without timestamps
> -------------------------------------------
>                 Key: CONTINUUM-1253
>                 URL:
>             Project: Continuum
>          Issue Type: New Feature
>          Components: Core system, Integration - Maven 2, Web - UI
>    Affects Versions: 1.0.3
>            Reporter: Damian Golda
>            Assignee: Emmanuel Venisse
> 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
>  ArtifactRepository deploymentRepository =
>                         artifactRepositoryFactory.createDeploymentArtifactRepository(
"deployment-repository", location,
 repositoryLayout, true );
> PLEASE, change it, and allow to set required behavior by admin in Edit Configuration
> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message