[
https://issues.apache.org/jira/browse/OFBIZ-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464830#comment-15464830 ]
Taher Alkhateeb commented on OFBIZ-7930:
----------------------------------------
That might be an overkill Jacques. This would substantially complicate the script for something which very few people would actually use.
Also, the plugin is reliant on mavenCentral, not jcenter. So all that you need to do is delete $HOME/.m2 and you're done (unless you have other things that depend on mavenCentral). But even if not the case, I think what you are trying to accomplish would be a lot of work for little value.
> Load the OWASP dependency checker Gradle plugin efficiently
> -----------------------------------------------------------
>
> Key: OFBIZ-7930
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7930> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7534.patch
>
>
> As I warned at
https://cwiki.apache.org/confluence/display/OFBIZ/About+OWASP+Dependency+Check it's currently difficult to separate the OFBiz jars from other jars in the .gradle\caches contains which may contain jars unrelated to OFBiz. Notably Eclipse jars if you use the Gradle Eclipse task and more if you use Gradle for other reasons than OFBiz.
> I did not find yet a way to avoid to have all external jars in .gradle\caches and I wonder if it's even possible. What I would like to have is the external jars mandatory for OFBiz to work in an isolated place. For instance a sub folder of the main Gradle build folder. I picked $buildDir/externalJars.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
