Hi Rui,
I guess You were formally using the 'assembly:assembly' (or
'assembly:directory') goal, right? Those goals where "not inherited by
default in multi-project builds" [1], but they "forced Maven to build
all included POMs up to the package phase before the assembly is
processed" [1].
This is discouraged now, You should assemble Your release artifacts
using an additional submodule instead - like discribed in [2].
About Your POM and command invocation:
In contrast to using 'assembly:assembly', the 'assembly:single' goal is
inherited to the sub modules. The results are:
- With inherited=false, the 'assembly:single' execution is missing the
assembly descriptor configuration.
- With inherited=true, the 'assembly:single' execution cannot find
Your assembly descriptor, because it expects a 'release.xml' file in the
base directory of each sub module.
- You could call 'mvn help:effective-pom -N' to not recurse into the
sub modules, but how would You get their artifacts then?
One last point: With all my questions I wanted to tell You that You
should tend to provide all the information that might be needed to
answer Your question. Even in Your last mail I didn't find enough
information so that I had to guess what You really want to achieve and
how Your assembly descriptor might look like. (And I guess that this
lack of information is the main reason why no one else took care of Your
question so far)
Kind regards
Marc
[1] http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html
[2]
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
