But in Online mode, cert issue is not resolving, after fixing JDK Installation.
Well, then you either did not fix the installation, or maybe you use a bad proxy, or there is a man-in-the-middle attack, or any other of the possible reasons. Impossible to guess from here. You might want to set the system property javax.net.debug
to all
to get very detailed logging about HTTPS connection procedure, used certificates and so on. Maybe that will help you to figure out the problem.
We tried to use openjdk1.0
No idea what that should be, actually. 
In the server, I have tried to download this file via CURL and Wget but it did not work.
curl -o test.pom https://jcenter.bintray.com/org/springframework/boot/spring-boot-buildpack-platform/3.0.4/spring-boot-buildpack-platform-3.0.3.pom
curl: (60) Peer’s certificate issuer has been marked as not trusted by the user.
Well, if even curl
cannot download the file, why do you think it is a Gradle problem?
Even more a hint it is a different problem not related to Gradle.
Make your IT make the curl
work and maybe they fixed it then for Gradle too.
Here, your curl
command works fine.
Besides that it returns 404 not found as you mixed 3.0.4
and 3.0.3
in the URL. But with twice the same version in the URL it downloads just fine here.
Shall we use gradlepluginPortal() to resolve this dependency ?
The Gradle Plugin Portal does not have this dependency, so it would just send a redirect to JCenter.
JCenter would then forward the request to Maven Central as JCenter also does not have that dependency itself.
You could try to add Maven Central as repository before JCenter or Gradle Plugin Portal.
Actually I would recommend not using JCenter at all explicitly due to its quirks unless you really need something from it and always prefix it with Maven Central so get things from Maven Central directly even if JCenter is down again.
So for plugin repositories I’d define “Maven Central” first and “Gradle Plugin Portal” second as long as the Gradle Plugin Portal redirects to JCenter for missing dependencies.
This way things on Maven Central are fetched from Maven Central directly, everything else is got from Gradle Plugin Portal which redirects to JCenter for thing it does not have itself which should only be the things actually available on JCenter as Maven Central ones were fetched directly already.
as mentioned in this link, JCenter Shutdown Impact on Gradle Builds.
There is not really an Impact, as JCenter was not and will not be shutdown.
It was just set to read-only and regularly has outages as it always had.