I am doing work for a very large, international company. They use maven everwhere and don’t seem to know a lot about Gradle. I would like to introduce Gradle but my problem is as follows.
Maven works fine through their corporate firewall / proxy, Gradle does not. It is my impression that Gradle has stricter security requirements (HTTPS, etc.). I would like it if Gradle had a simple way of disabling those strict requirements so that I can:
A. easily get Gradle to work so that I can demo it (and use it in the future)
B. rely on their corporate firewall / proxy for security rather than having Gradle enforce any
I understand that there are ways of configuring Gradle to retain it’s security requirements and get it to work in this corporate environment, but the problem is as follows:
The barrier to entry is too high. It takes too much work / time to figure out how to get it working for a developer who’s not well connected to their corporate network configuration.
It’s hard to get corporate assistance when they are happy with what works. A bit of a chicken and egg problem.
So, what I am looking for is a very simple, single flag or environment variable to set to allow Gradle to work in a very restricted corporate environment. I will rely on their corporate security mechanisms for security assurances.
If I can’t get Gradle to work myself, they’ll remain a maven shop.