Maybe you could just create some Maven profiles. One profile would have Released dependencies, while another would have the SNAPSHOTs.
Well, that's one ideia. See ya On Wed, Oct 8, 2008 at 8:13 AM, murali mohan <[EMAIL PROTECTED]> wrote: > My take : > > I think this is more of a maven problem rather than Continuum. Continuum > just executes the maven goal (along with arguments specified) specified in > the build definition. So if you want to use a different version of a > dependency, you have to use the corresponding maven command and arguments > which will help you override the version of the dependency - I am not sure > if maven has such a provision to override versions set in POM. > > rgds, > Murali. > > On Wed, Oct 8, 2008 at 12:00 PM, chuchi <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > we are thinking about installing Continuum, but we don't know if it > > can do what we need. We have read the tutorials but they are not clear > > about this point: > > > > When you use maven in your projects, does Continuum compile every > > project with trunk version of each library project, or only with the POM > > version? I mean: > > > > Library A: Version 2 final, Version 3-SNAPSHOT in trunk > > App B: Using library A-1 in POM > > App C: Using library A-2 in POM > > App D: Using library A-3-SNAPSHOT in POM > > > > In order to be sure about backward compatibility, we want to compile all > > applications with the trunk version of the library (Version 3-SNAPSHOT, > > in example) instead of the pom specification. > > > > Regards, > > Chuchi > > > > >
