So I’ve been pushing this build migration to Gradle for quite some time now. Between third party bugs and other tasks and the monstrously huge size of our build (which is why we needed something that performs in the first place), it’s taken at least a year and a half. I think we waited 9 months to see if IntelliJ would fix their issues but this was in vain and we had to adapt our build so that both Eclipse and IntelliJ would work. Now I’ve got it running and I’d like to show everyone how much faster it is than Maven… except I can’t. It isn’t faster. It’s about the same. I’d like to do some investigating but I can’t do that either since the --profile option seems to have been castrated. I know Gradle has a cloud widget which we can’t use in accordance with our corporate security and intellectual property policies, nor would I ever recommend an unnecessary third party exposure to anyone else. I’d be more likely to recommend an open source fork of Gradle or at least a plugin that does what is needed and does it locally (and securely).
Soooo… what do I do next? I suppose what I’ll have to do, for now, is downgrade long enough to figure out the bottleneck unless someone has a better idea.