The release plugin must avoid snapshot dependencies in the release of an artifact. This is true. But the question is whether the dependency is kicked to the next snapshot in the next development version of that artifact or it stays at the release version. For example project A depends on artifact B and we want release project A.
Before release of A (Have to release project B before. After that i got B(0.0.2-SNAPSHOT) right?): A(0.0.1-SNAPSHOT) depends on B(0.0.1-SNAPSHOT) The release of A: A(0.0.1) depends on B(0.0.1) After the release of A: a) A(0.0.2-SNAPSHOT) depends on B(0.0.1) b) A(0.0.2-SNAPSHOT) depends on B(0.0.2-SNAPSHOT). For my own usecase where we have strongly coupled projects and usually changes are made in both projects we desire behavior b) but other users would like prefer behavior a). This depends on the project structure i think. So this behavior should be configurable by the user (maybe as a plugin?). This would give us the possibility to define the desired behavior per project. One would argue that switching to the next snapshot is not the responsibility of the release plugin but for my own usecase manually switching the dependencies to the next development version is tedious and error-prone. One solution could be to integrate functionality of the maven-versions-plugin here that collects its version information from the real repository and allows the user to define the desired behavior. Any Comments? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
