The Buildbot has detected a new failure on builder ofbiz-trunk-ARM while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/ofbiz-trunk-ARM/builds/498
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-cal-2_ubuntu_ARM
Build Reason: scheduler
[
https://issues.apache.org/jira/browse/OFBIZ-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13749909#comment-13749909
]
Parimal Gain commented on OFBIZ-5297:
-
Thanks Jacques and Taher. I think both of you
Hans,
Normally, we report problems on the mailing list, not revert someone
else's commit.
This was rude and uncalled for. If I did the same thing to your buggy
commits, none of your contributions would make it into the project.
-Adrian
On 8/25/2013 11:28 PM, hans...@apache.org wrote:
I'd add that using trunk for clients's projects should not be an excuse, you
can always revert locally, waiting for a definitive solution...
Jacques
Adrian Crum wrote:
Hans,
Normally, we report problems on the mailing list, not revert someone
else's commit.
This was rude and uncalled
[
https://issues.apache.org/jira/browse/OFBIZ-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux resolved OFBIZ-5267.
Resolution: Fixed
Net before overhead report generates an error
[
https://issues.apache.org/jira/browse/OFBIZ-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reopened OFBIZ-5267:
Net before overhead report generates an error
[
https://issues.apache.org/jira/browse/OFBIZ-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-5267:
---
Attachment: OFBIZ-5267 - Net before overhead report generates an error.patch
Hi all,
This
[
https://issues.apache.org/jira/browse/OFBIZ-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13749968#comment-13749968
]
Jacques Le Roux commented on OFBIZ-5267:
OK wait, there is a circular reference
[
https://issues.apache.org/jira/browse/OFBIZ-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13749971#comment-13749971
]
Jacques Le Roux commented on OFBIZ-5297:
Damn wrong Jira issue :D
[
https://issues.apache.org/jira/browse/OFBIZ-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-5297:
---
Attachment: (was: OFBIZ-5267 - Net before overhead report generates an
error.patch)
[
https://issues.apache.org/jira/browse/OFBIZ-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-5297:
---
Attachment: OFBIZ-5267 - Net before overhead report generates an error.patch
I simply forgot
[
https://issues.apache.org/jira/browse/OFBIZ-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-5267:
---
Attachment: OFBIZ-5267 - Net before overhead report generates an error.patch
I simply forgot
[
https://issues.apache.org/jira/browse/OFBIZ-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reopened OFBIZ-5267:
For OFBIZ-4794, I track issues to be backported. This is one of those = reopen
[
https://issues.apache.org/jira/browse/OFBIZ-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-5297:
---
Comment: was deleted
(was: Damn wrong Jira issue :D
)
Order Report Issue
[
https://issues.apache.org/jira/browse/OFBIZ-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-5297:
---
Comment: was deleted
(was: I simply forgot to remove the includes to facility and accouting
[
https://issues.apache.org/jira/browse/OFBIZ-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux resolved OFBIZ-5267.
Resolution: Incomplete
OK forgot how I track them :D (I actually use incomplete status).
[
https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13749996#comment-13749996
]
Jacques Le Roux commented on OFBIZ-4952:
OFBIZ-5267 ready to test
[
https://issues.apache.org/jira/browse/OFBIZ-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13749997#comment-13749997
]
Jacques Le Roux commented on OFBIZ-5297:
OFBIZ-5267 ready to test
[
https://issues.apache.org/jira/browse/OFBIZ-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750005#comment-13750005
]
Jacques Le Roux commented on OFBIZ-5267:
Note: this must be tested with trunk and
Pierre Smits created OFBIZ-5299:
---
Summary: ProudctionRunServices.xml doesn't set
dateTimeManufactured in inventoryItem
Key: OFBIZ-5299
URL: https://issues.apache.org/jira/browse/OFBIZ-5299
Project:
[
https://issues.apache.org/jira/browse/OFBIZ-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-5299:
Attachment: OFBIZ-5299-ManufacturingServices.patch
Following patch corrects the issue.
Pierre Smits created OFBIZ-5300:
---
Summary: ProductionRunServices doens't set UoM of goods in
inventoryItems
Key: OFBIZ-5300
URL: https://issues.apache.org/jira/browse/OFBIZ-5300
Project: OFBiz
Fixed in rev 1517611.
Not only was this revert unnecessary, the commit message is false. The
Tomahawk theme was entirely usable, but one drop-down menu had a
slightly broken layout.
-Adrian
On 8/26/2013 1:47 AM, Adrian Crum wrote:
Hans,
Normally, we report problems on the mailing list,
Adrian,
Normally I would try to fix a problem and i did this pretty often.
Because this was a blocking problem i saw no other way then to revert it.
Very good to hear you like my commits which at least make a difference
for our end users. Although i personally appreciate your framework
Jacques,
Blocking, obvious problems like this one , should not be committed to
the trunk, they upset other developers because the system becomes un-usable.
Our customers do not use the trunk, so that is not a problem, but use a
version which run at our staging server for a month. We call it a
No one is asking you to fix anything. All you had to do was post a
message and I would have fixed it.
There was nothing blocking about my commit, and as I said there was no
reason to revert it.
Reverting a commit the way you did is NOT co-operation, and co-operation
is a concept you
26 matches
Mail list logo
