Hi all,
after a recent upgrade of the Jira server of the Apache Software
Foundation, the ASF Infrastructure team has setup the Fisheye plugin for
a few projects, including OFBiz.
You can now see the Fisheye tab in different spots in Jira; I'm sure
this will be a very useful tool for
Hi Hans,
if it's possible I don't want to lose my last translations inside the patch for
the issue OFBIZ-1619 (https://issues.apache.org/jira/browse/OFBIZ-1619).
In this patch I have inserted also some new CommonUiLabels.
Is it possible for you include those labels into the new
Great,
I hope performance concerns on infra ML will not pop up
Jacques
From: Jacopo Cappellato [EMAIL PROTECTED]
Hi all,
after a recent upgrade of the Jira server of the Apache Software
Foundation, the ASF Infrastructure team has setup the Fisheye plugin for
a few projects, including
Thinking more about this...
in the sales order the drop shipment method is defined at ship group
level (by setting the OrderItemShipGroup.supplierPartyId field); the
same order item could be split into different ship groups, and only some
of them could be for drop shipments.
What if we don't
David,
thank you for your valuable feedback; please see my comments inline:
David E Jones wrote:
It sounds like Adrian's comments are a great scenario to address, but
probably only one of various that we should target.
In general with this sort of thing (or designing anything really) I
Thanks for your comments David. I still need the accessor methods for some screen widget
enhancements I'm working on. So instead of reverting, I'll change the code a bit.
-Adrian
David E Jones wrote:
This is an okay pattern Adrian, but one that is avoided in most parts
of the framework.
That's totally fine, you can certainly adjust instead of revert.
The main point is that every time a form (or screen or ftl or
whatever) is rendered that the cache entry for it gets hit.
-David
On Feb 7, 2008, at 12:35 PM, Adrian Crum wrote:
Thanks for your comments David. I still need
This is an okay pattern Adrian, but one that is avoided in most parts
of the framework.
The reason is caching and a balance between production performance and
development convenience.
In production looking up a local field in an object is definitely
faster than doing a Map lookup, but
Accounting Error when completing a POS order
Key: OFBIZ-1623
URL: https://issues.apache.org/jira/browse/OFBIZ-1623
Project: OFBiz
Issue Type: Test
Components: ALL COMPONENTS
Affects
On Feb 7, 2008, at 5:46 AM, Jacopo Cappellato wrote:
David,
thank you for your valuable feedback; please see my comments inline:
David E Jones wrote:
It sounds like Adrian's comments are a great scenario to address,
but probably only one of various that we should target.
In general with
[
https://issues.apache.org/jira/browse/OFBIZ-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566718#action_12566718
]
Jacques Le Roux commented on OFBIZ-1622:
David's proposition even cooler :o)
[
https://issues.apache.org/jira/browse/OFBIZ-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566801#action_12566801
]
jacopoc edited comment on OFBIZ-1623 at 2/7/08 1:19 PM:
--
[
https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566898#action_12566898
]
Chris Lombardi commented on OFBIZ-1580:
---
Yes, the height works very well. It's not
Hi Marco...
your changes are re-applied in revision 619785.
Regards,
Hans
On Thu, 2008-02-07 at 11:22 +0100, [EMAIL PROTECTED] wrote:
Hi Hans,
if it's possible I don't want to lose my last translations inside the patch
for the issue OFBIZ-1619
14 matches
Mail list logo
