[
https://issues.apache.org/jira/browse/OFBIZ-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530967#comment-16530967
]
Taher Alkhateeb commented on OFBIZ-9793:
----------------------------------------
A fix if needed for this Jira is rather minor with just exclusion patterns in
build.gradle which already exist.
Furthermore, each baseline never had an isolated structure to begin with. They
just had separate jar files. We did not implement java sub-projects in gradle
like it was with ant (although we can) but the whole class loading logic in the
end lead to the same result., Components cannot (and in my opinion, should not)
be isolated from each other as far as class loading is concerned. The mess was
scattered in many build.xml files and everything was integrated into one
build.gradle file. This actually brought the mess right to our faces. It was
this integration work that showed us how much mess was there int he first place.
Anyway, without a specific implementation action, I recommend closing this JIRA.
> Do *NOT* place config files into ofbiz.jar.
> -------------------------------------------
>
> Key: OFBIZ-9793
> URL: https://issues.apache.org/jira/browse/OFBIZ-9793
> Project: OFBiz
> Issue Type: Bug
> Components: Gradle
> Affects Versions: Trunk
> Reporter: Adam Heath
> Priority: Minor
>
> Placing so many properties/xml stuff from each and every $component/config
> makes it very very very difficult to provide deployment overrides, without
> doing a full rebuild of the ofbiz.jar. The deploy system should not be
> running a build environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
