If you use the release plugin it can generate the pom with fully locked down versions from the time of release. Just use that pom from your SCM tag for the release
On Wed, Jul 30, 2008 at 8:52 AM, Victor Tsoukanov <[EMAIL PROTECTED]> wrote: > We decided to use version ranges in module dependecies. For example I have > 3 modules: m1, m2 and m3, m2 and m3 depends on m1 and I can describe version > range instead of exact version number. In m1 pom.xml I set > "<version>1.1.0</version>" and in m2 and m3 pom.xml I described > dependencies: > <dependencies> > <dependency> > ......... > <artifactId>module-1</artifactId> > <version>[1.0,2.0)</version> > </dependency> > </dependencies> > Now I can compile m2 and m3 with the last version of m1 and I am able to > control backward compatibility. > But sometimes I should use specific version of modules, for example I have > to fix bug which is not reporoduced on last version of modules only on > specific (e.g. I need compile m2 with version 1.1.2, m3 (1.4.6) and > m1(1.1.5)). I have all versions in repository and would like just reproduce > specific build. > Thanks > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
