You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by "Diamond, Greg" <GD...@harryfox.com> on 2009/06/18 21:22:03 UTC

Selecting Local Repository From Maven Build Definition

Hi -

I am using Continuum with Maven2 projects.  I have some projects with dependancies on other internal projects which have QA and Production versions on my companies common repository.  Since Maven looks to the local repository first, I created separate QA and Production local repositories so when I call "Copy-Dependancies" the correct version gets selected and placed in the Continuum data folder.  If it doesn't exist locally, the pom profile specifies the correct remote repository to grab it from.

The only place I see to select a different local repository is at the Project Group level, and when I try to specify in a Build Definition with something like -Dmaven.repo.local=/my/repo/production, Continuum seems to overwrite it when it executes.  

Is there a way to do this?

TIA

RE: Selecting Local Repository From Maven Build Definition

Posted by Darren Hartford <dh...@ghsinc.com>.
If this is the preferred solution, I think you are going down the right
path.

For myself, I keep the dependency versions separated in a 'policy' type
fashion as the identifier between 'good' libraries and 'development'
libraries.

1.0.1-SNAPSHOT, 1.0.2-SNAPSHOT, etc = dev.
1.0.1, 1.0.2, 1.0.3, 1.0.4 = QA
1.0.4 = actually released to production once blessed by QA.  Do not
change the version, as that precise binary was what was blessed, no
changes to binary including the filename.

Now, this is just what I'm doing. For your shop, you might want to
change the version number once it is 'blessed'. So instead, odd a major
or minor version number for non-production versions, even major or minor
versions are production versions.

1.1-SNAPSHOT, 1.2-SNAPSHOT, etc = dev.
1.1, 1.2, 1.3, 1.4 = QA
1.4 becomes 2.0 = actually released to production once blessed by QA.

Start at 3.1-SNAPSHOT to continue development, and will become 4.0 once
production ready.

My two coppers,
-D


-----Original Message-----
From: Diamond, Greg [mailto:GDiamond@harryfox.com] 
Sent: Thursday, June 18, 2009 3:22 PM
To: users@continuum.apache.org
Subject: Selecting Local Repository From Maven Build Definition

Hi -

I am using Continuum with Maven2 projects.  I have some projects with
dependancies on other internal projects which have QA and Production
versions on my companies common repository.  Since Maven looks to the
local repository first, I created separate QA and Production local
repositories so when I call "Copy-Dependancies" the correct version gets
selected and placed in the Continuum data folder.  If it doesn't exist
locally, the pom profile specifies the correct remote repository to grab
it from.

The only place I see to select a different local repository is at the
Project Group level, and when I try to specify in a Build Definition
with something like -Dmaven.repo.local=/my/repo/production, Continuum
seems to overwrite it when it executes.  

Is there a way to do this?

TIA