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

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

I'm not against moving demo (and even other types if they exist, I hope not, 
not even a real worry anyway) data down the stack. It was just a reaction, a 
reflex I could say, I often have when I'm confronted with legacy. I have been 
bitten so much time, than I, often unconsciously, try to keep the concept. here 
to have these data in ecommerce  ofbiz-component.xml file to make clear it's 
used by this component. Actually a simple comment in, here, marketing would do 
(almost) the same. Almost because there is an indirection, and I believe this 
is why it was put there in 1st place (could be wrong on that but ASF repo can't 
tell, it's pre Apache era).

I guess Pierre means that we should not simply move data but also check before 
if we cannot improve them by removing redundancy or/and inadequacy. Quite a 
task I'd say. If it's what Pierre want to do, I'd recomment to create a "long 
term" improvement Jira...

> move base component demo data from specialpurpose/ecommerce to base components
> ------------------------------------------------------------------------------
>
>                 Key: OFBIZ-7016
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7016
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: specialpurpose/ecommerce
>    Affects Versions: Trunk
>            Reporter: Pierre Smits
>            Priority: Critical
>         Attachments: demo_marketing_moved.patch
>
>
> Currently a lot of demo data exists in the ecommerce component that should go 
> into the appropriate base components (e.g. party, product, etc)...
> If a adopting organisation wants to assess OFBiz without the components in 
> special purpose (which should be possible), loading of the demo data of sec 
> the base components fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to