I suggest to create a [multi module maven project][1] (see the attached link)
In short, you do it as follows:
Create a project directory structure as follows
myRootFolder
- myIvyProjectA
-- pom.xml
- myIvyProjectB
-- pom.xml
- myMavenAggregationProject
-- pom.xml
The pom.xml files of the ivy-projects are the same as before (including dependencies etc.).
The pom.xml of the aggregation-project is an aggregation or multi module pom. It contains a section, that defines all modules to aggregate like:
<modules>
<module>../myIvyProjectA</module>
<module>../myIvyProjectB</module>
</modules><modules>
<module>../myIvyProjectA</module>
<module>../myIvyProjectB</module>
</modules>
For building, you run Maven for the myMavenAggregationProject only. As a result, all defined modules are built as well. Maven (or better said the [reactor plugin][2]) resolves inter-module-dependencies and controls the order of the modules to build accordingly.
[1]: https://maven.apache.org/pom.html#Aggregation
[2]: https://maven.apache.org/plugins/maven-reactor-plugin/examples.html
