We recommend that you raise a ticket with Oracle Support if you are stuck so that in the case of a defect, the root cause can be addressed in the next Oracle Middleware version. That said, we have provided below a reference of workarounds to the standard Oracle Maven build parent seed process in case it helps to unblock you.
12.1.3 Oracle Maven Synchornization and Workarounds
Update the value of ORACLE_HOME to suit the target environment.
export ORACLE_HOME=/opt/app/oracle/product/fmw1221
export PATH=$PATH:${ORACLE_HOME}/oracle_common/modules/org.apache.maven_3.0.5/bin
# Workaround for building composites with OWSM policies as per https://community.oracle.com/thread/3597910
printf '<project xmlns="http://maven.apache.org/POM/4.0.0">\
<modelVersion>4.0.0</modelVersion>\
<groupId>com.oracle.adf</groupId>\
<artifactId>wsm-policy-core</artifactId>\
<version>12.1.3-0-0</version>\
<packaging>jar</packaging>\
<name>wsm-policy-core</name>\
<description>Generated from Oracle JDeveloper</description>\
<dependencies>\
<dependency>\
<groupId>com.oracle.adf</groupId>\
<artifactId>osdt_xmlsec</artifactId>\
<version>12.1.3-0-0</version>\
</dependency>\
<dependency>\
<groupId>com.oracle.adf</groupId>\
<artifactId>wsm-agent-core</artifactId>\
<version>12.1.3-0-0</version>\
</dependency>\
</dependencies>\
</project>' > wsm-policy-core-12.1.3.pom
rm -f ${ORACLE_HOME}/oracle_common/plugins/maven/com/oracle/adf/wsm-policy-core/12.1.3/wsm-policy-core-12.1.3.pom
cp wsm-policy-core-12.1.3.pom ${ORACLE_HOME}/oracle_common/plugins/maven/com/oracle/adf/wsm-policy-core/12.1.3
# Dependency for workaround as per http://www.esentri.com/blog/2016/04/07/unable-to-compile-a-composite-java-embedded-maven/
mvn install:install-file \
-Dfile=${ORACLE_HOME}/soa/soa/modules/oracle.soa.bpel_11.1.1/orabpel.jar \
-DgroupId=com.oracle.soa -DartifactId=orabpel -Dversion=12.1.3.0-0 -Dpackaging=jar
# Publishes the OFMW dependencies locally.
mvn install:install-file \
-Dfile=${ORACLE_HOME}/oracle_common/plugins/maven/com/oracle/maven/oracle-maven-sync/12.1.3/oracle-maven-sync-12.1.3.jar \
-DpomFile=${ORACLE_HOME}/oracle_common/plugins/maven/com/oracle/maven/oracle-maven-sync/12.1.3/oracle-maven-sync-12.1.3.pom
mvn com.oracle.maven:oracle-maven-sync:12.1.3-0-0:push \
-DoracleHome=${ORACLE_HOME} -DfailOnError=false
12.2.1 Oracle Maven Synchornization and Workarounds
Update the value of ORACLE_HOME to suit the target environment.
Installing the library dependencies for OSB standalone build
Unlike the SOA and JDeveloper build, the OSB build can be achieved without the need to install OSB once the initial library dependency seed has been done from a machine with OSB installed. Here is how:
Run the script from a Linux machine which has OSB 11.1.1.7 installed.
Edit the file install-dep-11.1.1.7.sh, setting:
MYST_FMW to point to Oracle FMW home
MYST_ARTIFACT_DEPLOY_PREFIX to do a maven install rather than deploy. e.g (note that MYST_ARTIFACT_DEPLOY_PREFIX is commented out for deploy):
export MYST_FMW=/u01/app/oracle/product/fmw
export MYST_OSB=$MYST_FMW/Oracle_OSB1
export MYST_TEMP=/tmp
set -e
export MYST_ARTIFACT_DEPLOY_PREFIX=install:install-file
#export MYST_ARTIFACT_DEPLOY_PREFIX="deploy:deploy-file -Durl=http://admin:password@127.0.0.1:8083/artifactory/libs-release-local"
set -e
...
Publishing to a Maven Repository
This is a one-off activity that will allow all developers and the CI server to retrieve the build parents automatically on build. Before performing these steps, make sure you have the Maven settings.xml defined to point to your Maven Repository such as Artifactory, Nexus, Archiva etc.
Run the following commands, making sure that your replace the URL with your Maven repository URL (which contains login/pwd)
Deploying the library dependencies for OSB standalone build
Run the script from a Linux machine which has OSB 11.1.1.7 installed.
Edit the file install-dep-11.1.1.7.sh, setting:
MYST_FMW to point to Oracle FMW home
MYST_ARTIFACT_DEPLOY_PREFIX to do a maven deploy rather than install. e.g (note that MYST_ARTIFACT_DEPLOY_PREFIX is commented out for install):
export MYST_FMW=/u01/app/oracle/product/fmw
export MYST_OSB=$MYST_FMW/Oracle_OSB1
export MYST_TEMP=/tmp
set -e
#export MYST_ARTIFACT_DEPLOY_PREFIX=install:install-file
export MYST_ARTIFACT_DEPLOY_PREFIX="deploy:deploy-file -Durl=http://admin:password@127.0.0.1:8083/artifactory/libs-release-local"
set -e
...
Retrieving the MyST CLI from the MyST Studio container
To access the above 11g build parents, you will need to have MyST CLI installed. You can download this from the MyST website or you can access it from within an existing MyST Studio container at /usr/local/tomcat/conf/fusioncloud/agent/myst-impl.zip. Here is how to access it from the MyST Studio container.
