The current common apache parent POM (version 7) [1], when you specify
the "apache-release" profile, activates a part:
<plugins>
<!--
Create a source-release artifact that contains the fully buildable
project directory source structure. This is the artifact
which is
the official subject of any release vote.
-->
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
. . .
<executions>
<execution>
<id>source-release-assembly</id>
. . .
<configuration>
<runOnlyAtExecutionRoot>true</runOnlyAtExecutionRoot>
. . .
</configuration>
When used on a multi-module aggregate project, this only creates the
source-release-assembly at the aggregate project level. It seems to me,
since this artifact is the "official subject of any release vote", that
this source assembly should include the sources from this aggregate
project, **** plus all of the sub-modules ****. (Currently it only has
the the source from this aggregate project; none of the submodules are
included.)
I think the assembly plugin attempts to support this use case, via its
"<moduleSets>" elements. Are multi-module projects in Apache supposed
to override the common Apache Parent and specify the <moduleSets> form
of assembly?
Or is there another preferred way to do this?
-Marshall Schor
[1] http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
