Skip through them in turn.
- project dependency on another module in the assembly
This means that if module A has a dependency on module B, then B must be built up to A. This handles the case when in the POM of group A you must:
<dependencies>
<dependency>
<groupId>${project.groupId}<groupId>
<artifactId>B<artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
- plugin declaration, where the plugin is another module in the assembly
, A Maven, B, B A. , POM A :
<build>
<plugins>
<plugin>
<groupId>${project.groupId}<groupId>
<artifactId>B<artifactId>
<version>${project.version}</version>
</plugin>
</plugins>
</build>
, A Maven B, B A. , POM A :
<build>
<plugins>
<plugin>
<groupId>some.plugin.groupId<groupId>
<artifactId>some.plugin.artifactId<artifactId>
<version>some.version</version>
<dependencies>
<dependency>
<groupId>${project.groupId}<groupId>
<artifactId>B<artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
, , , , , .
, A B, B A. POM A :
<build>
<extensions>
<extension>
<groupId>${project.groupId}</groupId>
<artifactId>B</artifactId>
<version>${project.version}</version>
</extension>
</extensions>
</build>
, - <modules>, POM :
<modules>
<module>A</module>
<module>B</module>
</modules>
A B, .