[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419319#comment-15419319 ]
Taher Alkhateeb commented on OFBIZ-7910:
----------------------------------------
You are absolutely right and you guessed right, my answer is temporary. Right now I'm just trying to help Wai to make sure there are no bugs in the build system (I believe there are none as far as lib importing is concerned).
Perhaps a permanent solution is to get rid of all /lib folders and just keep an empty one in root folder. Given that we do not really need the custom classloader and we can just share the libraries with all components (cleaner, easier, integrated and detects conflicts early).
So if we do decide to adopt the permanent solution described above, we can use the code snippet I provided to Wai. No strong opinion, whatever you guys prefer.
> Improve component template(s) to work with the Gradle solution
> --------------------------------------------------------------
>
> Key: OFBIZ-7910
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7910> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
> Reporter: Pierre Smits
> Assignee: Jacques Le Roux
> Priority: Trivial
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have the means to work with the Gradle build solution visavis dependency management.
> The reason for this is that no build.gradle template exists that need to be copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
