ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Le Roux (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-8156) Disentangle Fedex solution from current integrated state
Date Thu, 15 Sep 2016 09:33:20 GMT

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

Jacques Le Roux commented on OFBIZ-8156:
----------------------------------------

SInce there are 2 parts, maybe we could rename this Jira remove and add a link to another
Jira where the new stuff would be put in. Unfotunately Jira does not allow more than 1 level
for subtasks. Else we could also have an umbrella subtask named disentangle which would group
the 2 others.

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

Mime
View raw message