Le 08/12/2015 20:59, Nicolas Malin a écrit :
Le 19/11/2015 11:45, Jacques Le Roux a écrit :
Could we list, apart the well known Birt issue, special components which
are overriding main applications?
Directly by memory, the scrum components has defined new seca on cust
request to send email that break the standard customer request system
An other where I failed, used service findProductsById instead of
findProductById, the first from hhfacilty and the second from catalog. And
want you start your hot-deploy component without specialpurpose ... paff !
:)
Thanks for these points Nicolas, I agree with Pierre suggestion.
For instance does really the hhfacilty findProductById service needs to be
named the same than in product? Etc.
Of course I'm also for this, but the problem isn't on the capacity to open a
jira issue.
Nicolas
OK, I had an idea. Why not commenting out the specialpurpose components by default, but
uncomment those which have proved to "not be a problem"?
"Not be a problem" means here which are not overriding applications component. So we could create a "Comment out specialpurpose components by default"
Jira
with possible subtasks for litigious cases (when we find an issue after
uncommenting out)
I suggest though that we don't do that on trunk (which would still contains all components active) but on the next frozen release. We could even do it
on R14.12 if we have a consensus.
To start, I'd at least uncomment out:
example
exampleext
pos
ecommerce(? if not OK then we create the main Jira and a subtask for it)
Adds your please...
Opinions?
Jacques
