I thought that the release plugin handled this. But I have never
tried, as I always use the ${project.version} property for specifying
version within a multi-module project. That would solve your problem./Anders On Fri, Sep 23, 2011 at 12:08, Abid Hussain <[email protected]> wrote: > Hello, > > my question is about how SNAPSHOT dependencies between submodules in multi > module projects can be automatically incremented when performing a release. > > Let's give an example: I've a multi module project P with two sub modules A > and B. Current version is 1.0-SNAPSHOT. The version number is only declared > in P. A and B inherit P's version. > > A is dependent on B 1.0-SNAPSHOT: A -> B (1.0-SNAPSHOT). > > Now I prepare a release of P by calling mvn release:prepare in the root > directory of P. The release preparation is done and the dependency from A to > B is changed to 1.0 in the tagged version. On my local machine the version of > P is incremented to 1.1-SNAPSHOT, same is done with the parent version > declaration in A and B (incremented to 1.1-SNAPSHOT). > > But, on my local machine the dependency from A to B is still of version > 1.0-SNAPSHOT. Is there a way to configure that also the dependencies between > modules in a multi-module project is to be incremented after a release? > > Regards, > > Abid > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
