[jira] [Commented] (OFBIZ-7723) Use Pandoc to integrate our README.MD from repo to Confluence
[ https://issues.apache.org/jira/browse/OFBIZ-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429230#comment-15429230 ] Jacques Le Roux commented on OFBIZ-7723: So we will use http://pandoc.org/ to create HTML files from our README.MD files in the OFBiz trunk and the installed HTML connector plugin for the rendering in Confluence > Use Pandoc to integrate our README.MD from repo to Confluence > - > > Key: OFBIZ-7723 > URL: https://issues.apache.org/jira/browse/OFBIZ-7723 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > Labels: documentation, gradle, wiki > Fix For: Upcoming Branch > > > See INFRA-12200 for details, this is about moving/updating Gradle > documentation into the wiki -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7962) Migrate the patch management Ant targets
[ https://issues.apache.org/jira/browse/OFBIZ-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428831#comment-15428831 ] Jacques Le Roux commented on OFBIZ-7962: Also I noticed something important in one of Nicolas message on dev ML: http://markmail.org/message/s6g4cfnvp6lwyimp Nicolas: bq. We can create the plugins directory, and keep specialpurpose on a first step and move step by step each component present. I: bq. This is a very important point and we have to be very careful about the transition! > Migrate the patch management Ant targets > > > Key: OFBIZ-7962 > URL: https://issues.apache.org/jira/browse/OFBIZ-7962 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: Upcoming Branch > > > We need to migrate the patch management Ant targets which are documented at > https://cwiki.apache.org/confluence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz#AddressingCustomRequirementsInOFBiz-PatchManagementUsingGradleTargets -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7962) Migrate the patch management Ant targets
[ https://issues.apache.org/jira/browse/OFBIZ-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428565#comment-15428565 ] Taher Alkhateeb commented on OFBIZ-7962: Hi Jacques, FYI I am working on a PoC for the plugin system. The idea that I have in mind is for each plugin to contain a task called "install". This task executes custom logic such as applying patches or whatever is needed for the plugin to be operational in the system. Looking at these older tasks, I would suggest that we do not implement them, but instead unify the process in the plugin "install" and possibly "uninstall" tasks. Here are the reasons for my suggestions: - First of all, these older tasks only apply patches, preparing a test/dev/production environment involves much more than just patching. There is database setup and other environment factors to consider. Hence the solution is not really complete nor is it preparing the system for test/dev/production (or doing it only partially). - They are fragile because there is no dependency management. Thus one component could override / conflict with other components. - They are dependent on the version control system and external tools (patch) which is perhaps not the best idea. We can instead deploy java-based diff libraries or other solutions that are independent of surrounding environment. Code so far is still a WIP but I thought I'd note it here to avoid conflicting targets. > Migrate the patch management Ant targets > > > Key: OFBIZ-7962 > URL: https://issues.apache.org/jira/browse/OFBIZ-7962 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: Upcoming Branch > > > We need to migrate the patch management Ant targets which are documented at > https://cwiki.apache.org/confluence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz#AddressingCustomRequirementsInOFBiz-PatchManagementUsingGradleTargets -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7962) Migrate the patch management Ant targets
Jacques Le Roux created OFBIZ-7962: -- Summary: Migrate the patch management Ant targets Key: OFBIZ-7962 URL: https://issues.apache.org/jira/browse/OFBIZ-7962 Project: OFBiz Issue Type: Sub-task Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Jacques Le Roux Fix For: Upcoming Branch We need to migrate the patch management Ant targets which are documented at https://cwiki.apache.org/confluence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz#AddressingCustomRequirementsInOFBiz-PatchManagementUsingGradleTargets -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7677) Update documentation with respect to implementation of gradle as a replacement of ant
[ https://issues.apache.org/jira/browse/OFBIZ-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428381#comment-15428381 ] Jacques Le Roux commented on OFBIZ-7677: OK I did a bunch of changes in Confluence, the main changed pages are https://cwiki.apache.org/confluence/display/OFBIZ/Eclipse+Tips https://cwiki.apache.org/confluence/display/OFBIZ/Demo+and+Test+Setup+Guide https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+Technical+Production+Setup+Guide > Update documentation with respect to implementation of gradle as a > replacement of ant > - > > Key: OFBIZ-7677 > URL: https://issues.apache.org/jira/browse/OFBIZ-7677 > Project: OFBiz > Issue Type: Sub-task > Components: site >Reporter: Pierre Smits >Assignee: Jacques Le Roux > > Documentation must be updated before any release, that will have the > replacement of ant in place, can be cut. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7942) GitInfo.ftl cannot be created when sources checkout using svn
[
https://issues.apache.org/jira/browse/OFBIZ-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-7942.
--
Resolution: Fixed
Fix Version/s: Upcoming Branch
Simply check if the one of the 2 major versions managers used with OFBiz (Git
or Subversion) is used
> GitInfo.ftl cannot be created when sources checkout using svn
> -
>
> Key: OFBIZ-7942
> URL: https://issues.apache.org/jira/browse/OFBIZ-7942
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Jacques Le Roux
> Fix For: Upcoming Branch
>
> Attachments: mycomponent.tar.bz2
>
>
> When running a hot-deploy component and exception occurs. I have included the
> component for reference purposes.
> Used the following steps to create the component...
> -ran $ gradlew createComponent -PcomponentName=mycomponent
> -PcomponentResourceName=myrscname -PwebappName=mywebapp -PbasePermission=NONE
> -added request and associated screen.
> -ran $ gradlew cleanAll loadDefault
> -ran $ gradlew ofbiz
> The console shows the following exception...
> {code}
> FreeMarker template error: Template inclusion failed (for parameter value
> "ofbizhome://runtime/SvnInfo.ftl"):
> /home/wt/wt-mystuff/eclipse/workspace/ofbiz-trunk-test/runtime/SvnInfo.ftl
> (No such file or directory) FTL stack trace ("~" means nesting-related):
> - Failed at: #include "ofbizhome://runtime/SvnInfo... [in template
> "component://tomahawk/template/Footer.ftl" at line 26, column 104] Java
> stack trace (for programmers): freemarker.core._MiscTemplateException:
> [... Exception message was already printed; see it above ...] at
> freemarker.core.Include.accept(Include.java:164) at
> freemarker.core.Environment.visit(Environment.java:326) at
> freemarker.core.Environment.visit(Environment.java:332) at
> freemarker.core.Environment.process(Environment.java:305) at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.renderTemplate(FreeMarkerWorker.java:261)
> at
> org.apache.ofbiz.widget.model.HtmlWidget.renderHtmlTemplate(HtmlWidget.java:167)
> at
> org.apache.ofbiz.widget.model.HtmlWidget$HtmlTemplate.renderWidgetString(HtmlWidget.java:216)
> at
> org.apache.ofbiz.widget.model.HtmlWidget.renderWidgetString(HtmlWidget.java:140)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$PlatformSpecific.renderWidgetString(ModelScreenWidget.java:1321)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
> at
> org.apache.ofbiz.widget.model.ModelScreen.renderScreenString(ModelScreen.java:164)
> at
> org.apache.ofbiz.widget.model.ScreenFactory.renderReferencedScreen(ScreenFactory.java:214)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$IncludeScreen.renderWidgetString(ModelScreenWidget.java:780)
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
> at
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7959) Enable the status selection for WorkEffort duplication
[ https://issues.apache.org/jira/browse/OFBIZ-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427975#comment-15427975 ] Jacques Le Roux commented on OFBIZ-7959: Thanks Florian, I just tested (no review), this works well and the form looks nice to. Maybe we should not copy the 'old" workEffortId but generate automatically a new one, which could be still overridable I see no (French) labels missing, else it's easy to add them > Enable the status selection for WorkEffort duplication > -- > > Key: OFBIZ-7959 > URL: https://issues.apache.org/jira/browse/OFBIZ-7959 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Nicolas Malin >Priority: Minor > Labels: duplicate, status, workeffort > Attachments: OFBIZ-7959.patch, OFBIZ-7959.patch > > > It is possible to duplicate workeffort in the WorkEffort component > (https://localhost:8443/workeffort/control/EditWorkEffort?workEffortId=9000) > but the duplicated WorkEffort keeps the same status than the original one. So > when you duplicate a cancelled task, it is locked in the same state. > We could adapt this service to allow the selection of the status for the new > workeffort. Of course, you should be able to select only status that are > relevant to the workeffort type. > A first solution is to get the currentStatusId of the workeffort to > duplicate. Then we can access to the linked statusTypeId. So we can retrieve > all status relevant and order them by sequenceId (that way the default value > is the first statuts of the sequence : created for the task). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7385) Allow user to select multiple options in "Sales By Store" report from basic search criteria while generating report
[ https://issues.apache.org/jira/browse/OFBIZ-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427864#comment-15427864 ] Jacques Le Roux commented on OFBIZ-7385: Bump! > Allow user to select multiple options in "Sales By Store" report from basic > search criteria while generating report > --- > > Key: OFBIZ-7385 > URL: https://issues.apache.org/jira/browse/OFBIZ-7385 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Upcoming Branch >Reporter: Swapnil Shah >Assignee: Mohammad Kathawala > Attachments: OFBIZ-7385.patch, Salebystore.png > > > Currently system allow user to select any specific search criteria link and > hence report is generated only based on any one given selected criteria. > We can add the feature for generating single report based on multiple values > (possibly via checkbox?) within basic search criteria in this report namely: > 1) Product Store > 2) Order Status > and show the results based on all the selected values. Please refer attached > screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7389) Allow user to select multiple options in "Purchases by Organization" report from basic search criterias while generating report
[ https://issues.apache.org/jira/browse/OFBIZ-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427861#comment-15427861 ] Jacques Le Roux commented on OFBIZ-7389: Should we close or reopen? > Allow user to select multiple options in "Purchases by Organization" report > from basic search criterias while generating report > --- > > Key: OFBIZ-7389 > URL: https://issues.apache.org/jira/browse/OFBIZ-7389 > Project: OFBiz > Issue Type: Improvement > Components: order >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Fix For: Upcoming Branch > > Attachments: OFBIZ-7389.patch, PurchasebyOrg.png > > > Currently system allow user to select any specific search criteria link and > hence 'Purchases by Organization' report is generated only based on any one > given selected criteria. > We can add the feature for generating single report based on multiple values > (possibly via checkbox?) within basic search criteria in this report namely: > 1) To Party > 2) Order Status -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7512) 'Issue Component' option after partial issuance against required component quantity is not accounting for already issued quantity
[ https://issues.apache.org/jira/browse/OFBIZ-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427863#comment-15427863 ] Jacques Le Roux commented on OFBIZ-7512: Should we not close? > 'Issue Component' option after partial issuance against required component > quantity is not accounting for already issued quantity > - > > Key: OFBIZ-7512 > URL: https://issues.apache.org/jira/browse/OFBIZ-7512 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: Release Branch 14.12, 14.12.01, Release Branch 15.12, > 15.12.01 >Reporter: Swapnil Shah >Assignee: Divesh Dutta > Attachments: OFBIZ-7173.png, OFBIZ-7512.patch > > > Once we issue the required component partially (i.e. by producing partial > quantity while task is still is still running or in case full ATP against > required quantity is not available for issuance) then "Issue Component" is > not honoring the already made issuance and hence issuing the whole required > quantity once again. (please refer to attached screenshot) > !https://issues.apache.org/jira/secure/attachment/12811801/OFBIZ-7173.png|width=800px! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7386) Allow user to select multiple options in "Open Order Items" report from basic search criterias while generating report
[ https://issues.apache.org/jira/browse/OFBIZ-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427859#comment-15427859 ] Jacques Le Roux commented on OFBIZ-7386: Should we not close? > Allow user to select multiple options in "Open Order Items" report from basic > search criterias while generating report > -- > > Key: OFBIZ-7386 > URL: https://issues.apache.org/jira/browse/OFBIZ-7386 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Upcoming Branch >Reporter: Swapnil Shah >Assignee: Swapnil Shah > Attachments: OFBIZ-7386.patch, OrderItemReport.png > > > Currently system allow user to select any specific search criteria link and > hence 'Open Order Items' report is generated only based on any one given > selected criteria. > We can add the feature for generating single report based on multiple values > (possibly via checkbox?) within basic search criteria in this report namely: > 1) Product Store > 2) Order Type (could make it either or selection i.e. either SO or PO with > help of radio button) > 2) Order Status (Here just allow to list only "Created"/"Approved"/"Hold" > order (as systemically only these status should have open item) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7959) Enable the status selection for WorkEffort duplication
[ https://issues.apache.org/jira/browse/OFBIZ-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Montalbano Florian updated OFBIZ-7959: -- Attachment: OFBIZ-7959.patch Here is a patch including the comments : - Moved the form from flt to xml - Enabled the description in locale langage (warning : some label does not have translation and thus can not be translated) - Corrected comment in the service The form appears a little bit different so feel free to submit idea for improvement. > Enable the status selection for WorkEffort duplication > -- > > Key: OFBIZ-7959 > URL: https://issues.apache.org/jira/browse/OFBIZ-7959 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Nicolas Malin >Priority: Minor > Labels: duplicate, status, workeffort > Attachments: OFBIZ-7959.patch, OFBIZ-7959.patch > > > It is possible to duplicate workeffort in the WorkEffort component > (https://localhost:8443/workeffort/control/EditWorkEffort?workEffortId=9000) > but the duplicated WorkEffort keeps the same status than the original one. So > when you duplicate a cancelled task, it is locked in the same state. > We could adapt this service to allow the selection of the status for the new > workeffort. Of course, you should be able to select only status that are > relevant to the workeffort type. > A first solution is to get the currentStatusId of the workeffort to > duplicate. Then we can access to the linked statusTypeId. So we can retrieve > all status relevant and order them by sequenceId (that way the default value > is the first statuts of the sequence : created for the task). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7350) Manage filters in lookup auto completion
[ https://issues.apache.org/jira/browse/OFBIZ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427843#comment-15427843 ] Jacques Le Roux commented on OFBIZ-7350: Finally backported in R14.12 r1756887 R13.07 r1756888 > Manage filters in lookup auto completion > > > Key: OFBIZ-7350 > URL: https://issues.apache.org/jira/browse/OFBIZ-7350 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk, Release Branch 15.12 >Reporter: Charles STELTZLEN >Assignee: Deepak Dixit >Priority: Minor > Fix For: 15.12.01 > > Attachments: OFBIZ-7350.13.07.patch, OFBIZ-7350.patch > > > On form lookup, we can specify target parameters to pass them to the lookup > screen and do filtered searches with these parameters. It works fine when you > click on lookup button. But when you start to write something in lookup > input, these parameters are not passed to the ajax auto-complete system. So, > the results are not filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7750) Error adding foreign key: ModelEntity was null for related entity name Tenant
[
https://issues.apache.org/jira/browse/OFBIZ-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427841#comment-15427841
]
Jacques Le Roux commented on OFBIZ-7750:
Backported in
R15.12 r1756883
R14.12 r1756884
R13.07 r1756885
> Error adding foreign key: ModelEntity was null for related entity name Tenant
> -
>
> Key: OFBIZ-7750
> URL: https://issues.apache.org/jira/browse/OFBIZ-7750
> Project: OFBiz
> Issue Type: Bug
> Components: datamodel
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Assignee: Deepak Dixit
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7750.patch
>
>
> While data loading with derby database found console error
> {quote}
> Error adding foreign key: ModelEntity was null for related entity name Tenant
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-7960) css property name correction in flatgrey and rainbowstone themes
[ https://issues.apache.org/jira/browse/OFBIZ-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-7960: --- Priority: Trivial (was: Major) This is weird and does not make sense I agree your changes seems good but how did you check? BTW this is related with http://svn.apache.org/viewvc?view=revision=1361685 and I wonder if we should still care about IE7, though I guess we should :/ > css property name correction in flatgrey and rainbowstone themes > > > Key: OFBIZ-7960 > URL: https://issues.apache.org/jira/browse/OFBIZ-7960 > Project: OFBiz > Issue Type: Bug > Components: themes >Affects Versions: Trunk >Reporter: Wai >Priority: Trivial > Attachments: OFBIZ-7960.patch > > > found some funny css property names. I believe is it a syntax problem. Please > verify to make sure I'm correct. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7959) Enable the status selection for WorkEffort duplication
[ https://issues.apache.org/jira/browse/OFBIZ-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin reassigned OFBIZ-7959: Assignee: Nicolas Malin > Enable the status selection for WorkEffort duplication > -- > > Key: OFBIZ-7959 > URL: https://issues.apache.org/jira/browse/OFBIZ-7959 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Nicolas Malin >Priority: Minor > Labels: duplicate, status, workeffort > Attachments: OFBIZ-7959.patch > > > It is possible to duplicate workeffort in the WorkEffort component > (https://localhost:8443/workeffort/control/EditWorkEffort?workEffortId=9000) > but the duplicated WorkEffort keeps the same status than the original one. So > when you duplicate a cancelled task, it is locked in the same state. > We could adapt this service to allow the selection of the status for the new > workeffort. Of course, you should be able to select only status that are > relevant to the workeffort type. > A first solution is to get the currentStatusId of the workeffort to > duplicate. Then we can access to the linked statusTypeId. So we can retrieve > all status relevant and order them by sequenceId (that way the default value > is the first statuts of the sequence : created for the task). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
