Gradle issuesGradle issueshttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1130324032024-03-28T18:24:22Z2024-03-28T18:24:22ZRE: Gradle issuesLee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1131261842019-04-10T19:27:06Z2019-04-10T19:27:06ZCompletley agree. I never go off network on public WiFi but would when working from home on my own wired eth.Lee Jordan2019-04-10T19:27:06ZRE: Gradle issuesDavid H Nebingerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1131067622019-04-10T04:35:41Z2019-04-10T04:35:41Z<blockquote>Lee Jordan<br /><br />we recently had our proxy just outright block CDN's that gradle was trying to get dependencies from.</blockquote>I hate these kinds of heavy-handed security "solutions".<br /><br />I would argue your situation is worse now. Since you're building outside of the organization, the organization has no control over what dependencies you're using or where they are sourcing from. "Here, just use this binary I made for you, you can trust me..." Nonsense. Their kneejerk reaction to block CDNs is a higher risk than they realize.<br /><br />There are appropriate ways to handle dependencies from a security standpoint.<br /><br />An HTTP proxy is one, you can limit the external source sites where dependencies can come from. Not going to be super controlling but can give an audit trail if anyone is looking.<br /><br />A better solution is a Maven caching proxy such as Nexus or Artifactory. These guys can host artifacts the organization approves of and they can be configured to allow pulling from approved external sources, plus there's the regular old auditing stuff, etc. <br /><br />All of these features combine to provide the kind of protection the organization wants to enforce without styming development or, even worse, forcing developers to build offsite and ship the binaries in.David H Nebinger2019-04-10T04:35:41ZRE: Gradle issuesLee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1130919692019-04-09T14:08:07Z2019-04-09T14:08:07ZHey David, we recently had our proxy just outright block CDN's that gradle was trying to get dependencies from. So even going through authentication didn't work, we had to build projects away from our corporate network. Something for the documentation folks?<br /><br />Do we really have to use gradle to build themes? <img alt="emoticon" src="@theme_images_path@/emoticons/sad.gif" ><br /><br />Amitosh try this<br /><a href="https://dev.liferay.com/en/develop/tutorials/-/knowledge_base/7-0/themes-generator">https://dev.liferay.com/en/develop/tutorials/-/knowledge_base/7-0/themes-generator</a><br /><a href="https://dev.liferay.com/en/develop/tutorials/-/knowledge_base/7-1/creating-themes">https://dev.liferay.com/en/develop/tutorials/-/knowledge_base/7-1/creating-themes</a>Lee Jordan2019-04-09T14:08:07ZRE: Gradle issuesDavid H Nebingerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1130338452019-04-05T13:23:56Z2019-04-05T13:23:56ZYou haven't configured your proxy settings: <a href="https://dev.liferay.com/en/develop/tutorials/-/knowledge_base/7-0/setting-proxy-requirements-for-liferay-ide">https://dev.liferay.com/en/develop/tutorials/-/knowledge_base/7-0/setting-proxy-requirements-for-liferay-ide</a>David H Nebinger2019-04-05T13:23:56ZRE: Gradle issuesAmitosh Kumarhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1130329802019-04-05T13:11:00Z2019-04-05T13:11:00ZPlease find attachement . Amitosh Kumar2019-04-05T13:11:00ZGradle issuesAmitosh Kumar