In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service.
If you followed a previous chapter, you should have your local Maven repository populated with the necessary SOA binaries. In order to build on the cloud, the project's remote Maven repository needs to be seeded with the same binaries. We can use the same sync plugin to achieve this.
First, in a pom.xml or preferably settings.xml, configure a repository and a server. An example of this is shown at 0:25 of the video. The important part is that the child "id" tag of the "server" tag match the reference of the child "id" tag of the "repository" tag. Secondly, if you put the "repository" tag inside a profile tag, make note of the child "id" tag.
Now we are ready to deploy the plugin to the remote repository (the red text denotes the values that must match in your pom.xml or settings.xml):
mvn deploy:deploy-file \
Finally, we use the "push" goal of the sync plugin to push the changes to the remote Maven repository (again, the red text denotes the values that must match in your pom.xml or settings.xml. The -P is because I put the repository tag in a profile. Just note that there are other ways to get the repository information to Maven; in fact, we will use a different way in the next chapter. The reason I used settings.xml here is to avoid editing multiple files in the video):
mvn com.oracle.maven:oracle-maven-sync:push \
While Linux is used in the video series, all mvn and git commands are applicable to Windows. Any variations will be called out in the accompanying blog.