In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service.
When you use the SOA Maven Archetype to generate a SOA project, the resulting pom.xmls are independent of each other. This leads to fragmentation and manageability issues. Further, the OSB Maven Archetype generates different pom.xmls that have mostly the same properties.
To combat these issues, I created a parent pom.xml that can be used for SOA projects and another parent pom.xml that can be used for OSB projects. Both of these pom.xmls in turn inherit from a third grandparent pom.xml. This provides a single configuration point for most properties. A project pom need only reference the pom.xml. It is free to override any properties set in the parent pom.xmls. Users are also free (and encouraged) to override any properties in their settings.xml.
You can find this project in the following github repository:
This project showcases the following: