[
https://issues.apache.org/jira/browse/OFBIZ-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15492813#comment-15492813 ]
Taher Alkhateeb commented on OFBIZ-8156:
----------------------------------------
Given that you provided a dictionary link you should know that disentangle is NOT the same as remove. To disentangle is to separate things, whereas remove is to eliminate or get rid of. The title of this JIRA is misleading because I spent time looking at your patch to see how is it that you are disentangling before I realized you are actually just removing things. This time could have been saved with a proper usage of words.
> Disentangle Fedex solution from current integrated state
> --------------------------------------------------------
>
> Key: OFBIZ-8156
> URL:
https://issues.apache.org/jira/browse/OFBIZ-8156> Project: OFBiz
> Issue Type: Sub-task
> Components: commonext, datamodel, order, product, specialpurpose/ecommerce, specialpurpose/oagis, specialpurpose/webpos
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Priority: Minor
> Labels: 3rdParty, integration, shipment
> Attachments: OFBIZ-8156-FedexRemoval.patch
>
>
> Disentanglement of the 3rd party shipment integration for FedEx gives the OFBiz adopter more flexibility, reduces the default code base and offers the project more opportunities with respect to attracting product specific contributors, better code and faster release cycles.
> Requirements of the disentangled solution:
> * should not need a separate entity to capture configuration elements
> * configuration should be contained in the component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
