Allow to deploy artifact without timestamps
-------------------------------------------
Key: CONTINUUM-1253
URL: http://jira.codehaus.org/browse/CONTINUUM-1253
Project: Continuum
Issue Type: New Feature
Components: Core system, Integration - Maven 2, Web - UI
Affects Versions: 1.0.3
Reporter: Damian Golda
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
