I'm releasing a Maven2 multi-module project. One of the
modules is a POM project ("assembly project") that uses
the maven-assembly-plugin in order to build an assembly
(zip archive). The artifacts to be assembled are specified
via dependencies in the POM. They point to modules
contained in the same multi-module project.
When running mvn release:prepare on the multi-module
project, the build of the assembly project fails with the
message that the dependencies cannot be resolved. These
dependencies are reported with the version that should be
released, e.g. 0.0.3. Before running the goal, all
dependency versions are 0.0.3-SNAPSHOT.
What seems to happen is that the snapshot version
0.0.3-SNAPSHOT is replaced by 0.0.3 and then the assembly
plugin is started (which is bound to the package phase).
The assembly plugin tries to resolve the dependencies
based on version 0.0.3 which however do not yet exist at
that point.
I guess it is not a problem in Maven but I'm missing
practice on how to perform a successful release in this
situation.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
