Re: Bootstrap dev branch
There are significant changes in the bootstrap dev branch regarding widgets, that aren't reflected in trunk. I tried the bootstrap theme in my dev for trunk and it gave errors. It seems to me that best would be to bring bootstrap dev in sync with branch, fix the issues registered and then, when there is consensus, port back to trunk. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, May 19, 2015 at 9:30 AM, Julien NICOLAS julien.nico...@nomaka.fr wrote: What could be the best way to keep this work alive ? I propose to make diff between bootstrap branch and trunk and make a patch with bootstrap theme and GUI modifications. It's a manual merge but it could work ;) What do you think ? Julien. Le 18/05/2015 13:05, Jacques Le Roux a écrit : I tried but got this Command: Auto-merge https://svn.apache.org/repos/asf/ofbiz/trunk into C:\projectsASF\boostrap_theme Error: Reintegrate can only be used if revisions 1634810 through 1679986 were Error: previously merged from Error: https://svn.apache.org/repos/asf/ofbiz/branches/boostrap_theme to the Error: reintegrate source, but this is not the case: Error: ofbiz/trunk Error: Missing ranges: /ofbiz/branches/boostrap_theme:1634810,1635414,1635439 Gave up Jacques Le 18/05/2015 12:39, Pierre Smits a écrit : Hi all, Can we have an update on the bootstrap dev branch so that it has the latest from trunk? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
[jira] [Commented] (OFBIZ-6291) Update code to check for types rather than throw ClassCastException
[ https://issues.apache.org/jira/browse/OFBIZ-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549868#comment-14549868 ] Jacques Le Roux commented on OFBIZ-6291: Smart move, thanks Adrian! Update code to check for types rather than throw ClassCastException --- Key: OFBIZ-6291 URL: https://issues.apache.org/jira/browse/OFBIZ-6291 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk, Upcoming Branch Reporter: Gareth Carter Assignee: Adrian Crum Priority: Trivial Fix For: Upcoming Branch Attachments: LocalizedConverters.patch, minilang_compare.patch, minilang_compare_r1675655.patch framework/minilang/src/org/ofbiz/minilang/method/conditional/Compare.java framework/base/src/org/ofbiz/base/util/ObjectType.java framework/minilang/src/org/ofbiz/minilang/MiniLangUtil.java all throw ClassCastExceptions and are ignored instead of checking types This caused issues in debugging when adding a ClassCastException breakpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: svn commit: r1680155 - /ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml
Hi Christian,
When you commit please don't put only a reference to a Jira in your comment. Sometimes we have no Internet access and then here a (possibly
simplified) copy of the Jira description would fit. In more complicated cases it's good to at least give an idea of what is done by the commit.
Jacques
Le 19/05/2015 05:15, ccar...@apache.org a écrit :
Author: ccarlow
Date: Tue May 19 03:15:43 2015
New Revision: 1680155
URL: http://svn.apache.org/r1680155
Log:
JIRA OFBIZ-6387.patch
Modified:
ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml
Modified: ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml?rev=1680155r1=1680154r2=1680155view=diff
==
--- ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml
(original)
+++ ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml Tue
May 19 03:15:43 2015
@@ -58,8 +58,7 @@ under the License.
/field
field name=partyIdhidden//field
field name=applyingPartyId
title=${uiLabelMap.FormFieldTitle_applyingPartyId}lookup
target-form-name=LookupPartyName//field
-field name=referredByPartyId title=${uiLabelMap.FormFieldTitle_referredByPartyId}
use-when=quot;${referredByPartyId}quot;.equals(null)lookup
target-form-name=LookupPartyName//field
-field name=referredByPartyId use-when=referredByPartyId!=nulllookup
target-form-name=LookupPartyName//field
+field name=referredByPartyId
title=${uiLabelMap.FormFieldTitle_referredByPartyId}lookup
target-form-name=LookupPartyName//field
field name=applicationDate
title=${uiLabelMap.FormFieldTitle_applicationDate}date-time//field
field name=deleteLink title=${uiLabelMap.CommonDelete}
widget-style=buttontext
hyperlink target=deleteEmploymentApp
description=${uiLabelMap.CommonDelete} also-hidden=true
Re: svn commit: r1680155 - /ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml
Ha, we are on the same page Adrian, just sent the same kind of message, crossed
on wire :)
Jacques
Le 19/05/2015 05:25, Adrian Crum a écrit :
Please make the commit message more informative. What was changed/fixed? Also,
if there is a related Jira issue, then include a link to the issue.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 5/18/2015 8:15 PM, ccar...@apache.org wrote:
Author: ccarlow
Date: Tue May 19 03:15:43 2015
New Revision: 1680155
URL: http://svn.apache.org/r1680155
Log:
JIRA OFBIZ-6387.patch
Modified:
ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml
Modified: ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml?rev=1680155r1=1680154r2=1680155view=diff
==
--- ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml
(original)
+++ ofbiz/trunk/applications/humanres/widget/forms/EmploymentAppForms.xml Tue
May 19 03:15:43 2015
@@ -58,8 +58,7 @@ under the License.
/field
field name=partyIdhidden//field
field name=applyingPartyId
title=${uiLabelMap.FormFieldTitle_applyingPartyId}lookup
target-form-name=LookupPartyName//field
-field name=referredByPartyId title=${uiLabelMap.FormFieldTitle_referredByPartyId}
use-when=quot;${referredByPartyId}quot;.equals(null)lookup target-form-name=LookupPartyName//field
-field name=referredByPartyId use-when=referredByPartyId!=nulllookup
target-form-name=LookupPartyName//field
+field name=referredByPartyId
title=${uiLabelMap.FormFieldTitle_referredByPartyId}lookup
target-form-name=LookupPartyName//field
field name=applicationDate
title=${uiLabelMap.FormFieldTitle_applicationDate}date-time//field
field name=deleteLink title=${uiLabelMap.CommonDelete}
widget-style=buttontext
hyperlink target=deleteEmploymentApp
description=${uiLabelMap.CommonDelete} also-hidden=true
Re: Bootstrap dev branch
As far as 'bootstrap' themes go, I wouldn't create a redo of the Tomahawk theme. Having one (bootstrap-basic) would be enough to show the potential. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, May 19, 2015 at 9:51 AM, Pierre Smits pierre.sm...@gmail.com wrote: There are significant changes in the bootstrap dev branch regarding widgets, that aren't reflected in trunk. I tried the bootstrap theme in my dev for trunk and it gave errors. It seems to me that best would be to bring bootstrap dev in sync with branch, fix the issues registered and then, when there is consensus, port back to trunk. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, May 19, 2015 at 9:30 AM, Julien NICOLAS julien.nico...@nomaka.fr wrote: What could be the best way to keep this work alive ? I propose to make diff between bootstrap branch and trunk and make a patch with bootstrap theme and GUI modifications. It's a manual merge but it could work ;) What do you think ? Julien. Le 18/05/2015 13:05, Jacques Le Roux a écrit : I tried but got this Command: Auto-merge https://svn.apache.org/repos/asf/ofbiz/trunk into C:\projectsASF\boostrap_theme Error: Reintegrate can only be used if revisions 1634810 through 1679986 were Error: previously merged from Error: https://svn.apache.org/repos/asf/ofbiz/branches/boostrap_theme to the Error: reintegrate source, but this is not the case: Error: ofbiz/trunk Error: Missing ranges: /ofbiz/branches/boostrap_theme:1634810,1635414,1635439 Gave up Jacques Le 18/05/2015 12:39, Pierre Smits a écrit : Hi all, Can we have an update on the bootstrap dev branch so that it has the latest from trunk? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: Bootstrap dev branch
What could be the best way to keep this work alive ? I propose to make diff between bootstrap branch and trunk and make a patch with bootstrap theme and GUI modifications. It's a manual merge but it could work ;) What do you think ? Julien. Le 18/05/2015 13:05, Jacques Le Roux a écrit : I tried but got this Command: Auto-merge https://svn.apache.org/repos/asf/ofbiz/trunk into C:\projectsASF\boostrap_theme Error: Reintegrate can only be used if revisions 1634810 through 1679986 were Error: previously merged from Error: https://svn.apache.org/repos/asf/ofbiz/branches/boostrap_theme to the Error: reintegrate source, but this is not the case: Error: ofbiz/trunk Error: Missing ranges: /ofbiz/branches/boostrap_theme:1634810,1635414,1635439 Gave up Jacques Le 18/05/2015 12:39, Pierre Smits a écrit : Hi all, Can we have an update on the bootstrap dev branch so that it has the latest from trunk? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
[jira] [Closed] (OFBIZ-6371) Make background-color in setSourceColor function in fieldlookup.js theme dependent
[ https://issues.apache.org/jira/browse/OFBIZ-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6371. -- Resolution: Done Assignee: Jacques Le Roux Done at r Make background-color in setSourceColor function in fieldlookup.js theme dependent -- Key: OFBIZ-6371 URL: https://issues.apache.org/jira/browse/OFBIZ-6371 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Priority: Trivial Fix For: Upcoming Branch Fornow it's harcoded as yellow -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6276) Fix deprecation issues in framework/entity
[ https://issues.apache.org/jira/browse/OFBIZ-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550039#comment-14550039 ] Jacques Le Roux commented on OFBIZ-6276: Thanks Martin, I think we already used the same than your 2nd solution which I agree is simpler. Fix deprecation issues in framework/entity -- Key: OFBIZ-6276 URL: https://issues.apache.org/jira/browse/OFBIZ-6276 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Adam Heath Priority: Minor Attachments: OFBIZ-6276-variant-1.patch, OFBIZ-6276-variant-2.patch It appears that the storeAll() variants are being refactor; basically, the useCache parameter is being removed. However, this has caused the entity engine to have deprecation with itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-4481) Adding a new attribute ignore-when (verry similar to use-when) that enable rendering or not a field in list or multi form.
[ https://issues.apache.org/jira/browse/OFBIZ-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550044#comment-14550044 ] Wei Zhang commented on OFBIZ-4481: -- Hi youssef, May I know if you have a patch for latest trunk? Can you please share it if possible? Thanks, Wei Adding a new attribute ignore-when (verry similar to use-when) that enable rendering or not a field in list or multi form. -- Key: OFBIZ-4481 URL: https://issues.apache.org/jira/browse/OFBIZ-4481 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: youssef khaye Priority: Minor Labels: form, list, use-when Attachments: ignoreField.patch I need to define some parameters (using portlet attributes) that enable showing or not some field in my portlet taht contains a form of type list. Or on a form of type list or multi, it is not possible to completely ignore a field via use-when attribute. Instead it hides the title and the column header became shifted from the table content. For example I want to hide the description column from my form when exampleName is choosen as sort-field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-5610) Labels for UK date formats
[ https://issues.apache.org/jira/browse/OFBIZ-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reassigned OFBIZ-5610: Assignee: Michael Brohl Labels for UK date formats -- Key: OFBIZ-5610 URL: https://issues.apache.org/jira/browse/OFBIZ-5610 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Gareth Carter Assignee: Michael Brohl Priority: Trivial Attachments: gb_labels.patch Date formats displayed in the title of the input field are not correctly showing the default format for UK but the actual date itself is correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6312) Catalog Manager's EditProduct screen HTML should place a limit on the size of text that can be entered in the Product Description box
[
https://issues.apache.org/jira/browse/OFBIZ-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550097#comment-14550097
]
Pierre Smits commented on OFBIZ-6312:
-
Shouldn't the adjustment/extension regarding the widget-form.xsd not also
reference the default length?
{code}
xs:attribute type=xs:positiveInteger name=maxlength/
{code}
vs
{code}
xs:attribute type=xs:positiveInteger name=maxlength default=255/
{code}
Catalog Manager's EditProduct screen HTML should place a limit on the size of
text that can be entered in the Product Description box
-
Key: OFBIZ-6312
URL: https://issues.apache.org/jira/browse/OFBIZ-6312
Project: OFBiz
Issue Type: Improvement
Components: product
Affects Versions: Release Branch 14.12, Trunk, 12.04.05, 13.07.01
Reporter: Forrest Rae
Assignee: Michael Brohl
Attachments: OFBIZ-6312.patch
Catalog Manager's EditProduct and EditProductDup screens HTML should place a
limit on the size of text that can be entered in the Product Description box.
When more than 255 characters are entered an error is displayed. There is
no easy way of knowing when you've hit the 255 character max without the HTML
limiting it.
The patch I'm including changes the TextArea to include the maxlength
argument. This should be useful in other areas of the system.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6291) Update code to check for types rather than throw ClassCastException
[ https://issues.apache.org/jira/browse/OFBIZ-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550023#comment-14550023 ] Gareth Carter commented on OFBIZ-6291: -- Thanks Adrian. Update code to check for types rather than throw ClassCastException --- Key: OFBIZ-6291 URL: https://issues.apache.org/jira/browse/OFBIZ-6291 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk, Upcoming Branch Reporter: Gareth Carter Assignee: Adrian Crum Priority: Trivial Fix For: Upcoming Branch Attachments: LocalizedConverters.patch, minilang_compare.patch, minilang_compare_r1675655.patch framework/minilang/src/org/ofbiz/minilang/method/conditional/Compare.java framework/base/src/org/ofbiz/base/util/ObjectType.java framework/minilang/src/org/ofbiz/minilang/MiniLangUtil.java all throw ClassCastExceptions and are ignored instead of checking types This caused issues in debugging when adding a ClassCastException breakpoint -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5853) The createPartyRole service does not check a duplicate key.
[ https://issues.apache.org/jira/browse/OFBIZ-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-5853. -- Resolution: Fixed If ever you have something to add or think it should not be closed, please begins a thread in the dev ML, thanks! The createPartyRole service does not check a duplicate key. --- Key: OFBIZ-5853 URL: https://issues.apache.org/jira/browse/OFBIZ-5853 Project: OFBiz Issue Type: Bug Components: party Affects Versions: Trunk Reporter: Supatthra Nawicha Assignee: Nicolas Malin Priority: Minor Fix For: Trunk Attachments: OFBIZ-5853.patch, OFBIZ-5853.patch, ofbizbug_CreatePartyroleService.diff The createPartyRole service is changed from minilang to entity-auto which does not check a duplicate key. It effect to the createPartyRelationshipContactAccount service which call the createPartyRole service without check a duplicate key. And it might effect to other code that call the createPartyRole service as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reassigned OFBIZ-6373: Assignee: Michael Brohl CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6258) Trivial perfomance improvement for creating OrderItemAttributes during store/update Order
[
https://issues.apache.org/jira/browse/OFBIZ-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brohl reassigned OFBIZ-6258:
Assignee: Michael Brohl
Trivial perfomance improvement for creating OrderItemAttributes during
store/update Order
-
Key: OFBIZ-6258
URL: https://issues.apache.org/jira/browse/OFBIZ-6258
Project: OFBiz
Issue Type: Improvement
Components: order
Affects Versions: Upcoming Branch
Reporter: Martin Becker
Assignee: Michael Brohl
Priority: Trivial
Attachments: ShoppingCart-makeAllOrderItemAttributes.patch
Improved use of given mode parameter in {{makeAllOrderItemAttributes(String
orderId, int mode)}} to avoid creating new OrderItemAttribute GenericValues
that have not to be created according to the value for mode (FILLED_ONLY,
EMPTY_ONLY).
Change was made for a project with massive use of OrderItemAttributes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6312) Catalog Manager's EditProduct screen HTML should place a limit on the size of text that can be entered in the Product Description box
[ https://issues.apache.org/jira/browse/OFBIZ-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reassigned OFBIZ-6312: Assignee: Michael Brohl Catalog Manager's EditProduct screen HTML should place a limit on the size of text that can be entered in the Product Description box - Key: OFBIZ-6312 URL: https://issues.apache.org/jira/browse/OFBIZ-6312 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 12.04.05, 13.07.01 Reporter: Forrest Rae Assignee: Michael Brohl Attachments: OFBIZ-6312.patch Catalog Manager's EditProduct and EditProductDup screens HTML should place a limit on the size of text that can be entered in the Product Description box. When more than 255 characters are entered an error is displayed. There is no easy way of knowing when you've hit the 255 character max without the HTML limiting it. The patch I'm including changes the TextArea to include the maxlength argument. This should be useful in other areas of the system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14525722#comment-14525722 ] Jacques Le Roux edited comment on OFBIZ-4183 at 5/19/15 9:39 AM: - Hi Adrian, # I agree, I'd rather use layered-window, I did not notice this point when Sascha introduced it in example. It should not be big deal to change in custome projects, just a S/R. # I'm more circumspect here, because it would entail some work in our side and even more in custom projects and I don't clearly by why we would replace it, I think it's a picky BTW I will soon engage a discussion about maintaining widget not HTML part on the dev ML was (Author: jacques.le.roux): Hi Adrian, # I agree, I'd rather use layered-window, I did not notice this point when Sascha introduced it in example. It should not be big deal to change in custome projects, just a S/R. # I'm more circumspect here, because it would entail some work in our side and even more in custom projects and I don't clearly by why would replace it, I think it's a picky BTW I will soon engage a discussion about maintaining widget not HTML part on the dev ML Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Sascha Rodekamp Assignee: Adrian Crum Fix For: Trunk Attachments: LayeredLink_new.jpg, Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6386) compareBigDecimals in org.ofbiz.minilang.method.conditional.Compare does not compare certain values correctly
[ https://issues.apache.org/jira/browse/OFBIZ-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550061#comment-14550061 ] Gareth Carter commented on OFBIZ-6386: -- It may not perform calculations directly but it is a control statement in minilang, therefore calculations (or other code) may occur that were not expected. I only analysed ofbiz for usage not impact. I noticed the accounting component used if-compare and if-compare-field with type=BigDecimal and with accounting you generally want accuracy in terms of numbers, BigDecimal offers this but, to me compareBigDecimals does not. You lose information on comparison. Java code in ofbiz generally uses compareTo for comparison without modifying scale. Groovy code is the same as java (using compareTo), groovy also supports operator overloading which will use compareTo for relational operator overloading (eg, a == b) The compareBigDecimals method used in minilang behaves slightly different to those comparisons done in java or groovy but only for values like those in compareBigDecimals.png I will provide a patch for review as soon as I can compareBigDecimals in org.ofbiz.minilang.method.conditional.Compare does not compare certain values correctly - Key: OFBIZ-6386 URL: https://issues.apache.org/jira/browse/OFBIZ-6386 Project: OFBiz Issue Type: Bug Affects Versions: Trunk Reporter: Gareth Carter Priority: Minor Attachments: compareBigDecimals.png Moving the conversation from https://issues.apache.org/jira/browse/OFBIZ-6291 to this issue. compareBigDecimals scales down and rounds up meaning you lose information and the comparison result is not as expected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-4481) Adding a new attribute ignore-when (verry similar to use-when) that enable rendering or not a field in list or multi form.
[
https://issues.apache.org/jira/browse/OFBIZ-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550117#comment-14550117
]
Jacques Le Roux commented on OFBIZ-4481:
Interestin, quick non functional patch review
# This patch is not based on trunk, example is now in specialpurpose.
# Are you sure (did not try because of 1), you need to use
{code}
amp;amp;
{code}
in
{code}
set field=ignoreDescription value=${groovy: if(sortField amp;amp;
'exampleName'.equals(sortField)) return 'Y' else return 'N'}/
{code}
?
Adding a new attribute ignore-when (verry similar to use-when) that enable
rendering or not a field in list or multi form.
--
Key: OFBIZ-4481
URL: https://issues.apache.org/jira/browse/OFBIZ-4481
Project: OFBiz
Issue Type: Improvement
Components: ALL COMPONENTS
Affects Versions: Trunk
Reporter: youssef khaye
Priority: Minor
Labels: form, list, use-when
Attachments: ignoreField.patch
I need to define some parameters (using portlet attributes) that enable
showing or not some field in my portlet taht contains a form of type list.
Or on a form of type list or multi, it is not possible to completely ignore a
field via use-when attribute. Instead it hides the title and the column
header became shifted from the table content.
For example I want to hide the description column from my form when
exampleName is choosen as sort-field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: buildbot failure in ASF Buildbot on ofbiz-branch14
Hi everyone,
I investigated the build failure because I'm on the blamelist and found
that the build breaks directly after checking out the fresh version on
the server, without even building the code:
program finished with exit code 0
elapsedTime=23.983329
svn info --xml
in dir /home/buildslave2/slave2/ofbiz-branch14/build (timeout 1200 secs)
watching logfiles {}
argv: ['svn', 'info', '--xml']
environment:
HOME=/home/buildslave2
LANG=en_AU.UTF-8
LESSCLOSE=/usr/bin/lesspipe %s %s
LESSOPEN=| /usr/bin/lesspipe %s
LOGNAME=buildslave2
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:
MAIL=/var/mail/buildslave2
OLDPWD=/home/gmcdonald
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/home/buildslave2/slave2/ofbiz-branch14/build
SHELL=/bin/bash
SHLVL=1
SUDO_COMMAND=/bin/bash
SUDO_GID=2393
SUDO_UID=2393
SUDO_USER=gmcdonald
TEMP=/tmp/user/10006
TEMPDIR=/tmp/user/10006
TERM=screen
TMP=/tmp/user/10006
TMPDIR=/tmp/user/10006
USER=buildslave2
USERNAME=buildslave2
_=/usr/bin/buildslave
using PTY: True
program finished with exit code 0
elapsedTime=0.016973
Corrupted xml, aborting step
I have checked the latest build failures and this seems to happen once
in a while. Does anyone have a clue how to solve this?
Regards,
Michael Brohl
ecomify GmbH
www.ecomify.de
Am 19.05.15 um 12:27 schrieb build...@apache.org:
The Buildbot has detected a new failure on builder ofbiz-branch14 while
building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/ofbiz-branch14/builds/125
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: lares_ubuntu
Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz14-commit'
triggered this build
Build Source Stamp: [branch ofbiz/branches/release14.12] 1680233
Blamelist: mbrohl
BUILD FAILED: failed
Sincerely,
-The Buildbot
smime.p7s
Description: S/MIME Cryptographic Signature
[jira] [Updated] (OFBIZ-5610) Labels for UK date formats
[ https://issues.apache.org/jira/browse/OFBIZ-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-5610: - Fix Version/s: (was: 13.07.02) (was: 14.12.01) Release Branch 13.07 Release Branch 14.12 Trunk Labels for UK date formats -- Key: OFBIZ-5610 URL: https://issues.apache.org/jira/browse/OFBIZ-5610 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk Reporter: Gareth Carter Assignee: Michael Brohl Priority: Trivial Fix For: Release Branch 13.07, Release Branch 14.12, Trunk Attachments: gb_labels.patch Date formats displayed in the title of the input field are not correctly showing the default format for UK but the actual date itself is correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5610) Labels for UK date formats
[ https://issues.apache.org/jira/browse/OFBIZ-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-5610: - Affects Version/s: Release Branch 13.07 Release Branch 14.12 Labels for UK date formats -- Key: OFBIZ-5610 URL: https://issues.apache.org/jira/browse/OFBIZ-5610 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk Reporter: Gareth Carter Assignee: Michael Brohl Priority: Trivial Fix For: 14.12.01, 13.07.02 Attachments: gb_labels.patch Date formats displayed in the title of the input field are not correctly showing the default format for UK but the actual date itself is correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6276) Fix deprecation issues in framework/entity
[ https://issues.apache.org/jira/browse/OFBIZ-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550171#comment-14550171 ] Martin Becker commented on OFBIZ-6276: -- Hi Jacques, what do you mean with we already used the same? This issue is open and unassigned and I wanted to take a step forward to be able to work on OFBIZ-6273. Fix deprecation issues in framework/entity -- Key: OFBIZ-6276 URL: https://issues.apache.org/jira/browse/OFBIZ-6276 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Adam Heath Priority: Minor Attachments: OFBIZ-6276-variant-1.patch, OFBIZ-6276-variant-2.patch It appears that the storeAll() variants are being refactor; basically, the useCache parameter is being removed. However, this has caused the entity engine to have deprecation with itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6388) Licence header is missing in Seo*.xml files
Pierre Smits created OFBIZ-6388: --- Summary: Licence header is missing in Seo*.xml files Key: OFBIZ-6388 URL: https://issues.apache.org/jira/browse/OFBIZ-6388 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Trunk Reporter: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6388) Licence header is missing in Seo*.xml files
[ https://issues.apache.org/jira/browse/OFBIZ-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6388: --- Assignee: Pierre Smits Licence header is missing in Seo*.xml files --- Key: OFBIZ-6388 URL: https://issues.apache.org/jira/browse/OFBIZ-6388 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5610) Labels for UK date formats
[ https://issues.apache.org/jira/browse/OFBIZ-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-5610: - Fix Version/s: 14.12.01 Labels for UK date formats -- Key: OFBIZ-5610 URL: https://issues.apache.org/jira/browse/OFBIZ-5610 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk Reporter: Gareth Carter Assignee: Michael Brohl Priority: Trivial Fix For: 14.12.01, 13.07.02 Attachments: gb_labels.patch Date formats displayed in the title of the input field are not correctly showing the default format for UK but the actual date itself is correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5610) Labels for UK date formats
[ https://issues.apache.org/jira/browse/OFBIZ-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-5610: - Fix Version/s: 13.07.02 Labels for UK date formats -- Key: OFBIZ-5610 URL: https://issues.apache.org/jira/browse/OFBIZ-5610 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Gareth Carter Assignee: Michael Brohl Priority: Trivial Fix For: 13.07.02 Attachments: gb_labels.patch Date formats displayed in the title of the input field are not correctly showing the default format for UK but the actual date itself is correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
buildbot failure in ASF Buildbot on ofbiz-branch14
The Buildbot has detected a new failure on builder ofbiz-branch14 while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-branch14/builds/125 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz14-commit' triggered this build Build Source Stamp: [branch ofbiz/branches/release14.12] 1680233 Blamelist: mbrohl BUILD FAILED: failed Sincerely, -The Buildbot
[jira] [Updated] (OFBIZ-6388) Licence header is missing in Seo*.xml files
[ https://issues.apache.org/jira/browse/OFBIZ-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6388: Attachment: OFBIZ-6388-product-SEO.patch This patch fixes the issue. Licence header is missing in Seo*.xml files --- Key: OFBIZ-6388 URL: https://issues.apache.org/jira/browse/OFBIZ-6388 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits Attachments: OFBIZ-6388-product-SEO.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5610) Labels for UK date formats
[ https://issues.apache.org/jira/browse/OFBIZ-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-5610. fixed in trunk r1680219 R14.12 r1680233 R13.07 r1680226 Thanks Gareth for reporting and providing the patch. Labels for UK date formats -- Key: OFBIZ-5610 URL: https://issues.apache.org/jira/browse/OFBIZ-5610 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk Reporter: Gareth Carter Assignee: Michael Brohl Priority: Trivial Fix For: Release Branch 13.07, Release Branch 14.12, Trunk Attachments: gb_labels.patch Date formats displayed in the title of the input field are not correctly showing the default format for UK but the actual date itself is correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-5610) Labels for UK date formats
[ https://issues.apache.org/jira/browse/OFBIZ-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-5610: - Comment: was deleted (was: fixed in trunk r1680219 R14.12 r1680233 R13.07 r1680226 Thanks Gareth for reporting and providing the patch.) Labels for UK date formats -- Key: OFBIZ-5610 URL: https://issues.apache.org/jira/browse/OFBIZ-5610 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk Reporter: Gareth Carter Assignee: Michael Brohl Priority: Trivial Fix For: Release Branch 13.07, Release Branch 14.12, Trunk Attachments: gb_labels.patch Date formats displayed in the title of the input field are not correctly showing the default format for UK but the actual date itself is correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6276) Fix deprecation issues in framework/entity
[ https://issues.apache.org/jira/browse/OFBIZ-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-6276: -- Assignee: Jacques Le Roux Fix deprecation issues in framework/entity -- Key: OFBIZ-6276 URL: https://issues.apache.org/jira/browse/OFBIZ-6276 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Adam Heath Assignee: Jacques Le Roux Priority: Minor Attachments: OFBIZ-6276-variant-1.patch, OFBIZ-6276-variant-2.patch It appears that the storeAll() variants are being refactor; basically, the useCache parameter is being removed. However, this has caused the entity engine to have deprecation with itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6276) Fix deprecation issues in framework/entity
[ https://issues.apache.org/jira/browse/OFBIZ-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550313#comment-14550313 ] Jacques Le Roux commented on OFBIZ-6276: I mean while refactoring after a deprecation we already switched parameters in signature as a way to prevent collisions :) Fix deprecation issues in framework/entity -- Key: OFBIZ-6276 URL: https://issues.apache.org/jira/browse/OFBIZ-6276 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Adam Heath Priority: Minor Attachments: OFBIZ-6276-variant-1.patch, OFBIZ-6276-variant-2.patch It appears that the storeAll() variants are being refactor; basically, the useCache parameter is being removed. However, this has caused the entity engine to have deprecation with itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6218) Unit tests throw exception in DBCP
[ https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550410#comment-14550410 ] Michael Brohl commented on OFBIZ-6218: -- I have a problem with it locally, running the tests inside Eclipse: clean-all load-demo run-tests [java] 2015-05-19 15:00:50,463 |main |TestRunContainer |W| [JUNIT (error)] - testPerformFind : java.lang.NullPointerException [java] java.lang.NullPointerException [java] at org.apache.commons.dbcp2.DelegatingConnection.closeInternal(DelegatingConnection.java:235) ~[commons-dbcp2-2.1.jar:2.1] [java] at org.apache.commons.dbcp2.DelegatingConnection.close(DelegatingConnection.java:218) ~[commons-dbcp2-2.1.jar:2.1] [java] at org.apache.commons.dbcp2.managed.ManagedConnection.close(ManagedConnection.java:166) ~[commons-dbcp2-2.1.jar:2.1] [java] at org.ofbiz.entity.jdbc.SQLProcessor.close(SQLProcessor.java:235) ~[ofbiz-entity.jar:?] [java] at org.ofbiz.entity.util.EntityListIterator.close(EntityListIterator.java:154) ~[ofbiz-entity.jar:?] [java] at org.ofbiz.entity.util.EntityListIterator.next(EntityListIterator.java:329) ~[ofbiz-entity.jar:?] [java] at org.ofbiz.entity.util.EntityListIterator.getCompleteList(EntityListIterator.java:436) ~[ofbiz-entity.jar:?] [java] at org.ofbiz.common.test.PerformFindTests.getCompleteList(PerformFindTests.java:49) ~[ofbiz-common-test.jar:?] [java] at org.ofbiz.common.test.PerformFindTests.performFindConditionFieldEquals(PerformFindTests.java:136) ~[ofbiz-common-test.jar:?] [java] at org.ofbiz.common.test.PerformFindTests.testPerformFind(PerformFindTests.java:113) ~[ofbiz-common-test.jar:?] [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_71] [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[?:1.7.0_71] [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.7.0_71] [java] at java.lang.reflect.Method.invoke(Method.java:606) ~[?:1.7.0_71] [java] at junit.framework.TestCase.runTest(TestCase.java:168) ~[junit-dep-4.10.jar:?] [java] at junit.framework.TestCase.runBare(TestCase.java:134) ~[junit-dep-4.10.jar:?] [java] at junit.framework.TestResult$1.protect(TestResult.java:110) ~[junit-dep-4.10.jar:?] [java] at junit.framework.TestResult.runProtected(TestResult.java:128) [junit-dep-4.10.jar:?] [java] at junit.framework.TestResult.run(TestResult.java:113) [junit-dep-4.10.jar:?] [java] at junit.framework.TestCase.run(TestCase.java:124) [junit-dep-4.10.jar:?] [java] at junit.framework.TestSuite.runTest(TestSuite.java:243) [junit-dep-4.10.jar:?] [java] at junit.framework.TestSuite.run(TestSuite.java:238) [junit-dep-4.10.jar:?] [java] at junit.framework.TestSuite.runTest(TestSuite.java:243) [junit-dep-4.10.jar:?] [java] at junit.framework.TestSuite.run(TestSuite.java:238) [junit-dep-4.10.jar:?] [java] at org.ofbiz.testtools.TestRunContainer.start(TestRunContainer.java:146) [ofbiz-testtools.jar:?] [java] at org.ofbiz.base.container.ContainerLoader.start(ContainerLoader.java:237) [ofbiz-base.jar:?] [java] at org.ofbiz.base.start.Start.startStartLoaders(Start.java:408) [ofbiz.jar:?] [java] at org.ofbiz.base.start.Start.start(Start.java:434) [ofbiz.jar:?] [java] at org.ofbiz.base.start.Start.main(Start.java:135) [ofbiz.jar:?] [java] 2015-05-19 15:00:50,472 |main |TestRunContainer |I| [JUNIT] : testPerformFind finished. [java] 2015-05-19 15:00:50,472 |main |GenericDelegator |I| Rolling back 21 entity operations [java] 2015-05-19 15:00:50,481 |main |TestRunContainer |I| [JUNIT] Results for test suite: performfindtests [java] 2015-05-19 15:00:50,481 |main |TestRunContainer |I| [JUNIT] Pass: false | # Tests: 1 | # Failed: 0 # Errors: 1 [java] 2015-05-19 15:00:50,481 |main |TestRunContainer |I| [JUNIT] - ERRORS - [JUNIT] Unit tests throw exception in DBCP -- Key: OFBIZ-6218 URL: https://issues.apache.org/jira/browse/OFBIZ-6218 Project: OFBiz Issue Type: Bug Reporter: Adrian Crum Attachments: OFBIZ-6218.patch Details in comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: buildbot failure in ASF Buildbot on ofbiz-branch14
Hi Michael,
Forget it, it's not related with our code, not even a Buildbot issue, but an
infra issue.
I have already reported but had no feedback yet, I have reopened the issue
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-9662
For new committers: please remember that we no longer create INFRA- issues but need to pass through
https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 for them to organise their work
More generally it's at
https://issues.apache.org/jira/servicedesk/customer/portal/1
Jacques
PS: I still check locally there are no tests issues... OK :)
BUILD SUCCESSFUL
Total time: 6 minutes 48 seconds
Le 19/05/2015 13:15, Michael Brohl a écrit :
Hi everyone,
I investigated the build failure because I'm on the blamelist and found that the build breaks directly after checking out the fresh version on the
server, without even building the code:
program finished with exit code 0
elapsedTime=23.983329
svn info --xml
in dir /home/buildslave2/slave2/ofbiz-branch14/build (timeout 1200 secs)
watching logfiles {}
argv: ['svn', 'info', '--xml']
environment:
HOME=/home/buildslave2
LANG=en_AU.UTF-8
LESSCLOSE=/usr/bin/lesspipe %s %s
LESSOPEN=| /usr/bin/lesspipe %s
LOGNAME=buildslave2
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:
MAIL=/var/mail/buildslave2
OLDPWD=/home/gmcdonald
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/home/buildslave2/slave2/ofbiz-branch14/build
SHELL=/bin/bash
SHLVL=1
SUDO_COMMAND=/bin/bash
SUDO_GID=2393
SUDO_UID=2393
SUDO_USER=gmcdonald
TEMP=/tmp/user/10006
TEMPDIR=/tmp/user/10006
TERM=screen
TMP=/tmp/user/10006
TMPDIR=/tmp/user/10006
USER=buildslave2
USERNAME=buildslave2
_=/usr/bin/buildslave
using PTY: True
program finished with exit code 0
elapsedTime=0.016973
Corrupted xml, aborting step
I have checked the latest build failures and this seems to happen once in a
while. Does anyone have a clue how to solve this?
Regards,
Michael Brohl
ecomify GmbH
www.ecomify.de
Am 19.05.15 um 12:27 schrieb build...@apache.org:
The Buildbot has detected a new failure on builder ofbiz-branch14 while
building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/ofbiz-branch14/builds/125
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: lares_ubuntu
Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz14-commit'
triggered this build
Build Source Stamp: [branch ofbiz/branches/release14.12] 1680233
Blamelist: mbrohl
BUILD FAILED: failed
Sincerely,
-The Buildbot
[jira] [Assigned] (OFBIZ-6390) Change btn-sm to btn-xs for buttons regarding calendar and field lookup in Bootstrap-Basic
[ https://issues.apache.org/jira/browse/OFBIZ-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6390: --- Assignee: Pierre Smits Change btn-sm to btn-xs for buttons regarding calendar and field lookup in Bootstrap-Basic -- Key: OFBIZ-6390 URL: https://issues.apache.org/jira/browse/OFBIZ-6390 Project: OFBiz Issue Type: Improvement Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Attachments: OFBIZ-6390-Bootstrap-templates.patch Currently buttons associated with field lookup and from/through date exceed the height of the associated fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6389) Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml
Christian Carlow created OFBIZ-6389: --- Summary: Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml Key: OFBIZ-6389 URL: https://issues.apache.org/jira/browse/OFBIZ-6389 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Fix For: Trunk EmplPositionType CEO and CFO seem just as common as PROGRAMMER and SYS_ADMIN so it seems to make sense to add them. ResponsibilityType GENERAL_MGMT is the common responsibility of position CEO and should probably be included also since it is just as common as SALES_MGMT and FIN_MGMT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6389) Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml
[ https://issues.apache.org/jira/browse/OFBIZ-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550420#comment-14550420 ] Pierre Smits commented on OFBIZ-6389: - And don't forget all the other CxO roles, like: * Chief Information Officer - CIO * Chief Marketing Officer - CMO * Chief Compliance Officer - CCO * Chief Security Officer - CSO And the associated ResponsibilityType entities: * Information Management * Marketing Management * Compliance Management * Security Management And there could even be more. Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml --- Key: OFBIZ-6389 URL: https://issues.apache.org/jira/browse/OFBIZ-6389 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Fix For: Trunk Attachments: OFBIZ-6389.patch EmplPositionType CEO and CFO seem just as common as PROGRAMMER and SYS_ADMIN so it seems to make sense to add them. ResponsibilityType GENERAL_MGMT is the common responsibility of position CEO and should probably be included also since it is just as common as SALES_MGMT and FIN_MGMT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6391) EmplPositionType.description and ResponsibilityType.description lack translations
Christian Carlow created OFBIZ-6391: --- Summary: EmplPositionType.description and ResponsibilityType.description lack translations Key: OFBIZ-6391 URL: https://issues.apache.org/jira/browse/OFBIZ-6391 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: Trunk Reporter: Christian Carlow Lack of translation of those types was realized when patching OFBIZ-6389. Translations exists for other type data such as ProductAssocType and this patch should probably be based on that translation implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5840) Create bootstrap theme
[ https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550453#comment-14550453 ] Jacques Le Roux commented on OFBIZ-5840: Agreed and done! Create bootstrap theme -- Key: OFBIZ-5840 URL: https://issues.apache.org/jira/browse/OFBIZ-5840 Project: OFBiz Issue Type: New Feature Components: framework, themes Affects Versions: Bootstrap theme Reporter: Julien NICOLAS Labels: bootstrap, theme Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, bootstrap-theme.zip, bootstrap.zip, calendar.PNG, catalog.png, htmlMenuMacroLibrary.patch, pagination_htmlFormMacroLibrary.patch, panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, preferences.png, tab-bar.png, workeffort.PNG 1- create a sub-directory called bootstrap under the image webapp to put the resources over there (js, css and fonts) as indicated earlier by Gavin. (Julien : not sure about location) 2- check to make sure that the current version of jQuery is compatible with the installed version or upgrade it accordingly 3- Create a new theme based on one of the existing themes as suggested by Julien and Gavin 4- Test the theme by switching to it and handle major bugs / issues. 5- Start to make a few test screens utilizing Bootstrap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6218) Unit tests throw exception in DBCP
[ https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550459#comment-14550459 ] Nicolas Malin commented on OFBIZ-6218: -- I try directly on shell with *ant clean-all load-demo run-tests*, without error ... strange. Unit tests throw exception in DBCP -- Key: OFBIZ-6218 URL: https://issues.apache.org/jira/browse/OFBIZ-6218 Project: OFBiz Issue Type: Bug Reporter: Adrian Crum Attachments: OFBIZ-6218.patch Details in comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6390) Change btn-sm to btn-xs for buttons regarding calendar and field lookup in Bootstrap-Basic
[ https://issues.apache.org/jira/browse/OFBIZ-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6390: Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-5840 Change btn-sm to btn-xs for buttons regarding calendar and field lookup in Bootstrap-Basic -- Key: OFBIZ-6390 URL: https://issues.apache.org/jira/browse/OFBIZ-6390 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Attachments: OFBIZ-6390-Bootstrap-templates.patch Currently buttons associated with field lookup and from/through date exceed the height of the associated fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6218) Unit tests throw exception in DBCP
[ https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550459#comment-14550459 ] Nicolas Malin edited comment on OFBIZ-6218 at 5/19/15 1:47 PM: --- I just tried directly on shell with *ant clean-all load-demo run-tests*, without error ... strange. was (Author: soledad): I try directly on shell with *ant clean-all load-demo run-tests*, without error ... strange. Unit tests throw exception in DBCP -- Key: OFBIZ-6218 URL: https://issues.apache.org/jira/browse/OFBIZ-6218 Project: OFBiz Issue Type: Bug Reporter: Adrian Crum Attachments: OFBIZ-6218.patch Details in comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6218) Unit tests throw exception in DBCP
[ https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550457#comment-14550457 ] Michael Brohl commented on OFBIZ-6218: -- Yes, trunk HEAD but with the change for OFBIZ-6258 to test the patch. I will later test again on command line and Eclipse without any changes. Unit tests throw exception in DBCP -- Key: OFBIZ-6218 URL: https://issues.apache.org/jira/browse/OFBIZ-6218 Project: OFBiz Issue Type: Bug Reporter: Adrian Crum Attachments: OFBIZ-6218.patch Details in comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6276) Fix deprecation issues in framework/entity
[ https://issues.apache.org/jira/browse/OFBIZ-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550445#comment-14550445 ] Martin Becker commented on OFBIZ-6276: -- Mmmh, 1st way was my 1st idea, but I was not happy with introducing a new method name like storeAllWithDummyFks while the strategy is more like adding boolean parameters for such features (e.g. useCache parameter instead of methods like findByAnd and findByAndCache). This combined with the small relevance of the createDummyFks Feature (my opinion) led me to the simpler API without a different method name but switched parameter order for a method that may not be used very often. Fix deprecation issues in framework/entity -- Key: OFBIZ-6276 URL: https://issues.apache.org/jira/browse/OFBIZ-6276 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Adam Heath Assignee: Jacques Le Roux Priority: Minor Attachments: OFBIZ-6276-variant-1.patch, OFBIZ-6276-variant-2.patch It appears that the storeAll() variants are being refactor; basically, the useCache parameter is being removed. However, this has caused the entity engine to have deprecation with itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6218) Unit tests throw exception in DBCP
[ https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550449#comment-14550449 ] Jacques Le Roux commented on OFBIZ-6218: I guess you used trunk HEAD w/o any changes? Then we need to continue investigating why this is still happening from time to time :/ Unit tests throw exception in DBCP -- Key: OFBIZ-6218 URL: https://issues.apache.org/jira/browse/OFBIZ-6218 Project: OFBiz Issue Type: Bug Reporter: Adrian Crum Attachments: OFBIZ-6218.patch Details in comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6324) Have clickable 'Applications' present the drop-down menu of applications
[ https://issues.apache.org/jira/browse/OFBIZ-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6324: Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-5840 Have clickable 'Applications' present the drop-down menu of applications Key: OFBIZ-6324 URL: https://issues.apache.org/jira/browse/OFBIZ-6324 Project: OFBiz Issue Type: Sub-task Affects Versions: Bootstrap theme Reporter: Pierre Smits Currently, when using the boot-strap theme the user has to click on the + symbol beside the clickable 'Applications' to get the drop-down menu of available applications. And the 'Applications' clickable doesn't do anything. However, it would deliver a better user experience when the drop-down menu is presented when the user clicks the 'Applications' clickable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-6373: - Affects Version/s: Release Branch 14.12 CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6393) Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition
Christian Carlow created OFBIZ-6393: --- Summary: Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition Key: OFBIZ-6393 URL: https://issues.apache.org/jira/browse/OFBIZ-6393 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Other PartyQualTypes such as EXPERIENCE are not available for JobRequisition qualification field for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition because the entity-constraint parentId=DEGREE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6389) Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml
[ https://issues.apache.org/jira/browse/OFBIZ-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6389: Attachment: OFBIZ-6389.patch This patch adds EmplPositionType CEO and CFO and ReponsibilityType GENERAL_MGMT for CEO to applications/humanres/data/HumanResTypeData.xml. Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml --- Key: OFBIZ-6389 URL: https://issues.apache.org/jira/browse/OFBIZ-6389 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Fix For: Trunk Attachments: OFBIZ-6389.patch EmplPositionType CEO and CFO seem just as common as PROGRAMMER and SYS_ADMIN so it seems to make sense to add them. ResponsibilityType GENERAL_MGMT is the common responsibility of position CEO and should probably be included also since it is just as common as SALES_MGMT and FIN_MGMT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6392) Move various selection options in appbar.ftl under one button-group 'Preferences'
[ https://issues.apache.org/jira/browse/OFBIZ-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550474#comment-14550474 ] Pierre Smits commented on OFBIZ-6392: - See the 'BizznessTime' theme for comparison Move various selection options in appbar.ftl under one button-group 'Preferences' - Key: OFBIZ-6392 URL: https://issues.apache.org/jira/browse/OFBIZ-6392 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Having the options for: * Visual Theme selection * Language selection * password change * etc under 1 button group e.g. 'Preferences' produces a cleaner appbar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6393) Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition
[ https://issues.apache.org/jira/browse/OFBIZ-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6393: Attachment: OFBIZ-6393.patch This patch removes entity-constraint name=parentTypeId operator=equals value=DEGREE/ from qualification field dropdown entity-options at applications/humanres/widget/forms/RecruitmentForms.xml#EditJobRequisition to allow other types such as EXPERIENCE to be assigned as a job requisition qualification type. Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition -- Key: OFBIZ-6393 URL: https://issues.apache.org/jira/browse/OFBIZ-6393 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Attachments: OFBIZ-6393.patch Other PartyQualTypes such as EXPERIENCE are not available for JobRequisition qualification field for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition because the entity-constraint parentId=DEGREE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6276) Fix deprecation issues in framework/entity
[ https://issues.apache.org/jira/browse/OFBIZ-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550341#comment-14550341 ] Martin Becker commented on OFBIZ-6276: -- Aaah, check! Not really nice but effective ;-) Fix deprecation issues in framework/entity -- Key: OFBIZ-6276 URL: https://issues.apache.org/jira/browse/OFBIZ-6276 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Adam Heath Assignee: Jacques Le Roux Priority: Minor Attachments: OFBIZ-6276-variant-1.patch, OFBIZ-6276-variant-2.patch It appears that the storeAll() variants are being refactor; basically, the useCache parameter is being removed. However, this has caused the entity engine to have deprecation with itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6390) Change btn-sm to btn-xs for buttons regarding calendar and field lookup in Bootstrap-Basic
[ https://issues.apache.org/jira/browse/OFBIZ-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6390: Attachment: OFBIZ-6390-Bootstrap-templates.patch This patch addresses the issue. Also replaces tabs with spaces. Change btn-sm to btn-xs for buttons regarding calendar and field lookup in Bootstrap-Basic -- Key: OFBIZ-6390 URL: https://issues.apache.org/jira/browse/OFBIZ-6390 Project: OFBiz Issue Type: Improvement Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Attachments: OFBIZ-6390-Bootstrap-templates.patch Currently buttons associated with field lookup and from/through date exceed the height of the associated fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6326) Pagination doesn't render well in Bootstrap Basic
[ https://issues.apache.org/jira/browse/OFBIZ-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6326: Issue Type: Sub-task (was: Bug) Parent: OFBIZ-5840 Pagination doesn't render well in Bootstrap Basic - Key: OFBIZ-6326 URL: https://issues.apache.org/jira/browse/OFBIZ-6326 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Labels: pagination When accessing an overview page (e.g. /catalog/control/FindProduct) with more than the default number of records to be shown, the pagination comes out garbled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6392) Move various selection options in appbar.ftl under one button-group 'Preferences'
Pierre Smits created OFBIZ-6392: --- Summary: Move various selection options in appbar.ftl under one button-group 'Preferences' Key: OFBIZ-6392 URL: https://issues.apache.org/jira/browse/OFBIZ-6392 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Having the options for: * Visual Theme selection * Language selection * password change * etc under 1 button group e.g. 'Preferences' produces a cleaner appbar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6276) Fix deprecation issues in framework/entity
[ https://issues.apache.org/jira/browse/OFBIZ-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550405#comment-14550405 ] Jacques Le Roux commented on OFBIZ-6276: Yes after reviewing both I'm still undecided. I think indeed the 1st way is cleaner. I will finally wait some other opinions before committing... Fix deprecation issues in framework/entity -- Key: OFBIZ-6276 URL: https://issues.apache.org/jira/browse/OFBIZ-6276 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Adam Heath Assignee: Jacques Le Roux Priority: Minor Attachments: OFBIZ-6276-variant-1.patch, OFBIZ-6276-variant-2.patch It appears that the storeAll() variants are being refactor; basically, the useCache parameter is being removed. However, this has caused the entity engine to have deprecation with itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6390) Change btn-sm to btn-xs for buttons regarding calendar and field lookup in Bootstrap-Basic
Pierre Smits created OFBIZ-6390: --- Summary: Change btn-sm to btn-xs for buttons regarding calendar and field lookup in Bootstrap-Basic Key: OFBIZ-6390 URL: https://issues.apache.org/jira/browse/OFBIZ-6390 Project: OFBiz Issue Type: Improvement Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Currently buttons associated with field lookup and from/through date exceed the height of the associated fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6258) Trivial perfomance improvement for creating OrderItemAttributes during store/update Order
[
https://issues.apache.org/jira/browse/OFBIZ-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brohl closed OFBIZ-6258.
fixed in
trunk r1680288
R14.12 r1680293
Thanks Martin for reporting and providing the patch.
Trivial perfomance improvement for creating OrderItemAttributes during
store/update Order
-
Key: OFBIZ-6258
URL: https://issues.apache.org/jira/browse/OFBIZ-6258
Project: OFBiz
Issue Type: Improvement
Components: order
Affects Versions: Upcoming Branch
Reporter: Martin Becker
Assignee: Michael Brohl
Priority: Trivial
Attachments: ShoppingCart-makeAllOrderItemAttributes.patch
Improved use of given mode parameter in {{makeAllOrderItemAttributes(String
orderId, int mode)}} to avoid creating new OrderItemAttribute GenericValues
that have not to be created according to the value for mode (FILLED_ONLY,
EMPTY_ONLY).
Change was made for a project with massive use of OrderItemAttributes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-6389) Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml
[ https://issues.apache.org/jira/browse/OFBIZ-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6389: Attachment: OFBIZ-6389_2.patch As suggested by Pierre, EmplPositionType CIO, CMO, CCO, CSO and ResponsibilityType INFO_MGMT, MKTG_MGMT, COMPLI_MGMT, SECUR_MGMT were added to applications/humanres/data/HumanREsTypeData.xml after the first patch was applied. Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml --- Key: OFBIZ-6389 URL: https://issues.apache.org/jira/browse/OFBIZ-6389 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Fix For: Trunk Attachments: OFBIZ-6389.patch, OFBIZ-6389_2.patch EmplPositionType CEO and CFO seem just as common as PROGRAMMER and SYS_ADMIN so it seems to make sense to add them. ResponsibilityType GENERAL_MGMT is the common responsibility of position CEO and should probably be included also since it is just as common as SALES_MGMT and FIN_MGMT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6393) Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition
[ https://issues.apache.org/jira/browse/OFBIZ-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6393: Component/s: (was: manufacturing) humanres Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition -- Key: OFBIZ-6393 URL: https://issues.apache.org/jira/browse/OFBIZ-6393 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Attachments: OFBIZ-6393.patch Other PartyQualTypes such as EXPERIENCE are not available for JobRequisition qualification field for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition because the entity-constraint parentId=DEGREE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6393) Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition
[ https://issues.apache.org/jira/browse/OFBIZ-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow reassigned OFBIZ-6393: --- Assignee: Christian Carlow Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition -- Key: OFBIZ-6393 URL: https://issues.apache.org/jira/browse/OFBIZ-6393 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Priority: Minor Attachments: OFBIZ-6393.patch Other PartyQualTypes such as EXPERIENCE are not available for JobRequisition qualification field for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition because the entity-constraint parentId=DEGREE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6393) Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition
[ https://issues.apache.org/jira/browse/OFBIZ-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550581#comment-14550581 ] Christian Carlow commented on OFBIZ-6393: - Whoops, you are right Pierre, it is related to humanres. Thanks for catching. Updating and closing issue as resolved. Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition -- Key: OFBIZ-6393 URL: https://issues.apache.org/jira/browse/OFBIZ-6393 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Priority: Minor Attachments: OFBIZ-6393.patch Other PartyQualTypes such as EXPERIENCE are not available for JobRequisition qualification field for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition because the entity-constraint parentId=DEGREE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6393) Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition
[ https://issues.apache.org/jira/browse/OFBIZ-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550609#comment-14550609 ] Christian Carlow commented on OFBIZ-6393: - Fixed in: trunk r1680300 Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition -- Key: OFBIZ-6393 URL: https://issues.apache.org/jira/browse/OFBIZ-6393 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Priority: Minor Attachments: OFBIZ-6393.patch Other PartyQualTypes such as EXPERIENCE are not available for JobRequisition qualification field for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition because the entity-constraint parentId=DEGREE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6389) Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml
[ https://issues.apache.org/jira/browse/OFBIZ-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550613#comment-14550613 ] Christian Carlow commented on OFBIZ-6389: - Fixed in: trunk r1680281 for first patch trunk r1680290 for second patch Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml --- Key: OFBIZ-6389 URL: https://issues.apache.org/jira/browse/OFBIZ-6389 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Fix For: Trunk Attachments: OFBIZ-6389.patch, OFBIZ-6389_2.patch EmplPositionType CEO and CFO seem just as common as PROGRAMMER and SYS_ADMIN so it seems to make sense to add them. ResponsibilityType GENERAL_MGMT is the common responsibility of position CEO and should probably be included also since it is just as common as SALES_MGMT and FIN_MGMT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6387) Duplicate referredByPartyId field for EmployementAppForms.xml#ListEmployementApps at humanres/control/FindEmploymentApps
[ https://issues.apache.org/jira/browse/OFBIZ-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow reassigned OFBIZ-6387: --- Assignee: Christian Carlow Duplicate referredByPartyId field for EmployementAppForms.xml#ListEmployementApps at humanres/control/FindEmploymentApps Key: OFBIZ-6387 URL: https://issues.apache.org/jira/browse/OFBIZ-6387 Project: OFBiz Issue Type: Bug Components: humanres Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Attachments: OFBIZ-6387.patch The use-case attributes being evaluated incorrectly causes the widget delete button to bleed past its title. referredByPartyId should be replaced with 1 field definition without a use-when attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6324) Have clickable 'Applications' present the drop-down menu of applications
[ https://issues.apache.org/jira/browse/OFBIZ-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550582#comment-14550582 ] Pierre Smits commented on OFBIZ-6324: - See how it could look like in OFBIZ-6392 Have clickable 'Applications' present the drop-down menu of applications Key: OFBIZ-6324 URL: https://issues.apache.org/jira/browse/OFBIZ-6324 Project: OFBiz Issue Type: Sub-task Affects Versions: Bootstrap theme Reporter: Pierre Smits Currently, when using the boot-strap theme the user has to click on the + symbol beside the clickable 'Applications' to get the drop-down menu of available applications. And the 'Applications' clickable doesn't do anything. However, it would deliver a better user experience when the drop-down menu is presented when the user clicks the 'Applications' clickable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6389) Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml
[ https://issues.apache.org/jira/browse/OFBIZ-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow reassigned OFBIZ-6389: --- Assignee: Christian Carlow Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml --- Key: OFBIZ-6389 URL: https://issues.apache.org/jira/browse/OFBIZ-6389 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Fix For: Trunk Attachments: OFBIZ-6389.patch, OFBIZ-6389_2.patch EmplPositionType CEO and CFO seem just as common as PROGRAMMER and SYS_ADMIN so it seems to make sense to add them. ResponsibilityType GENERAL_MGMT is the common responsibility of position CEO and should probably be included also since it is just as common as SALES_MGMT and FIN_MGMT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6392) Move various selection options in appbar.ftl under one button-group 'Preferences'
[ https://issues.apache.org/jira/browse/OFBIZ-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6392: Attachment: Screen Shot 2015-05-19 at 16.58.41.png This screenshot shows how it could look like. Move various selection options in appbar.ftl under one button-group 'Preferences' - Key: OFBIZ-6392 URL: https://issues.apache.org/jira/browse/OFBIZ-6392 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Attachments: Screen Shot 2015-05-19 at 16.58.41.png Having the options for: * Visual Theme selection * Language selection * password change * etc under 1 button group e.g. 'Preferences' produces a cleaner appbar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6387) Duplicate referredByPartyId field for EmployementAppForms.xml#ListEmployementApps at humanres/control/FindEmploymentApps
[ https://issues.apache.org/jira/browse/OFBIZ-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550616#comment-14550616 ] Christian Carlow commented on OFBIZ-6387: - Fixed in: trunk r1680155 Duplicate referredByPartyId field for EmployementAppForms.xml#ListEmployementApps at humanres/control/FindEmploymentApps Key: OFBIZ-6387 URL: https://issues.apache.org/jira/browse/OFBIZ-6387 Project: OFBiz Issue Type: Bug Components: humanres Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Attachments: OFBIZ-6387.patch The use-case attributes being evaluated incorrectly causes the widget delete button to bleed past its title. referredByPartyId should be replaced with 1 field definition without a use-when attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Apache Cloudstack moved to git for code and docs
This is a news summary from the Apache Cloudstack project that I thought might be interesting for a number of points. They seem happy with their move to git. They are also using sub-projects. Docs also on git with a build system to generate the web site. They actually have a public list of what the PMC thinks are worthwhile goals https://cwiki.apache.org/confluence/display/CLOUDSTACK/2015+Plan and a call to the community to JFDI if you see something that gets your attention and you think that you can. Ron Forwarded Message Hi folks, Couple months ago I shared a few thoughts for 2015 [1], things that we could do to make our project even greater. There has been good progress, so I would like to share a few updates. 1- Review board. We are no longer using review board, all code contributions should now come as github pull requests. This is proving to be very successful. We have closed 248 pull requests and have 12 currently open. This does not count the commits that come in directly into the source. Let's keep it coming. 2- AWSAPI We removed the AWSAPI code that was in our source. It consisted of a lot of auto-generated code and increased our number of lines of code quite a bit. This is going to make our build and our packaging easier. 3- ec2stack and gcestack Those two packages are now official CloudStack subproject. They are hosted on Apache git infrastructure and mirrored on github [2][3]. We are accepting pull requests the same way than our standard source. These are python packages, and represent a good entry point for Python programmers. Next is to actually do an official release of these two API interfaces. 4-Ansible The ansible cloudstack module from Rene Moser is being merged in as a core Ansible module. Expect it in Ansible 2.0 5-New docs theme Our documentation has a new documentation theme [4] thanks to Pierre-Luc Dion. There is still a lot to do here, see [1] for low hanging fruits in this area. 6-CloudStack days Our CloudStack days kicked off in Austin. The Tokyo day will be on June 2nd [5] and the schedule should be up shortly. The call for papers are open for Seattle [6] on August 20th and Dublin on October 8-9 [7] We also have a London meet up this week [11] and in June we will have one in Amsterdam. The Dublin event will be a two day event with an off-site hackathon. Submit your talks early so we can plan a great program. Sponsor so we can have a great conference. Register so we can all meet face to face. 7-Website The website has been moved to git, instead of the old svn based apache content management system. It is mirrored on github [8] and we can accept pull requests for modification. The website now uses middleman for build system. There is also tons to do there, we should come up with a new slick modern design. In terms of code, 4.5.1 has been released [10] which contains some great plugins like Nuage SDN, SAML 2.0 and Globo DNS. With Apache getting more resources from TravisCI, we are now able to run more integration tests for every commit and we are going to try a new release process for 4.6. We all continue to strive to make CloudStack even more rock solid than it is now, and making it a snap to release our code. So do chime in on the d...@cloudstack.apache.org if you want to help with hardening and extending CloudStack. If you are not a developer, do have a look at [1], a lot of those items fall in the JFDI [9] category. Finishing up some of those will greatly help the +2000 people on these lists. Personally I see all this as great progress and focus, let's keep it up. Cheers, [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/2015+Plan [2] https://github.com/apache/cloudstack-ec2stack [3] https://github.com/apache/cloudstack-gcestack [4] http://docs.cloudstack.apache.org [5] http://events.linuxfoundation.org/events/cloudstack-tokyo [6] http://events.linuxfoundation.org/events/cloudstack-seattle/program/cfp [7] http://events.linuxfoundation.org/events/cloudstack-collaboration-conference-europe [8] https://github.com/apache/cloudstack-www [9] http://www.urbandictionary.com/define.php?term=JFDI [10] http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.5.1/ [11] http://www.eventbrite.co.uk/e/cloudstack-european-user-group-tickets-16282793273?aff=erelexporg -Sebastien Goasguen VP Apache CloudStack
[jira] [Commented] (OFBIZ-6393) Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition
[ https://issues.apache.org/jira/browse/OFBIZ-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550517#comment-14550517 ] Pierre Smits commented on OFBIZ-6393: - It seems to me that this is more related to the HumanRes component than to the Manufacturing component. Support all JobRequisition.qualification PartyQualTypes for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition -- Key: OFBIZ-6393 URL: https://issues.apache.org/jira/browse/OFBIZ-6393 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Attachments: OFBIZ-6393.patch Other PartyQualTypes such as EXPERIENCE are not available for JobRequisition qualification field for RecruitmentForms.xml#EditJobRequisition at humanres/control/EditJobRequisition because the entity-constraint parentId=DEGREE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Bootstrap dev branch
There is no need to keep the bootstrap branch in sync with the trunk. The branch is intended to be a sandbox for visual theme development. Visual themes are not influenced by most of the work going on in the trunk. Once the related Jira issue is completed, then we can merge the branch to the trunk. The last time I checked, there were still a lot of problems with the boostrap theme, so it is not ready for merging. Adrian Crum Sandglass Software www.sandglass-software.com On 5/19/2015 12:51 AM, Pierre Smits wrote: There are significant changes in the bootstrap dev branch regarding widgets, that aren't reflected in trunk. I tried the bootstrap theme in my dev for trunk and it gave errors. It seems to me that best would be to bring bootstrap dev in sync with branch, fix the issues registered and then, when there is consensus, port back to trunk. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, May 19, 2015 at 9:30 AM, Julien NICOLAS julien.nico...@nomaka.fr wrote: What could be the best way to keep this work alive ? I propose to make diff between bootstrap branch and trunk and make a patch with bootstrap theme and GUI modifications. It's a manual merge but it could work ;) What do you think ? Julien. Le 18/05/2015 13:05, Jacques Le Roux a écrit : I tried but got this Command: Auto-merge https://svn.apache.org/repos/asf/ofbiz/trunk into C:\projectsASF\boostrap_theme Error: Reintegrate can only be used if revisions 1634810 through 1679986 were Error: previously merged from Error: https://svn.apache.org/repos/asf/ofbiz/branches/boostrap_theme to the Error: reintegrate source, but this is not the case: Error: ofbiz/trunk Error: Missing ranges: /ofbiz/branches/boostrap_theme:1634810,1635414,1635439 Gave up Jacques Le 18/05/2015 12:39, Pierre Smits a écrit : Hi all, Can we have an update on the bootstrap dev branch so that it has the latest from trunk? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
[jira] [Assigned] (OFBIZ-6368) Empty availabilityStatusId widget dropdown for statusTypeId WEFA_AVAILABILITY of ProductionRunTaskFixedAssets and AddProductionRunTaskFixedAsset
[ https://issues.apache.org/jira/browse/OFBIZ-6368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow reassigned OFBIZ-6368: --- Assignee: Christian Carlow Empty availabilityStatusId widget dropdown for statusTypeId WEFA_AVAILABILITY of ProductionRunTaskFixedAssets and AddProductionRunTaskFixedAsset Key: OFBIZ-6368 URL: https://issues.apache.org/jira/browse/OFBIZ-6368 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Attachments: OFBIZ-6368.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5840) Create bootstrap theme
[ https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum updated OFBIZ-5840: --- Attachment: styling_issue_4.png styling_issue_3.png styling_issue_3.png and styling_issue_4.png show styling flaws in list pagination. Create bootstrap theme -- Key: OFBIZ-5840 URL: https://issues.apache.org/jira/browse/OFBIZ-5840 Project: OFBiz Issue Type: New Feature Components: framework, themes Affects Versions: Bootstrap theme Reporter: Julien NICOLAS Labels: bootstrap, theme Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, bootstrap-theme.zip, bootstrap.zip, calendar.PNG, catalog.png, htmlMenuMacroLibrary.patch, pagination_htmlFormMacroLibrary.patch, panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, preferences.png, styling_issue_1.png, styling_issue_2.png, styling_issue_3.png, styling_issue_4.png, tab-bar.png, workeffort.PNG 1- create a sub-directory called bootstrap under the image webapp to put the resources over there (js, css and fonts) as indicated earlier by Gavin. (Julien : not sure about location) 2- check to make sure that the current version of jQuery is compatible with the installed version or upgrade it accordingly 3- Create a new theme based on one of the existing themes as suggested by Julien and Gavin 4- Test the theme by switching to it and handle major bugs / issues. 5- Start to make a few test screens utilizing Bootstrap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5840) Create bootstrap theme
[ https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum updated OFBIZ-5840: --- Attachment: styling_issue_6.png styling_issue_5.png styling_issue_5.png and styling_issue_6.png show a flaw in how sub-menus are handled. The menu items under Facility should not appear unless a Facility has been selected. If I click on the Children menu item, I get the error message in styling_issue_6.png. Create bootstrap theme -- Key: OFBIZ-5840 URL: https://issues.apache.org/jira/browse/OFBIZ-5840 Project: OFBiz Issue Type: New Feature Components: framework, themes Affects Versions: Bootstrap theme Reporter: Julien NICOLAS Labels: bootstrap, theme Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, bootstrap-theme.zip, bootstrap.zip, calendar.PNG, catalog.png, htmlMenuMacroLibrary.patch, pagination_htmlFormMacroLibrary.patch, panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, preferences.png, styling_issue_1.png, styling_issue_2.png, styling_issue_3.png, styling_issue_4.png, styling_issue_5.png, styling_issue_6.png, tab-bar.png, workeffort.PNG 1- create a sub-directory called bootstrap under the image webapp to put the resources over there (js, css and fonts) as indicated earlier by Gavin. (Julien : not sure about location) 2- check to make sure that the current version of jQuery is compatible with the installed version or upgrade it accordingly 3- Create a new theme based on one of the existing themes as suggested by Julien and Gavin 4- Test the theme by switching to it and handle major bugs / issues. 5- Start to make a few test screens utilizing Bootstrap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-5840) Create bootstrap theme
[ https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550786#comment-14550786 ] Adrian Crum edited comment on OFBIZ-5840 at 5/19/15 5:12 PM: - styling_issue_7.png shows flaws in how sub-menus are handled. Clicking on the Facility menu item should bring up a Find Facility screen, but instead it brings up a Create New Facility screen. The Create New Facility screen layout is broken. was (Author: adri...@hlmksw.com): styling_issue_7.png shows flaws in how sub-menus are handled. Clicking on the Facility menu item should bring up a Find Facility screen, but instead it brings up a Create New Facility screen. The Create New Faility screen layout is broken. Create bootstrap theme -- Key: OFBIZ-5840 URL: https://issues.apache.org/jira/browse/OFBIZ-5840 Project: OFBiz Issue Type: New Feature Components: framework, themes Affects Versions: Bootstrap theme Reporter: Julien NICOLAS Labels: bootstrap, theme Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, bootstrap-theme.zip, bootstrap.zip, calendar.PNG, catalog.png, htmlMenuMacroLibrary.patch, pagination_htmlFormMacroLibrary.patch, panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, preferences.png, styling_issue_1.png, styling_issue_2.png, styling_issue_3.png, styling_issue_4.png, styling_issue_5.png, styling_issue_6.png, styling_issue_7.png, tab-bar.png, workeffort.PNG 1- create a sub-directory called bootstrap under the image webapp to put the resources over there (js, css and fonts) as indicated earlier by Gavin. (Julien : not sure about location) 2- check to make sure that the current version of jQuery is compatible with the installed version or upgrade it accordingly 3- Create a new theme based on one of the existing themes as suggested by Julien and Gavin 4- Test the theme by switching to it and handle major bugs / issues. 5- Start to make a few test screens utilizing Bootstrap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5840) Create bootstrap theme
[ https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum updated OFBIZ-5840: --- Attachment: styling_issue_7.png styling_issue_7.png shows flaws in how sub-menus are handled. Clicking on the Facility menu item should bring up a Find Facility screen, but instead it brings up a Create New Facility screen. The Create New Faility screen layout is broken. Create bootstrap theme -- Key: OFBIZ-5840 URL: https://issues.apache.org/jira/browse/OFBIZ-5840 Project: OFBiz Issue Type: New Feature Components: framework, themes Affects Versions: Bootstrap theme Reporter: Julien NICOLAS Labels: bootstrap, theme Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, bootstrap-theme.zip, bootstrap.zip, calendar.PNG, catalog.png, htmlMenuMacroLibrary.patch, pagination_htmlFormMacroLibrary.patch, panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, preferences.png, styling_issue_1.png, styling_issue_2.png, styling_issue_3.png, styling_issue_4.png, styling_issue_5.png, styling_issue_6.png, styling_issue_7.png, tab-bar.png, workeffort.PNG 1- create a sub-directory called bootstrap under the image webapp to put the resources over there (js, css and fonts) as indicated earlier by Gavin. (Julien : not sure about location) 2- check to make sure that the current version of jQuery is compatible with the installed version or upgrade it accordingly 3- Create a new theme based on one of the existing themes as suggested by Julien and Gavin 4- Test the theme by switching to it and handle major bugs / issues. 5- Start to make a few test screens utilizing Bootstrap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5840) Create bootstrap theme
[ https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550392#comment-14550392 ] Pierre Smits commented on OFBIZ-5840: - I believe we should convert this to a normal issue and set the relation with OFBIZ-5040. That way we preserve the association, and we can use this as a placeholder for sub tasks. What do you think? Create bootstrap theme -- Key: OFBIZ-5840 URL: https://issues.apache.org/jira/browse/OFBIZ-5840 Project: OFBiz Issue Type: Sub-task Components: framework, themes Affects Versions: Bootstrap theme Reporter: Julien NICOLAS Labels: bootstrap, theme Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, bootstrap-theme.zip, bootstrap.zip, calendar.PNG, catalog.png, htmlMenuMacroLibrary.patch, pagination_htmlFormMacroLibrary.patch, panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, preferences.png, tab-bar.png, workeffort.PNG 1- create a sub-directory called bootstrap under the image webapp to put the resources over there (js, css and fonts) as indicated earlier by Gavin. (Julien : not sure about location) 2- check to make sure that the current version of jQuery is compatible with the installed version or upgrade it accordingly 3- Create a new theme based on one of the existing themes as suggested by Julien and Gavin 4- Test the theme by switching to it and handle major bugs / issues. 5- Start to make a few test screens utilizing Bootstrap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6388) Licence header is missing in Seo*.xml files
[ https://issues.apache.org/jira/browse/OFBIZ-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6388. -- Resolution: Fixed Fix Version/s: Upcoming Branch Assignee: Jacques Le Roux (was: Pierre Smits) Thanks Pierre, Your patch is in trunk r1680283 I let it as is but it was not quite a bug, rather a not done task Licence header is missing in Seo*.xml files --- Key: OFBIZ-6388 URL: https://issues.apache.org/jira/browse/OFBIZ-6388 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Trunk Reporter: Pierre Smits Assignee: Jacques Le Roux Fix For: Upcoming Branch Attachments: OFBIZ-6388-product-SEO.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5840) Create bootstrap theme
[ https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-5840: --- Issue Type: New Feature (was: Sub-task) Parent: (was: OFBIZ-5040) Create bootstrap theme -- Key: OFBIZ-5840 URL: https://issues.apache.org/jira/browse/OFBIZ-5840 Project: OFBiz Issue Type: New Feature Components: framework, themes Affects Versions: Bootstrap theme Reporter: Julien NICOLAS Labels: bootstrap, theme Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, bootstrap-theme.zip, bootstrap.zip, calendar.PNG, catalog.png, htmlMenuMacroLibrary.patch, pagination_htmlFormMacroLibrary.patch, panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, preferences.png, tab-bar.png, workeffort.PNG 1- create a sub-directory called bootstrap under the image webapp to put the resources over there (js, css and fonts) as indicated earlier by Gavin. (Julien : not sure about location) 2- check to make sure that the current version of jQuery is compatible with the installed version or upgrade it accordingly 3- Create a new theme based on one of the existing themes as suggested by Julien and Gavin 4- Test the theme by switching to it and handle major bugs / issues. 5- Start to make a few test screens utilizing Bootstrap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: buildbot failure in ASF Buildbot on ofbiz-branch14
Hi Jaques, thanks for the information! Pheww, not nice to break the build with the first commit, but so I learned to investigate what's going on there :-) Michael Brohl ecomify GmbH www.ecomify.de Am 19.05.15 um 15:33 schrieb Jacques Le Roux: Hi Michael, Forget it, it's not related with our code, not even a Buildbot issue, but an infra issue. I have already reported but had no feedback yet, I have reopened the issue https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-9662 For new committers: please remember that we no longer create INFRA- issues but need to pass through https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 for them to organise their work More generally it's at https://issues.apache.org/jira/servicedesk/customer/portal/1 Jacques PS: I still check locally there are no tests issues... OK :) BUILD SUCCESSFUL Total time: 6 minutes 48 seconds smime.p7s Description: S/MIME Cryptographic Signature
buildbot success in ASF Buildbot on ofbiz-branch14
The Buildbot has detected a restored build on builder ofbiz-branch14 while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-branch14/builds/126 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz14-commit' triggered this build Build Source Stamp: [branch ofbiz/branches/release14.12] 1680293 Blamelist: mbrohl Build succeeded! Sincerely, -The Buildbot
[jira] [Commented] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550837#comment-14550837 ] Jacques Le Roux commented on OFBIZ-6373: Michael, I just changed it for you: you fix only unreleased versions, so it's not trunk to put in Fix Version/s field but Upcoming Branch. We use that to automatically generates releases changelogs from Jira ;) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5840) Create bootstrap theme
[ https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum updated OFBIZ-5840: --- Attachment: styling_issue_8.png styling_issue_8.png shows some styling flaws in the lookup screen. The dialog window style does not match the rest of the screen, and the Close button seems to be missing an icon. Create bootstrap theme -- Key: OFBIZ-5840 URL: https://issues.apache.org/jira/browse/OFBIZ-5840 Project: OFBiz Issue Type: New Feature Components: framework, themes Affects Versions: Bootstrap theme Reporter: Julien NICOLAS Labels: bootstrap, theme Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, bootstrap-theme.zip, bootstrap.zip, calendar.PNG, catalog.png, htmlMenuMacroLibrary.patch, pagination_htmlFormMacroLibrary.patch, panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, preferences.png, styling_issue_1.png, styling_issue_2.png, styling_issue_3.png, styling_issue_4.png, styling_issue_5.png, styling_issue_6.png, styling_issue_7.png, styling_issue_8.png, tab-bar.png, workeffort.PNG 1- create a sub-directory called bootstrap under the image webapp to put the resources over there (js, css and fonts) as indicated earlier by Gavin. (Julien : not sure about location) 2- check to make sure that the current version of jQuery is compatible with the installed version or upgrade it accordingly 3- Create a new theme based on one of the existing themes as suggested by Julien and Gavin 4- Test the theme by switching to it and handle major bugs / issues. 5- Start to make a few test screens utilizing Bootstrap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6394) Have login screen rendered in bootstrap-basic theme
[ https://issues.apache.org/jira/browse/OFBIZ-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum closed OFBIZ-6394. -- Resolution: Invalid Have login screen rendered in bootstrap-basic theme --- Key: OFBIZ-6394 URL: https://issues.apache.org/jira/browse/OFBIZ-6394 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits When logging out - or accessing OFBiz in a new session - while using the Bootstrap-Basic theme, the theme used is that of Tomahawk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6394) Have login screen rendered in bootstrap-basic theme
[ https://issues.apache.org/jira/browse/OFBIZ-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550824#comment-14550824 ] Adrian Crum commented on OFBIZ-6394: This normal behavior in all themes. When a user is logged out, OFBiz reverts to the configured default visual theme. Have login screen rendered in bootstrap-basic theme --- Key: OFBIZ-6394 URL: https://issues.apache.org/jira/browse/OFBIZ-6394 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits When logging out - or accessing OFBiz in a new session - while using the Bootstrap-Basic theme, the theme used is that of Tomahawk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6394) Have login screen rendered in bootstrap-basic theme
[ https://issues.apache.org/jira/browse/OFBIZ-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550824#comment-14550824 ] Adrian Crum edited comment on OFBIZ-6394 at 5/19/15 5:28 PM: - This is normal behavior in all themes. When a user is logged out, OFBiz reverts to the configured default visual theme. was (Author: adri...@hlmksw.com): This normal behavior in all themes. When a user is logged out, OFBiz reverts to the configured default visual theme. Have login screen rendered in bootstrap-basic theme --- Key: OFBIZ-6394 URL: https://issues.apache.org/jira/browse/OFBIZ-6394 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits When logging out - or accessing OFBiz in a new session - while using the Bootstrap-Basic theme, the theme used is that of Tomahawk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6373: --- Fix Version/s: (was: Trunk) Upcoming Branch CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6389) Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml
[ https://issues.apache.org/jira/browse/OFBIZ-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6389: --- Fix Version/s: (was: Trunk) Upcoming Branch Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml --- Key: OFBIZ-6389 URL: https://issues.apache.org/jira/browse/OFBIZ-6389 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Fix For: Upcoming Branch Attachments: OFBIZ-6389.patch, OFBIZ-6389_2.patch EmplPositionType CEO and CFO seem just as common as PROGRAMMER and SYS_ADMIN so it seems to make sense to add them. ResponsibilityType GENERAL_MGMT is the common responsibility of position CEO and should probably be included also since it is just as common as SALES_MGMT and FIN_MGMT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6389) Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml
[ https://issues.apache.org/jira/browse/OFBIZ-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550841#comment-14550841 ] Jacques Le Roux commented on OFBIZ-6389: Christian, I just changed it for you: you fix only unreleased versions, so it's not trunk to put in Fix Version/s field but Upcoming Branch. We use that to automatically generate releases changelogs from Jira Add EmplPositionType for CEO and CFO in applications/humanres/data/HumanResTypeData.xml --- Key: OFBIZ-6389 URL: https://issues.apache.org/jira/browse/OFBIZ-6389 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Assignee: Christian Carlow Fix For: Upcoming Branch Attachments: OFBIZ-6389.patch, OFBIZ-6389_2.patch EmplPositionType CEO and CFO seem just as common as PROGRAMMER and SYS_ADMIN so it seems to make sense to add them. ResponsibilityType GENERAL_MGMT is the common responsibility of position CEO and should probably be included also since it is just as common as SALES_MGMT and FIN_MGMT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550837#comment-14550837 ] Jacques Le Roux edited comment on OFBIZ-6373 at 5/19/15 5:36 PM: - Michael, I just changed it for you: you fix only unreleased versions, so it's not trunk to put in Fix Version/s field but Upcoming Branch. We use that to automatically generate releases changelogs from Jira ;) was (Author: jacques.le.roux): Michael, I just changed it for you: you fix only unreleased versions, so it's not trunk to put in Fix Version/s field but Upcoming Branch. We use that to automatically generates releases changelogs from Jira ;) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551216#comment-14551216 ] Jacques Le Roux commented on OFBIZ-6373: Never, always Upcoming Branch :) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551196#comment-14551196 ] Michael Brohl commented on OFBIZ-6373: -- Thank you, Jacques! In which case should I select trunk in fix versions, if any? CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551282#comment-14551282 ] Michael Brohl commented on OFBIZ-6373: -- Ok! That's easy ;-) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551280#comment-14551280 ] Michael Brohl commented on OFBIZ-6373: -- Ok! That's easy ;-) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-6373: - Comment: was deleted (was: Ok! That's easy ;-)) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-6373: - Comment: was deleted (was: Ok! That's easy ;-)) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551281#comment-14551281 ] Michael Brohl commented on OFBIZ-6373: -- Ok! That's easy ;-) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Upcoming Branch Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6373) CategoryWorker.getRelatedCategoriesRet ignores recursive-flag
[ https://issues.apache.org/jira/browse/OFBIZ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-6373. fixed in trunk r1680304 R13.07 r1680324 R14.12 r1680305 Thanks Sebastian for reporting and providing the patch. CategoryWorker.getRelatedCategoriesRet ignores recursive-flag - Key: OFBIZ-6373 URL: https://issues.apache.org/jira/browse/OFBIZ-6373 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Release Branch 14.12, Trunk, 13.07.01 Reporter: Sebastian Leitner Assignee: Michael Brohl Priority: Minor Fix For: Release Branch 13.07, Release Branch 14.12, Trunk Attachments: CategoryWorker.patch Some of the CategoryWorker.getRelatedCategoriesRet methods have a flag in their signature (boolean) to switch on/off recursiveness. But they ignore this flag and pass 'false' to further processing. Will attach a patch in a second. Might also affect 14.x releases as it's in trunk and 13.07.01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
