[ 
https://issues.apache.org/jira/browse/OFBIZ-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476061#comment-15476061
 ] 

Pierre Smits edited comment on OFBIZ-8156 at 9/15/16 7:50 AM:
--------------------------------------------------------------

There isn't clarity within the project about where to move it too. But the code 
has to get out of where it is now. So this is just a part.

Furthermore, I doubt whether the code is even working. Last insightful 
references in MLs were around 2012 and these weren't compliments, and the 
reactions from community members didn't make me have faith.


was (Author: pfm.smits):
There isn't clarity within the project about where to move it too. But the code 
has to get out of where it is now. So this is just a part.

Furthermore, I doubt whether the code is even working. Last insightful 
references in MLs were around 2012 and these weren't complements, and the 
reactions from community members didn't make me have faith.

> 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)

Reply via email to