Migration Wizard In Jdeveloper 12.2.1.3.0 Leads To Maven Pom File Errors In SOA Projects (wrong Version )
(Doc ID 2504013.1)
Last updated on MAY 15, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version
Migration wizard in Jdeveloper 12.2.1.3.0 leads to Maven Pom file errors in SOA projects (wrong version )
When migration existing SOA projects with a Maven pom file from SOA JDeveloper 12.1.3 to 12.2.1.3.0 this results in errors on the Maven Pom file. Error when building the Effective Pom: "Non-resolvable parent pom".
The error is caused by a wrong version number in the POM; version 12.2.1-0-0 for the parent POM and the POM Hierarchy instead of 12.2.1-3-0.
See below apart of the POM file after running the migration wizard when opening the Application for the first time in Jdeveloper 12.2.1.3.0:
When manually changing the version tags to 12.2.1-3-0 the Pom can be used to deploy the project with Maven again.
ERROR
-----------------------
Non-resolvable parent pom
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |