The problem was, that developers could decide to either have the new features
from one or the other branch, leaving some goodies behind. That finally ends with the 12c release for the most part. Let's review some
scenarios and see which version should you use at the moment:
We are an ISV developing a stand alone ADF application, which is going to be
deployed on premise.
In this case it makes sense to use JDeveloper 12c and get the best from both
worlds. Even if you are extending your web application with ADF Mobile
application later on, you will have no problems as ADF Mobile is only using
standard SOAP/REST web services to communicate with your 12c ADF application.
We want to develop ADF Mobile application and deploy it on iOS and Android.
You need to use JDeveloper 188.8.131.52 for the ADF Mobile application. It does
NOT mean your web/back-end application needs to be developed with this version
We are developing SOA/BPM/Portal application
In this case, you need to stay with 184.108.40.206 for a while, as Oracle Fusion
Middleware 12c has not been released yet.
We want to develop an ADF application and host it on the Oracle Public Cloud
Oracle Public Cloud only supports ADF R1/PS5 at this time, so you should develop
your application with JDeveloper 220.127.116.11
I am a developer and I would like to use ADF for my project, but I don't
have the budget for WebLogic server
We have a free version of ADF called ADF essentials, and it has been
updated to 12c. You can use that and deploy your application on GlassFish.
Here is a version map which can help you make the right decision:
Provided by Oracle FMW Evangelist Jernej Kase email@example.com