Pierre Smits created OFBIZ-6714:
---
Summary: Removing unexplained TODO from Manufacturing services
Key: OFBIZ-6714
URL: https://issues.apache.org/jira/browse/OFBIZ-6714
Project: OFBiz
Issue
[
https://issues.apache.org/jira/browse/OFBIZ-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-6714:
Attachment: OFBIZ-6714-ProductionRun.java.patch
This patch addresses the issue.
> Removing
[
https://issues.apache.org/jira/browse/OFBIZ-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits reassigned OFBIZ-6714:
---
Assignee: Pierre Smits
> Removing unexplained TODO from Manufacturing services
>
[
https://issues.apache.org/jira/browse/OFBIZ-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne closed OFBIZ-6714.
---
> Removing unexplained TODO from Manufacturing services
>
Don't worries Jacques, I create the hot-fix quickly for stable environment.
Thanks to having finalized this on trunk and complete the jira issue !
Nicolas
Le 02/11/2015 13:10, Jacques Le Roux a écrit :
Thanks Nicolas, just did the same on trunk (was my bad)
Jacques
Le 02/11/2015 10:11,
[
https://issues.apache.org/jira/browse/OFBIZ-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14997394#comment-14997394
]
Gil Portenseigne commented on OFBIZ-6714:
-
Indeed this TODO is here for more than 9 years and the
[
https://issues.apache.org/jira/browse/OFBIZ-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gil Portenseigne reassigned OFBIZ-6714:
---
Assignee: Gil Portenseigne (was: Pierre Smits)
> Removing unexplained TODO from
Nicolas,
as explained before this java call is just a hook to an external java
program which is called when the new test type is used which was added
to the XSD as part of the patch. The required code can be added to the
hot-deploy directory. We provided an example component with
Hi Nicolas,
The 13.07 to me was a painful release to deal with because of stripping out the
specialpurpose components. Also disabling these components means lower quality,
no testing and no guarantee of being compatible with the current version of
trunk. So i would imagine this to be sort of
Hello,
I arrive after the war but :)
This issue is interesting for many points and I keep :
* ModelTestSuite.java I'm afraid to see dead code, the call 'if
("webdriver-test".equals(nodeName)' will be never use for a standard
OFBiz and some new user won't understand why we call a non existent
[
https://issues.apache.org/jira/browse/OFBIZ-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998122#comment-14998122
]
Pierre Smits commented on OFBIZ-6703:
-
If you find any bugs, feel free to create new JIRA issues.
>
Hello,
With some latest great discussion about keep or not keep specialpurpose
components on branch, I some inconvenience come from that a
specialpurpose can be overload the definition (service, entity or
something like that) present on application component.
It's easier, we can comment all
Pierre Smits created OFBIZ-6713:
---
Summary: Have ShipmentServices.java work with configurable aspects
regarding integration 3rd party shipment providers
Key: OFBIZ-6713
URL:
Interesting, but should we use it to change and format OOTB files?
Jacques
Le 08/11/2015 18:13, Adrian Crum a écrit :
minilang.properties:
# Enable mini-language auto-correction. If set to true, mini-language will
attempt
# to correct common syntax errors. The corrections are saved in the
Hi Jinghai,
Any chances?
Jacques
Le 24/10/2015 14:20, Jacques Le Roux a écrit :
Hi Jinghai,
I just spotted the specialpurpose/runtime component. It's related to Solr, I
guess it should not be committed, or at least not at this place?
Thanks
Jacques
Le 06/10/2015 14:48, sh...@apache.org
15 matches
Mail list logo
