[
https://issues.apache.org/jira/browse/OFBIZ-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399281#comment-15399281 ]
Taher Alkhateeb commented on OFBIZ-7930:
----------------------------------------
One idea comes to my mind is not to load the plugin unless you pass a project property. It is easy to code that during the configuration phase of Gradle and it has the added benefit of hiding this stuff away from regular users and reducing the help menu. Another idea is to create the plugin in a subproject (/tools for example) and do whatever you want in there. This would also have the added benefit of moving all unwanted tasks to it. For example, we move svnInfoFooter, gitInfoFooter, copyDtds also to that build.gradle away from the master build script.
Food for thought!
> Copy external jars in OFBiz $buildDir/externalJars for (at least) dependency check
> ----------------------------------------------------------------------------------
>
> 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
>
>
> 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
