Re: How to use ProjectMgr in 13.07
I've never used svn external property, just discovering. That sounds usefull and i'll try it out ! Thanks for the advice ! Gil On 20/10/2014 19:08, Jacques Le Roux wrote: I use svn external in the stable demo, already explained that in the MLs: see https://svn.apache.org/viewvc/ofbiz/trunk/tools/demo-backup/branch13.7-demo.patch?view=markup You can use the same to keep in sync, only consider projectmgr in your case. Since there is no projectmgr in R13.07 the risk of gettins conflicts or build issue is extremely low Jacques Le 20/10/2014 17:28, gil portenseigne a écrit : Hi Jacopo, Ok then, i will have to re-synchronize new trunk devs each time i'll feel it necessary. My fear is about incompatibility between 13.07 and trunk technologies, but that won't happen soon, or i might backport the evolution into my local environment. That will do the job ! Thanks Gil On 20/10/2014 16:36, Jacopo Cappellato wrote: Hi Gil, I would suggest to check it out from the trunk to the hot-deploy folder of 13.07: cd hot-deploy svn co http://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/projectmgr Jacopo On Oct 20, 2014, at 4:11 PM, gil portenseigne gil.portensei...@nereide.fr wrote: Hi all, I don't want to relaunch the debate around including the projectMgmt component into the 13.07 release, but i have a question : What is the best way to import the projectMgr component in my local 13.07 checkout environment, to start using it in a real project and to contribute on upgrading it for trunk and/or the 13.07 release ? Trunk technical evolution might be a problem if a want to stick to 13.07 release with projectMgmt features. Should I use trunk instead ? Cheers Gil -- siteon0.jpg Gil Portenseigne Consultant ERP OFBiz Société Néréide 3b Les isles 37270 Veretz Tel : 09 74 53 46 09, puis 1, poste 61 Mob : 06 82 740 444 www.nereide.fr -- www.nereide.fr Gil Portenseigne Consultant ERP OFBiz Société Néréide 3b Les isles 37270 Veretz Tel : 09 74 53 46 09, puis 1, poste 61 Mob : 06 82 740 444 www.nereide.fr http://www.nereide.fr
Re: Theme bootstrap
Hi, My apologize for answering late, I was deep under the annual balance sheet for my company... Thanks Jonatan for informations. I try to find specific theme for the front end in the branch that you told me but I can't find were it can be enable... I didnt' search a lot so maybe it was just closed to my nose and I didn't seen it... ^^ Anyway I think a lot about the work we have to do and I think it could be interesting to go deeper in the GUI modifications. Including bootstrap framework in OFBiz will be a step but maybe we can go ahead and modify best practices of screen creation. Define a design pattern that developers can follow to create standardized screens. So we can define teams to work simultaneously : - Team 1 - Framework modifications - Team 2 - List actual standard screens, list actual tools and send survey to know tools that people need in the GUI (like breadcrumb, better treeview, calendar, etc.) - Team 3 - Create the new GUI design. Define new standardization for screen listed by Team 2. A fourth team could be work on new tools integration, tests and validations. Maybe it's too ambitious and we have to go step by step but I think if we have enough good soul to work on, we can do it ! Let me know your feeling about this. Julien. PS : I can't modify the wiki that contain bootstrap integration definition. Is it possible to have modifications right ? Maybe it's better to create specific wiki page ? Le 14/10/2014 22:52, Jonatan Soto a écrit : Hi all, I made a similar proposition a year ago (see http://markmail.org/message/jc7nfodhtoordqli) but unfortunately I couldn't find the time to work on that. I'm not sure if I'll be able to join on this but I'll try. On the other hand, I seem to remember that there was a branch already created for this ( https://fisheye6.atlassian.com/browse/ofbiz/branches/frontendNewTheme2013-05-10) and a Jira ticket (https://issues.apache.org/jira/browse/OFBIZ-5040). Cheers, On Tue, Oct 14, 2014 at 8:32 AM, Adrian Crum adrian.c...@sandglass-software.com wrote: You can create a branch for this effort. Adrian Crum Sandglass Software www.sandglass-software.com On 10/14/2014 1:44 AM, Nicolas Malin wrote: Hi, The best way will be open a issue and manage by sub task each step. After that dev mailing list is good to sharing. Webconf and jabber are interesting for dynamic and quick exchange but keep in mind to report the talking result on the mailing or issue. It's important for the follow-up :) Nicolas Le 2014-10-13 09:56, Julien NICOLAS a écrit : Hi Taher, I think that we can use the OFBiz wiki to write the action plan and tasks to do, etc. I was thinking about regular webconf and we can be connected via jabber. But maybe ofbiz dev use other collaborative tools ? Any suggestions ? Regards, Julien. Le 13/10/2014 09:48, Taher Alkhateeb a écrit : Hi Nicolas, Great! I'm rubbing hands in excitement. What is the next action now? open a JIRA, have a discussion on mailing list? Furthermore, such a project requires a lot of collaboration. Do we have a platform or a solution for easier collaboration on this project? Regards, Taher Alkhateeb - Original Message - From: Nicolas Malin malin.nico...@librenberry.net To: u...@ofbiz.apache.org Sent: Monday, 13 October, 2014 4:47:05 AM Subject: Re: Theme bootstrap Hi all, I updated the page https://cwiki.apache.org/confluence/display/OFBADMIN/ New+Features+Roadmap+-+Living+Document, Now the best way will be move the discussion on dev and set your battle line on jira ;) Nicolas Le 2014-10-10 15:50, Julien NICOLAS a écrit : Hi Gavin, Pierre, Florient and Taher, It's a good news that you all join the team :) Other thanks to Adrian for informations ! Maybe the first step could be to create a setting which allow to switch from old management to the new one because it seems to be hard to change the framework without breaking old css themes. Another important point is to define a mock-up for the basic navigation and apply it for easiest navigation. This will be helpful to work with the other points. Taher, I think that it's a big task because we can find several types of screens (widget, ftl, form, etc.) and many technologies very helpful but maybe it's time to unify the main software UI. Even if we keep all technologies that make the software flexibility, it's important to be coherent in standard UI. So I suggest this following steps : 1 - Create themes switch 2 - Submit several mock-up for the basic navigation (ask community feeling) 3 - Implement basic navigation 4 - Mock-up for standard to unify standard UI (ask community feeling) 5 - Screen widgets 6 - Form Widgets 7 - Styling I think point 2 and 4 could be running during working on the others but we have to start to submit mock-ups to the community because discussions could take a lot of time ;) Julien. Le 10/10/2014 11:49, Gavin Mabie a écrit : Hi Julien I'd like to join the team. I've done
[jira] [Commented] (OFBIZ-5631) service getFxConversion is never used
[ https://issues.apache.org/jira/browse/OFBIZ-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178129#comment-14178129 ] Pierre Smits commented on OFBIZ-5631: - Thanks for the reply, Hans. I will close this issue. service getFxConversion is never used - Key: OFBIZ-5631 URL: https://issues.apache.org/jira/browse/OFBIZ-5631 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Trunk Reporter: Pierre Smits Assignee: Hans Bakker Priority: Minor service getFxConversion got incorporated in r891159. However, it is not used anywhere. I propose to remove it as part of the trim down effort -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5631) service getFxConversion is never used
[ https://issues.apache.org/jira/browse/OFBIZ-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-5631. --- Resolution: Not a Problem service getFxConversion is never used - Key: OFBIZ-5631 URL: https://issues.apache.org/jira/browse/OFBIZ-5631 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Trunk Reporter: Pierre Smits Assignee: Hans Bakker Priority: Minor service getFxConversion got incorporated in r891159. However, it is not used anywhere. I propose to remove it as part of the trim down effort -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: UOM of products
Hi Hoan, Do you think your needs are the same as this jira https://issues.apache.org/jira/browse/OFBIZ-5672 ? In this case, we can provide an add-on that can do the job. We are testing it but if you want to test it with us just let me know. Julien NICOLAS. Le 20/10/2014 03:54, Hoan dang van a écrit : Hi all I want to create a products that have more two uom ( A and B ...). B is basically UOM has price is 5$ and is default uom when sale product, A is extendedly UOM ( A = 50B) has price is 245$ and is default uom when purchasing or receipt product. Can everybody show me how this dose. Thank all
[jira] [Commented] (OFBIZ-5672) UOM conversion for supplier and sale order
[ https://issues.apache.org/jira/browse/OFBIZ-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178141#comment-14178141 ] Pierre Smits commented on OFBIZ-5672: - I suggest to raise the priority level. This is not something of minor importance and affecting various functions in multiple applications (catalog, facility, assetmaint, workeffort, manufacturing, etc). Regards, Pierre UOM conversion for supplier and sale order -- Key: OFBIZ-5672 URL: https://issues.apache.org/jira/browse/OFBIZ-5672 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Release Branch 13.07, Trunk Environment: OOTB Reporter: Julien NICOLAS Assignee: Jacques Le Roux Priority: Minor Labels: features Original Estimate: 120h Remaining Estimate: 120h It's possible to define different UomQuantity in measures tab, supplier tab or price tab of a product but OFBiz don't manage it in stock. The improvement must manage it using UomConversion table for standard conversions. When a new order (supplier or sale) is created, the user can choose the UomQuantity if more than one UomQuantity is available. By default if only one conversion is defined in UomConversion table, OFBiz will use it for both conversion way. However, it's possible to define different rules for each ways. Add new concept in UomConversion rules : rouding method and number of digit after decimal point. To be more flexible, add new fields in price and supplier product tab. - Uom conversion factor - Rounding method - Number of digit after decimal point If those fields are empty, OFBiz will use the standard UomConversion table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5434) Improvement of Dutch localization in Product
[ https://issues.apache.org/jira/browse/OFBIZ-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178154#comment-14178154 ] Pierre Smits commented on OFBIZ-5434: - [~toashishvijay] Are you still going to work on this? Regards, Pierre Improvement of Dutch localization in Product Key: OFBIZ-5434 URL: https://issues.apache.org/jira/browse/OFBIZ-5434 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Trunk Reporter: Pierre Smits Assignee: Ashish Vijaywargiya Attachments: OFBIZ-5434-PRODUCT_Labels.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5672) UOM conversion for supplier and sale order
[ https://issues.apache.org/jira/browse/OFBIZ-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178155#comment-14178155 ] Julien NICOLAS commented on OFBIZ-5672: --- Hi Pierre, I put minor because I was thinking that it's not a bug, just an improvement so don't need to be a priority for comiters. But maybe I'm wrong and priority can be linked to the complexity of the modifications. Regards, Julien. UOM conversion for supplier and sale order -- Key: OFBIZ-5672 URL: https://issues.apache.org/jira/browse/OFBIZ-5672 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Release Branch 13.07, Trunk Environment: OOTB Reporter: Julien NICOLAS Assignee: Jacques Le Roux Priority: Minor Labels: features Original Estimate: 120h Remaining Estimate: 120h It's possible to define different UomQuantity in measures tab, supplier tab or price tab of a product but OFBiz don't manage it in stock. The improvement must manage it using UomConversion table for standard conversions. When a new order (supplier or sale) is created, the user can choose the UomQuantity if more than one UomQuantity is available. By default if only one conversion is defined in UomConversion table, OFBiz will use it for both conversion way. However, it's possible to define different rules for each ways. Add new concept in UomConversion rules : rouding method and number of digit after decimal point. To be more flexible, add new fields in price and supplier product tab. - Uom conversion factor - Rounding method - Number of digit after decimal point If those fields are empty, OFBiz will use the standard UomConversion table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5529) User should be able to delete associated production runs
[ https://issues.apache.org/jira/browse/OFBIZ-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178156#comment-14178156 ] Pierre Smits commented on OFBIZ-5529: - [~toashishvijay] Are you still going to work on this? Regards, Pierre User should be able to delete associated production runs Key: OFBIZ-5529 URL: https://issues.apache.org/jira/browse/OFBIZ-5529 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Pierre Smits Assignee: Ashish Vijaywargiya Attachments: OFBIZ-5529-MFG-removeAssoc.patch If associations to production runs are set manually in a production run, it should be possible to delete erroneous associations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5672) UOM conversion for supplier and sale order
[ https://issues.apache.org/jira/browse/OFBIZ-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178159#comment-14178159 ] Pierre Smits commented on OFBIZ-5672: - Julien, Even improvements can have a priority. E.g. improving code comments could be regarded as minor, whereas improvement of functionality has a higher classification. I let you decide. It was a suggestion. Regards, Pierre UOM conversion for supplier and sale order -- Key: OFBIZ-5672 URL: https://issues.apache.org/jira/browse/OFBIZ-5672 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Release Branch 13.07, Trunk Environment: OOTB Reporter: Julien NICOLAS Assignee: Jacques Le Roux Priority: Minor Labels: features Original Estimate: 120h Remaining Estimate: 120h It's possible to define different UomQuantity in measures tab, supplier tab or price tab of a product but OFBiz don't manage it in stock. The improvement must manage it using UomConversion table for standard conversions. When a new order (supplier or sale) is created, the user can choose the UomQuantity if more than one UomQuantity is available. By default if only one conversion is defined in UomConversion table, OFBiz will use it for both conversion way. However, it's possible to define different rules for each ways. Add new concept in UomConversion rules : rouding method and number of digit after decimal point. To be more flexible, add new fields in price and supplier product tab. - Uom conversion factor - Rounding method - Number of digit after decimal point If those fields are empty, OFBiz will use the standard UomConversion table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Theme bootstrap
Hi Julien, Le 21/10/2014 10:18, Julien NICOLAS a écrit : Hi, My apologize for answering late, I was deep under the annual balance sheet for my company... Thanks Jonatan for informations. I try to find specific theme for the front end in the branch that you told me but I can't find were it can be enable... I didnt' search a lot so maybe it was just closed to my nose and I didn't seen it... ^^ It's there https://svn.apache.org/viewvc/ofbiz/branches/frontendNewTheme2013-05-10/ Anyway I think a lot about the work we have to do and I think it could be interesting to go deeper in the GUI modifications. Including bootstrap framework in OFBiz will be a step but maybe we can go ahead and modify best practices of screen creation. Define a design pattern that developers can follow to create standardized screens. So we can define teams to work simultaneously : - Team 1 - Framework modifications - Team 2 - List actual standard screens, list actual tools and send survey to know tools that people need in the GUI (like breadcrumb, better treeview, calendar, etc.) - Team 3 - Create the new GUI design. Define new standardization for screen listed by Team 2. A fourth team could be work on new tools integration, tests and validations. Maybe it's too ambitious and we have to go step by step but I think if we have enough good soul to work on, we can do it ! Let me know your feeling about this. Julien. PS : I can't modify the wiki that contain bootstrap integration definition. Is it possible to have modifications right ? Maybe it's better to create specific wiki page ? Only the wiki https://cwiki.apache.org/confluence/display/OFBIZ/Home is open to contributors The idea is you can always add comments (possibly formatted, they use the same editor) and we can use them to complete the Confluence not open workspaces (members of the OFBiz team monitor changes in Confluence) Jacques Le 14/10/2014 22:52, Jonatan Soto a écrit : Hi all, I made a similar proposition a year ago (see http://markmail.org/message/jc7nfodhtoordqli) but unfortunately I couldn't find the time to work on that. I'm not sure if I'll be able to join on this but I'll try. On the other hand, I seem to remember that there was a branch already created for this ( https://fisheye6.atlassian.com/browse/ofbiz/branches/frontendNewTheme2013-05-10) and a Jira ticket (https://issues.apache.org/jira/browse/OFBIZ-5040). Cheers, On Tue, Oct 14, 2014 at 8:32 AM, Adrian Crum adrian.c...@sandglass-software.com wrote: You can create a branch for this effort. Adrian Crum Sandglass Software www.sandglass-software.com On 10/14/2014 1:44 AM, Nicolas Malin wrote: Hi, The best way will be open a issue and manage by sub task each step. After that dev mailing list is good to sharing. Webconf and jabber are interesting for dynamic and quick exchange but keep in mind to report the talking result on the mailing or issue. It's important for the follow-up :) Nicolas Le 2014-10-13 09:56, Julien NICOLAS a écrit : Hi Taher, I think that we can use the OFBiz wiki to write the action plan and tasks to do, etc. I was thinking about regular webconf and we can be connected via jabber. But maybe ofbiz dev use other collaborative tools ? Any suggestions ? Regards, Julien. Le 13/10/2014 09:48, Taher Alkhateeb a écrit : Hi Nicolas, Great! I'm rubbing hands in excitement. What is the next action now? open a JIRA, have a discussion on mailing list? Furthermore, such a project requires a lot of collaboration. Do we have a platform or a solution for easier collaboration on this project? Regards, Taher Alkhateeb - Original Message - From: Nicolas Malin malin.nico...@librenberry.net To: u...@ofbiz.apache.org Sent: Monday, 13 October, 2014 4:47:05 AM Subject: Re: Theme bootstrap Hi all, I updated the page https://cwiki.apache.org/confluence/display/OFBADMIN/ New+Features+Roadmap+-+Living+Document, Now the best way will be move the discussion on dev and set your battle line on jira ;) Nicolas Le 2014-10-10 15:50, Julien NICOLAS a écrit : Hi Gavin, Pierre, Florient and Taher, It's a good news that you all join the team :) Other thanks to Adrian for informations ! Maybe the first step could be to create a setting which allow to switch from old management to the new one because it seems to be hard to change the framework without breaking old css themes. Another important point is to define a mock-up for the basic navigation and apply it for easiest navigation. This will be helpful to work with the other points. Taher, I think that it's a big task because we can find several types of screens (widget, ftl, form, etc.) and many technologies very helpful but maybe it's time to unify the main software UI. Even if we keep all technologies that make the software flexibility, it's important to be coherent in standard UI. So I suggest this following steps : 1 - Create themes switch 2 - Submit several mock-up for the basic
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178227#comment-14178227 ] Jacques Le Roux commented on OFBIZ-5771: Actually there is more than just putting back the error.log (see org.ofbiz additivity logger added in attached patch). Let me explain my point of view. OOTB we use the COMPACT date option which shows as 20141021103936722, I think we will agree this is barely legible. I suggest to use rather dd HH:mm:ss,SSS which shows as 20 20:13:14,523. Because the files have already the year and month in names it should not be a problem. And from my experience, when browsing logs you rarely get back more than a month. As reported at http://markmail.org/message/cz7mypkzbaw57ixk, a Freemarker error generated by an error in an OFBiz Java file called by a Freemarker static call currently shows only in external.log. I guess it's the same for errors in custom Freemarker macros (did not test). So I added an additivity logger for Freemarker errors to error.log. I did the same to ofbiz.log and stdout. *Below are 2 mount points:* You might say that I'm conservative (hint, I'm not) but I prefer to not zip rolling logs. Because when browsing it's easier and with the rollover strategy I don't think the size of the logs kepts by day are a problem. Also users should have a policy to regularly backup and clean their logs somewhere else than just keeping in runtime/logs. Notably in production where a disk full can always happen even with zipped files. I also prefer to keep more rolled ofbiz.logs. Ten, as it was before, seems a good number to me. For error it would be 3, no change (4) for external. *Here are some things I want to report:* If you use *log level=always* in Minilang it will show as Fatal, it's the same for Debug.log(). I did not investigate this yet. In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-5771: --- Attachment: log4j2.xml.patch In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178230#comment-14178230 ] Jacques Le Roux commented on OFBIZ-5771: I'm also interested about thoughts about a schema validation for log4j2, see https://issues.apache.org/jira/browse/LOG4J2-170 In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-5833) Tasks menu item should only be visible to persons with appropriate rights
Pierre Smits created OFBIZ-5833: --- Summary: Tasks menu item should only be visible to persons with appropriate rights Key: OFBIZ-5833 URL: https://issues.apache.org/jira/browse/OFBIZ-5833 Project: OFBiz Issue Type: Bug Components: specialpurpose/projectmgr Affects Versions: Trunk, Release Branch 13.07, Release Branch 12.04, Release Branch 11.04 Reporter: Pierre Smits Currently the menu item Tasks (and the subsequent overview) is visibe to all persons having basic access to the application. However, persons with assigned tasks can view these through the My Tasks options and project managers of assigned projects can view the tasks via the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-3457) Project Manager (projectmgr) -Project Summary - [Pick any project] - Schedule reports the following error...
[ https://issues.apache.org/jira/browse/OFBIZ-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178254#comment-14178254 ] Pierre Smits commented on OFBIZ-3457: - I could not reproduce this error. And that the Gantt chart is shown after the action is performed is of minor concern. I propose to close this issue. Project Manager (projectmgr) -Project Summary - [Pick any project] - Schedule reports the following error... --- Key: OFBIZ-3457 URL: https://issues.apache.org/jira/browse/OFBIZ-3457 Project: OFBiz Issue Type: Bug Components: specialpurpose/projectmgr Environment: 9.04 Reporter: Ruth Hoffman Navigate to the Project Manager application Under Project Summary, select any [Demo] project by clicking on the link provided From Project Summary Web Page, select the Schedule button The following error is returned to the user: The Following Errors Occurred: ERROR: Could not complete the Project Scheduler sets the planningdates according task requirements and available resources [file:.../ofbiz-release9.04/specialpurpose/projectmgr/script/org/ofbiz/project/ProjectServices.xml#scheduleProject] process [Could not find method to execute named addDaysToTimestamp: java.lang.NoSuchMethodException: org.ofbiz.base.util.UtilDateTime.addDaysToTimestamp(java.lang.String, java.lang.String)] And the following message is displayed: The following occurred: The action was performed successfully. And a Gantt Chart is displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5833) Tasks menu item should only be visible to persons with appropriate rights
[ https://issues.apache.org/jira/browse/OFBIZ-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-5833: Issue Type: Improvement (was: Bug) Tasks menu item should only be visible to persons with appropriate rights - Key: OFBIZ-5833 URL: https://issues.apache.org/jira/browse/OFBIZ-5833 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Release Branch 11.04, Release Branch 12.04, Release Branch 13.07, Trunk Reporter: Pierre Smits Labels: projectmgr, tasks Currently the menu item Tasks (and the subsequent overview) is visibe to all persons having basic access to the application. However, persons with assigned tasks can view these through the My Tasks options and project managers of assigned projects can view the tasks via the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5833) Tasks menu item should only be visible to persons with appropriate rights
[ https://issues.apache.org/jira/browse/OFBIZ-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-5833: Attachment: OFBIZ-5818-ProjectMgrTaskMenuItem.patch This patch fixes the issue. Tasks menu item should only be visible to persons with appropriate rights - Key: OFBIZ-5833 URL: https://issues.apache.org/jira/browse/OFBIZ-5833 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Release Branch 11.04, Release Branch 12.04, Release Branch 13.07, Trunk Reporter: Pierre Smits Labels: projectmgr, tasks Attachments: OFBIZ-5818-ProjectMgrTaskMenuItem.patch Currently the menu item Tasks (and the subsequent overview) is visibe to all persons having basic access to the application. However, persons with assigned tasks can view these through the My Tasks options and project managers of assigned projects can view the tasks via the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Please stop! was: Where is the error.log gone?
Hi All, Before I open a vote for this, please check https://issues.apache.org/jira/browse/OFBIZ-5771 Jacques Le 17/09/2014 08:50, Pierre Smits a écrit : The first 'in person' hangout is at Apachecon 2014, in Budapest, Hungary. 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, Sep 16, 2014 at 8:12 PM, Paul Piper p...@ilscipio.com wrote: +1 on my end as well. It would allow us to answer newcomer-questions and also make it easier to discuss important topics that have the tendency to get heated. -- View this message in context: http://ofbiz.135035.n4.nabble.com/Where-is-the-error-log-gone-tp4654961p4655319.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178280#comment-14178280 ] Jacopo Cappellato commented on OFBIZ-5771: -- My votes would be: * change date format to dd HH:mm:ss,SSS -1 I don't find the opposed format clearer than the existing one * set additivity=true for freemarker +1 (but in your patch you are changing additivity for all the loggers) * not zipping rolling files +0 * keeping 10 rolling files +0 * adding error.log -0 (you know what I think but I will not further object on this subject) In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
OFBiz Logging (was: Where is the error.log gone?)
Jacques, This issue affects all users of OFBiz. I suggest to post the announcement of the vote to all mailing lists. I also suggest to follow the ASF conventions regarding announcements and voting. 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, Oct 21, 2014 at 1:15 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi All, Before I open a vote for this, please check https://issues.apache.org/ jira/browse/OFBIZ-5771 Jacques Le 17/09/2014 08:50, Pierre Smits a écrit : The first 'in person' hangout is at Apachecon 2014, in Budapest, Hungary. 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, Sep 16, 2014 at 8:12 PM, Paul Piper p...@ilscipio.com wrote: +1 on my end as well. It would allow us to answer newcomer-questions and also make it easier to discuss important topics that have the tendency to get heated. -- View this message in context: http://ofbiz.135035.n4.nabble.com/Where-is-the-error-log- gone-tp4654961p4655319.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[DISCUSSION] JIRA issues for web and wiki pages
Hi all, Currently we only register issues related to the OFBiz code. But we also see a lot of comments in wiki pages regarding corrections. These comments can exists quite a long time and it seems that these are frequently overlooked. Should we not also have a setup in JIRA regarding the web and wiki pages? This helps us to stay aware of bugs and improvements thereof, and help us to track contributors and patches. Having JIRA issues for this seems to be done also in a number of other Apache projects. 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] [Comment Edited] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178280#comment-14178280 ] Jacopo Cappellato edited comment on OFBIZ-5771 at 10/21/14 11:46 AM: - My votes would be: * change date format to dd HH:mm:ss,SSS -1 I don't find the proposed format clearer than the existing one * set additivity=true for freemarker +1 (but in your patch you are changing additivity for all the loggers) * not zipping rolling files +0 * keeping 10 rolling files +0 * adding error.log -0 (you know what I think but I will not further object on this subject) was (Author: jacopoc): My votes would be: * change date format to dd HH:mm:ss,SSS -1 I don't find the opposed format clearer than the existing one * set additivity=true for freemarker +1 (but in your patch you are changing additivity for all the loggers) * not zipping rolling files +0 * keeping 10 rolling files +0 * adding error.log -0 (you know what I think but I will not further object on this subject) In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: OFBiz Logging (was: Where is the error.log gone?)
Pierre, I agree, but it's not yet a vote, just a request to review for now ;) Jacques Le 21/10/2014 13:38, Pierre Smits a écrit : Jacques, This issue affects all users of OFBiz. I suggest to post the announcement of the vote to all mailing lists. I also suggest to follow the ASF conventions regarding announcements and voting. 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, Oct 21, 2014 at 1:15 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi All, Before I open a vote for this, please check https://issues.apache.org/ jira/browse/OFBIZ-5771 Jacques Le 17/09/2014 08:50, Pierre Smits a écrit : The first 'in person' hangout is at Apachecon 2014, in Budapest, Hungary. 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, Sep 16, 2014 at 8:12 PM, Paul Piper p...@ilscipio.com wrote: +1 on my end as well. It would allow us to answer newcomer-questions and also make it easier to discuss important topics that have the tendency to get heated. -- View this message in context: http://ofbiz.135035.n4.nabble.com/Where-is-the-error-log- gone-tp4654961p4655319.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[jira] [Comment Edited] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178230#comment-14178230 ] Jacques Le Roux edited comment on OFBIZ-5771 at 10/21/14 11:51 AM: --- I'm also interested about thoughts on a schema validation for log4j2, see https://issues.apache.org/jira/browse/LOG4J2-170 was (Author: jacques.le.roux): I'm also interested about thoughts about a schema validation for log4j2, see https://issues.apache.org/jira/browse/LOG4J2-170 In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[
https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178321#comment-14178321
]
Jacques Le Roux commented on OFBIZ-5771:
Jacopo,
{quote}
set additivity=true for freemarker
+1
(but in your patch you are changing additivity for all the loggers)
{quote}
Yes I did that quickly this morning adding them one after the other, I will
update the patch with
{code}
logger name=freemarker additivity=true
appender-ref ref=error level=error/
appender-ref ref=ofbiz level=error/
appender-ref ref=stdout level=error/
/logger
{code}
rather
That's what you mean? IMO, we need to show the errors like Static in all those
appenders. I have not tested all cases, more a proposition for now.
In OFBIZ-5287 the error.log has been removed, some want to put it back
--
Key: OFBIZ-5771
URL: https://issues.apache.org/jira/browse/OFBIZ-5771
Project: OFBiz
Issue Type: Improvement
Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Attachments: log4j2.xml.patch
To be amended later
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178328#comment-14178328 ] Christian Geisert commented on OFBIZ-5771: -- Just a comment on the date format (need to think about the other proposals)... The current fomat (20141021103936722) is hard to read, but I don't like the suggestion to show the day only either. What about going back to the full date with separators? In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5818) Removal of unapplied code from ProjectMgr secas.xml
[ https://issues.apache.org/jira/browse/OFBIZ-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato updated OFBIZ-5818: - Priority: Trivial (was: Critical) Removal of unapplied code from ProjectMgr secas.xml --- Key: OFBIZ-5818 URL: https://issues.apache.org/jira/browse/OFBIZ-5818 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Trunk Reporter: Pierre Smits Priority: Trivial Attachments: OFBIZ-5818-ProjectMgrDeadCodeRemoval.patch This is related to http://ofbiz.markmail.org/message/b6n2fa5prwiekgcv?q=checkProjectMembership I did a check in viewvc and the functionality in secas.xml regarding 'updateTaskAssignment' was commented out in commit 706506 (5 years ago), see http://svn.apache.org/viewvc/ofbiz/trunk/specialpurpose/projectmgr/servicedef/secas.xml?revision=706506view=markuppathrev=706506 as part of a set of changes by Hans, see http://svn.apache.org/viewvc?view=revisionrevision=706506 Unfortunately no clues (other than the comment line in the file) were provided as to what the circumstances where that lead to the conclusion and the disablement of the service. I also did a search on whether 'updateTaskAssignment' was referenced anywhere else in the code of the ProjectMgr component, and everywhere else, and this is what I found: * it has a definition in servicedef.xml, pointing to a simple service in file ProjectServices.xml * it is referenced in the controller.xml and in TaskForms.xml * it is referenced in the controller.xml of the SFA application pointing to the service of ProjectMgr. I also did a search in JIRA whether both 'checkProjectMembership and 'updateTaskAssigment occured, but could not find an issue. It seems to me that this is some kind of forgotten leftover of a code change. I will create a patch to remove the commented out code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-5818) Removal of unapplied code from ProjectMgr secas.xml
[ https://issues.apache.org/jira/browse/OFBIZ-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato reassigned OFBIZ-5818: Assignee: Jacopo Cappellato Removal of unapplied code from ProjectMgr secas.xml --- Key: OFBIZ-5818 URL: https://issues.apache.org/jira/browse/OFBIZ-5818 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Trunk Reporter: Pierre Smits Assignee: Jacopo Cappellato Priority: Trivial Attachments: OFBIZ-5818-ProjectMgrDeadCodeRemoval.patch This is related to http://ofbiz.markmail.org/message/b6n2fa5prwiekgcv?q=checkProjectMembership I did a check in viewvc and the functionality in secas.xml regarding 'updateTaskAssignment' was commented out in commit 706506 (5 years ago), see http://svn.apache.org/viewvc/ofbiz/trunk/specialpurpose/projectmgr/servicedef/secas.xml?revision=706506view=markuppathrev=706506 as part of a set of changes by Hans, see http://svn.apache.org/viewvc?view=revisionrevision=706506 Unfortunately no clues (other than the comment line in the file) were provided as to what the circumstances where that lead to the conclusion and the disablement of the service. I also did a search on whether 'updateTaskAssignment' was referenced anywhere else in the code of the ProjectMgr component, and everywhere else, and this is what I found: * it has a definition in servicedef.xml, pointing to a simple service in file ProjectServices.xml * it is referenced in the controller.xml and in TaskForms.xml * it is referenced in the controller.xml of the SFA application pointing to the service of ProjectMgr. I also did a search in JIRA whether both 'checkProjectMembership and 'updateTaskAssigment occured, but could not find an issue. It seems to me that this is some kind of forgotten leftover of a code change. I will create a patch to remove the commented out code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5818) Removal of unapplied code from ProjectMgr secas.xml
[ https://issues.apache.org/jira/browse/OFBIZ-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178337#comment-14178337 ] Pierre Smits commented on OFBIZ-5818: - What kind of action is this, Jacopo? First you use this issue as one of the blockers to have the PROJECTMGR component released in r13.07.01 and now you regard it as trivial? Are you doing this just to get your way, and/or to show your animosity towards my contributions? Removal of unapplied code from ProjectMgr secas.xml --- Key: OFBIZ-5818 URL: https://issues.apache.org/jira/browse/OFBIZ-5818 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Trunk Reporter: Pierre Smits Assignee: Jacopo Cappellato Priority: Trivial Attachments: OFBIZ-5818-ProjectMgrDeadCodeRemoval.patch This is related to http://ofbiz.markmail.org/message/b6n2fa5prwiekgcv?q=checkProjectMembership I did a check in viewvc and the functionality in secas.xml regarding 'updateTaskAssignment' was commented out in commit 706506 (5 years ago), see http://svn.apache.org/viewvc/ofbiz/trunk/specialpurpose/projectmgr/servicedef/secas.xml?revision=706506view=markuppathrev=706506 as part of a set of changes by Hans, see http://svn.apache.org/viewvc?view=revisionrevision=706506 Unfortunately no clues (other than the comment line in the file) were provided as to what the circumstances where that lead to the conclusion and the disablement of the service. I also did a search on whether 'updateTaskAssignment' was referenced anywhere else in the code of the ProjectMgr component, and everywhere else, and this is what I found: * it has a definition in servicedef.xml, pointing to a simple service in file ProjectServices.xml * it is referenced in the controller.xml and in TaskForms.xml * it is referenced in the controller.xml of the SFA application pointing to the service of ProjectMgr. I also did a search in JIRA whether both 'checkProjectMembership and 'updateTaskAssigment occured, but could not find an issue. It seems to me that this is some kind of forgotten leftover of a code change. I will create a patch to remove the commented out code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-5818) Removal of unapplied code from ProjectMgr secas.xml
[ https://issues.apache.org/jira/browse/OFBIZ-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178337#comment-14178337 ] Pierre Smits edited comment on OFBIZ-5818 at 10/21/14 12:32 PM: What kind of action is this, Jacopo? First you use this issue as one of the blockers to have the PROJECTMGR component released in r13.07.01 and now you regard it as trivial? Are you doing this just to get your way, and/or to show your animosity towards my and therefor my contributions? Does that truly help the project? was (Author: pfm.smits): What kind of action is this, Jacopo? First you use this issue as one of the blockers to have the PROJECTMGR component released in r13.07.01 and now you regard it as trivial? Are you doing this just to get your way, and/or to show your animosity towards my contributions? Removal of unapplied code from ProjectMgr secas.xml --- Key: OFBIZ-5818 URL: https://issues.apache.org/jira/browse/OFBIZ-5818 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Trunk Reporter: Pierre Smits Assignee: Jacopo Cappellato Priority: Trivial Attachments: OFBIZ-5818-ProjectMgrDeadCodeRemoval.patch This is related to http://ofbiz.markmail.org/message/b6n2fa5prwiekgcv?q=checkProjectMembership I did a check in viewvc and the functionality in secas.xml regarding 'updateTaskAssignment' was commented out in commit 706506 (5 years ago), see http://svn.apache.org/viewvc/ofbiz/trunk/specialpurpose/projectmgr/servicedef/secas.xml?revision=706506view=markuppathrev=706506 as part of a set of changes by Hans, see http://svn.apache.org/viewvc?view=revisionrevision=706506 Unfortunately no clues (other than the comment line in the file) were provided as to what the circumstances where that lead to the conclusion and the disablement of the service. I also did a search on whether 'updateTaskAssignment' was referenced anywhere else in the code of the ProjectMgr component, and everywhere else, and this is what I found: * it has a definition in servicedef.xml, pointing to a simple service in file ProjectServices.xml * it is referenced in the controller.xml and in TaskForms.xml * it is referenced in the controller.xml of the SFA application pointing to the service of ProjectMgr. I also did a search in JIRA whether both 'checkProjectMembership and 'updateTaskAssigment occured, but could not find an issue. It seems to me that this is some kind of forgotten leftover of a code change. I will create a patch to remove the commented out code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [DISCUSSION] JIRA issues for web and wiki pages
It would be good to have a well organized and supported system for tracking defects of all types including documentation. The JIRA has a very very helpful features that would allow us to identify the importance of problems, any version dependencies, assigned person, etc. Ron On 21/10/2014 7:45 AM, Pierre Smits wrote: Hi all, Currently we only register issues related to the OFBiz code. But we also see a lot of comments in wiki pages regarding corrections. These comments can exists quite a long time and it seems that these are frequently overlooked. Should we not also have a setup in JIRA regarding the web and wiki pages? This helps us to stay aware of bugs and improvements thereof, and help us to track contributors and patches. Having JIRA issues for this seems to be done also in a number of other Apache projects. Regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
[jira] [Closed] (OFBIZ-5818) Removal of unapplied code from ProjectMgr secas.xml
[ https://issues.apache.org/jira/browse/OFBIZ-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato closed OFBIZ-5818. Removal of unapplied code from ProjectMgr secas.xml --- Key: OFBIZ-5818 URL: https://issues.apache.org/jira/browse/OFBIZ-5818 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Trunk Reporter: Pierre Smits Assignee: Jacopo Cappellato Priority: Trivial Fix For: Upcoming Branch Attachments: OFBIZ-5818-ProjectMgrDeadCodeRemoval.patch This is related to http://ofbiz.markmail.org/message/b6n2fa5prwiekgcv?q=checkProjectMembership I did a check in viewvc and the functionality in secas.xml regarding 'updateTaskAssignment' was commented out in commit 706506 (5 years ago), see http://svn.apache.org/viewvc/ofbiz/trunk/specialpurpose/projectmgr/servicedef/secas.xml?revision=706506view=markuppathrev=706506 as part of a set of changes by Hans, see http://svn.apache.org/viewvc?view=revisionrevision=706506 Unfortunately no clues (other than the comment line in the file) were provided as to what the circumstances where that lead to the conclusion and the disablement of the service. I also did a search on whether 'updateTaskAssignment' was referenced anywhere else in the code of the ProjectMgr component, and everywhere else, and this is what I found: * it has a definition in servicedef.xml, pointing to a simple service in file ProjectServices.xml * it is referenced in the controller.xml and in TaskForms.xml * it is referenced in the controller.xml of the SFA application pointing to the service of ProjectMgr. I also did a search in JIRA whether both 'checkProjectMembership and 'updateTaskAssigment occured, but could not find an issue. It seems to me that this is some kind of forgotten leftover of a code change. I will create a patch to remove the commented out code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5818) Removal of unapplied code from ProjectMgr secas.xml
[ https://issues.apache.org/jira/browse/OFBIZ-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178355#comment-14178355 ] Jacopo Cappellato commented on OFBIZ-5818: -- Committed to trunk with rev. 1633362 Removal of unapplied code from ProjectMgr secas.xml --- Key: OFBIZ-5818 URL: https://issues.apache.org/jira/browse/OFBIZ-5818 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Trunk Reporter: Pierre Smits Assignee: Jacopo Cappellato Priority: Trivial Fix For: Upcoming Branch Attachments: OFBIZ-5818-ProjectMgrDeadCodeRemoval.patch This is related to http://ofbiz.markmail.org/message/b6n2fa5prwiekgcv?q=checkProjectMembership I did a check in viewvc and the functionality in secas.xml regarding 'updateTaskAssignment' was commented out in commit 706506 (5 years ago), see http://svn.apache.org/viewvc/ofbiz/trunk/specialpurpose/projectmgr/servicedef/secas.xml?revision=706506view=markuppathrev=706506 as part of a set of changes by Hans, see http://svn.apache.org/viewvc?view=revisionrevision=706506 Unfortunately no clues (other than the comment line in the file) were provided as to what the circumstances where that lead to the conclusion and the disablement of the service. I also did a search on whether 'updateTaskAssignment' was referenced anywhere else in the code of the ProjectMgr component, and everywhere else, and this is what I found: * it has a definition in servicedef.xml, pointing to a simple service in file ProjectServices.xml * it is referenced in the controller.xml and in TaskForms.xml * it is referenced in the controller.xml of the SFA application pointing to the service of ProjectMgr. I also did a search in JIRA whether both 'checkProjectMembership and 'updateTaskAssigment occured, but could not find an issue. It seems to me that this is some kind of forgotten leftover of a code change. I will create a patch to remove the commented out code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178358#comment-14178358 ] Jacques Le Roux commented on OFBIZ-5771: Christian, My idea was to win 6 chars which are obvious (we know which year and month we are in logs), but using DEFAULT date format option would be good to me as well. In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178365#comment-14178365 ] Jacopo Cappellato commented on OFBIZ-5771: -- If we don't like 20141021103936722 the following formats would be good defaults 20141021 10:39:36.722 2014-10-21 10:39:36.722 The last one should be the original one. In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5818) Removal of unapplied code from ProjectMgr secas.xml
[ https://issues.apache.org/jira/browse/OFBIZ-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178381#comment-14178381 ] Jacques Le Roux commented on OFBIZ-5818: Pierre, It seems to me that Jacopo simply considered this issue as trivial while fixing it. Either ways, it's good to have it in the changes log. Removal of unapplied code from ProjectMgr secas.xml --- Key: OFBIZ-5818 URL: https://issues.apache.org/jira/browse/OFBIZ-5818 Project: OFBiz Issue Type: Improvement Components: specialpurpose/projectmgr Affects Versions: Trunk Reporter: Pierre Smits Assignee: Jacopo Cappellato Priority: Trivial Fix For: Upcoming Branch Attachments: OFBIZ-5818-ProjectMgrDeadCodeRemoval.patch This is related to http://ofbiz.markmail.org/message/b6n2fa5prwiekgcv?q=checkProjectMembership I did a check in viewvc and the functionality in secas.xml regarding 'updateTaskAssignment' was commented out in commit 706506 (5 years ago), see http://svn.apache.org/viewvc/ofbiz/trunk/specialpurpose/projectmgr/servicedef/secas.xml?revision=706506view=markuppathrev=706506 as part of a set of changes by Hans, see http://svn.apache.org/viewvc?view=revisionrevision=706506 Unfortunately no clues (other than the comment line in the file) were provided as to what the circumstances where that lead to the conclusion and the disablement of the service. I also did a search on whether 'updateTaskAssignment' was referenced anywhere else in the code of the ProjectMgr component, and everywhere else, and this is what I found: * it has a definition in servicedef.xml, pointing to a simple service in file ProjectServices.xml * it is referenced in the controller.xml and in TaskForms.xml * it is referenced in the controller.xml of the SFA application pointing to the service of ProjectMgr. I also did a search in JIRA whether both 'checkProjectMembership and 'updateTaskAssigment occured, but could not find an issue. It seems to me that this is some kind of forgotten leftover of a code change. I will create a patch to remove the commented out code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178384#comment-14178384 ] Jacques Le Roux commented on OFBIZ-5771: Yes indeed Jacopo, the last one is the log4j2 DEFAULT option. In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178397#comment-14178397 ] Jacques Le Roux commented on OFBIZ-5771: BTW about my comment above for Freemarker, it's wrong. We get debug information in stdout and ofbiz.log, not wanted! I rather suggest to remove the whole Freemarker block for now. Anyway, as I said I need to investigate more about Freemarker logging. In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[ https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178416#comment-14178416 ] Jacopo Cappellato commented on OFBIZ-5771: -- Removing the whole FreeMarker block is probably not the right way to go because it may enable all FreeMarker logging; in the past we had this issue in the trunk after an upgrade to a new Freemarker and all screen rendering was very slow. In OFBIZ-5287 the error.log has been removed, some want to put it back -- Key: OFBIZ-5771 URL: https://issues.apache.org/jira/browse/OFBIZ-5771 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Attachments: log4j2.xml.patch To be amended later -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5771) In OFBIZ-5287 the error.log has been removed, some want to put it back
[
https://issues.apache.org/jira/browse/OFBIZ-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178436#comment-14178436
]
Jacques Le Roux commented on OFBIZ-5771:
I mean only
{code}
logger name=freemarker additivity=true
appender-ref ref=error level=error/
appender-ref ref=ofbiz level=error/
appender-ref ref=stdout level=error/
/logger
{code}
I did not suggest to change
{code}
logger name=freemarker level=warn
appender-ref ref=external/
/logger
{code}
In OFBIZ-5287 the error.log has been removed, some want to put it back
--
Key: OFBIZ-5771
URL: https://issues.apache.org/jira/browse/OFBIZ-5771
Project: OFBiz
Issue Type: Improvement
Components: framework
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Attachments: log4j2.xml.patch
To be amended later
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Theme bootstrap
Hi Jacques, Le 21/10/2014 11:29, Jacques Le Roux a écrit : Hi Julien, Le 21/10/2014 10:18, Julien NICOLAS a écrit : Hi, My apologize for answering late, I was deep under the annual balance sheet for my company... Thanks Jonatan for informations. I try to find specific theme for the front end in the branch that you told me but I can't find were it can be enable... I didnt' search a lot so maybe it was just closed to my nose and I didn't seen it... ^^ It's there https://svn.apache.org/viewvc/ofbiz/branches/frontendNewTheme2013-05-10/ Yes, I've downloaded this branch as you told me but after building, load demo data and lauching, I still can't see any modifications in the front-end... I never use front-end so maybe I didn't use the good path... (http://localhost:8080/ecommerce/) Anyway I think a lot about the work we have to do and I think it could be interesting to go deeper in the GUI modifications. Including bootstrap framework in OFBiz will be a step but maybe we can go ahead and modify best practices of screen creation. Define a design pattern that developers can follow to create standardized screens. So we can define teams to work simultaneously : - Team 1 - Framework modifications - Team 2 - List actual standard screens, list actual tools and send survey to know tools that people need in the GUI (like breadcrumb, better treeview, calendar, etc.) - Team 3 - Create the new GUI design. Define new standardization for screen listed by Team 2. A fourth team could be work on new tools integration, tests and validations. Maybe it's too ambitious and we have to go step by step but I think if we have enough good soul to work on, we can do it ! Let me know your feeling about this. Julien. PS : I can't modify the wiki that contain bootstrap integration definition. Is it possible to have modifications right ? Maybe it's better to create specific wiki page ? Only the wiki https://cwiki.apache.org/confluence/display/OFBIZ/Home is open to contributors The idea is you can always add comments (possibly formatted, they use the same editor) and we can use them to complete the Confluence not open workspaces (members of the OFBiz team monitor changes in Confluence) Jacques Le 14/10/2014 22:52, Jonatan Soto a écrit : Hi all, I made a similar proposition a year ago (see http://markmail.org/message/jc7nfodhtoordqli) but unfortunately I couldn't find the time to work on that. I'm not sure if I'll be able to join on this but I'll try. On the other hand, I seem to remember that there was a branch already created for this ( https://fisheye6.atlassian.com/browse/ofbiz/branches/frontendNewTheme2013-05-10) and a Jira ticket (https://issues.apache.org/jira/browse/OFBIZ-5040). Cheers, On Tue, Oct 14, 2014 at 8:32 AM, Adrian Crum adrian.c...@sandglass-software.com wrote: You can create a branch for this effort. Adrian Crum Sandglass Software www.sandglass-software.com On 10/14/2014 1:44 AM, Nicolas Malin wrote: Hi, The best way will be open a issue and manage by sub task each step. After that dev mailing list is good to sharing. Webconf and jabber are interesting for dynamic and quick exchange but keep in mind to report the talking result on the mailing or issue. It's important for the follow-up :) Nicolas Le 2014-10-13 09:56, Julien NICOLAS a écrit : Hi Taher, I think that we can use the OFBiz wiki to write the action plan and tasks to do, etc. I was thinking about regular webconf and we can be connected via jabber. But maybe ofbiz dev use other collaborative tools ? Any suggestions ? Regards, Julien. Le 13/10/2014 09:48, Taher Alkhateeb a écrit : Hi Nicolas, Great! I'm rubbing hands in excitement. What is the next action now? open a JIRA, have a discussion on mailing list? Furthermore, such a project requires a lot of collaboration. Do we have a platform or a solution for easier collaboration on this project? Regards, Taher Alkhateeb - Original Message - From: Nicolas Malin malin.nico...@librenberry.net To: u...@ofbiz.apache.org Sent: Monday, 13 October, 2014 4:47:05 AM Subject: Re: Theme bootstrap Hi all, I updated the page https://cwiki.apache.org/confluence/display/OFBADMIN/ New+Features+Roadmap+-+Living+Document, Now the best way will be move the discussion on dev and set your battle line on jira ;) Nicolas Le 2014-10-10 15:50, Julien NICOLAS a écrit : Hi Gavin, Pierre, Florient and Taher, It's a good news that you all join the team :) Other thanks to Adrian for informations ! Maybe the first step could be to create a setting which allow to switch from old management to the new one because it seems to be hard to change the framework without breaking old css themes. Another important point is to define a mock-up for the basic navigation and apply it for easiest navigation. This will be helpful to work with the other points. Taher, I think that it's a big task because we can find several types
Re: [DISCUSSION] JIRA issues for web and wiki pages
I believe, the problem is more about people not knowing where to post things, else of course Jira is a perfect fit. Though I (hopefully I'm not alone) normally monitor Confluence (including comments) but https://issues.apache.org/jira/browse/INFRA-8323 Anyway I normally receive all changes by mail. Pierre, do you have something specific in mind about overlooked comments, I mean a list, etc.? Jacques Le 21/10/2014 14:43, Ron Wheeler a écrit : It would be good to have a well organized and supported system for tracking defects of all types including documentation. The JIRA has a very very helpful features that would allow us to identify the importance of problems, any version dependencies, assigned person, etc. Ron On 21/10/2014 7:45 AM, Pierre Smits wrote: Hi all, Currently we only register issues related to the OFBiz code. But we also see a lot of comments in wiki pages regarding corrections. These comments can exists quite a long time and it seems that these are frequently overlooked. Should we not also have a setup in JIRA regarding the web and wiki pages? This helps us to stay aware of bugs and improvements thereof, and help us to track contributors and patches. Having JIRA issues for this seems to be done also in a number of other Apache projects. Regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
JMeter examples
Hi, I know this might look a bit external, but I wonder if we could not provide some simple JMeter load tests OOTB? Jacques
Re: [DISCUSSION] JIRA issues for web and wiki pages
Le 21/10/2014 17:01, Jacques Le Roux a écrit : I believe, the problem is more about people not knowing where to post things, else of course Jira is a perfect fit. Though I (hopefully I'm not alone) normally monitor Confluence (including comments) but https://issues.apache.org/jira/browse/INFRA-8323 Anyway I normally receive all changes by mail. Also please read my comment to Julien about how to handle changes in not open Confluence spaces: http://markmail.org/message/yk2l3d22qenipqwz It's easier for committers than to have to check multi-places :/ Of course when those comments are about issues in code Jiras should be opened Jacques Pierre, do you have something specific in mind about overlooked comments, I mean a list, etc.? Jacques Le 21/10/2014 14:43, Ron Wheeler a écrit : It would be good to have a well organized and supported system for tracking defects of all types including documentation. The JIRA has a very very helpful features that would allow us to identify the importance of problems, any version dependencies, assigned person, etc. Ron On 21/10/2014 7:45 AM, Pierre Smits wrote: Hi all, Currently we only register issues related to the OFBiz code. But we also see a lot of comments in wiki pages regarding corrections. These comments can exists quite a long time and it seems that these are frequently overlooked. Should we not also have a setup in JIRA regarding the web and wiki pages? This helps us to stay aware of bugs and improvements thereof, and help us to track contributors and patches. Having JIRA issues for this seems to be done also in a number of other Apache projects. 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: Theme bootstrap
Le 21/10/2014 16:50, Julien NICOLAS a écrit : Hi Jacques, Le 21/10/2014 11:29, Jacques Le Roux a écrit : Hi Julien, Le 21/10/2014 10:18, Julien NICOLAS a écrit : Hi, I try to find specific theme for the front end in the branch that you told me but I can't find were it can be enable... I didnt' search a lot so maybe it was just closed to my nose and I didn't seen it... ^^ It's there https://svn.apache.org/viewvc/ofbiz/branches/frontendNewTheme2013-05-10/ Yes, I've downloaded this branch as you told me but after building, load demo data and lauching, I still can't see any modifications in the front-end... I never use front-end so maybe I didn't use the good path... (http://localhost:8080/ecommerce/) You are right Julien, I did not check. I created this branch in May 2013 (IIRW at Jonatan's - and others - request) but nothing happened since. SO it's simply trunk the 10th May 2013 :/ Can still be useful if we update it? The creation comment was Following the thread Converting frontend themes to Twitter Bootstrap here is a new branch for that. Actually the thread subject was misleading since we agreed that Twitter Bootstrap is not the only solution. The idea is though to introduce and use a HTML5/CSS framework, Bootstrap, H5Boilerplate and Zurb Foundation will be tried in the process... So I changed the thread subject to Converting frontend themes using HTML5/CSS framework/s. Maybe things have changed since? http://markmail.org/message/i7fnxid55cq5uiiz Jacques
Re: Theme bootstrap
Le 21/10/2014 17:26, Jacques Le Roux a écrit : Le 21/10/2014 16:50, Julien NICOLAS a écrit : Hi Jacques, Le 21/10/2014 11:29, Jacques Le Roux a écrit : Hi Julien, Le 21/10/2014 10:18, Julien NICOLAS a écrit : Hi, I try to find specific theme for the front end in the branch that you told me but I can't find were it can be enable... I didnt' search a lot so maybe it was just closed to my nose and I didn't seen it... ^^ It's there https://svn.apache.org/viewvc/ofbiz/branches/frontendNewTheme2013-05-10/ Yes, I've downloaded this branch as you told me but after building, load demo data and lauching, I still can't see any modifications in the front-end... I never use front-end so maybe I didn't use the good path... (http://localhost:8080/ecommerce/) You are right Julien, I did not check. I created this branch in May 2013 (IIRW at Jonatan's - and others - request) but nothing happened since. SO it's simply trunk the 10th May 2013 :/ Can still be useful if we update it? The creation comment was Following the thread Converting frontend themes to Twitter Bootstrap here is a new branch for that. Actually the thread subject was misleading since we agreed that Twitter Bootstrap is not the only solution. The idea is though to introduce and use a HTML5/CSS framework, Bootstrap, H5Boilerplate and Zurb Foundation will be tried in the process... So I changed the thread subject to Converting frontend themes using HTML5/CSS framework/s. yes, I have the same idea. The problem is not to integrate bootstrap, it's to create tools in the OFBiz framework that allow to use any HTML5/CSS frameworks. I've encountered problems to integrate bootstrap (the first one was the submenu structure) but I'm quite sure that it's the same with other HTML5/CSS frameworks. We have to think on how we can customize div container and class to use several HTML5/CSS frameworks without modifying OFBiz framework. I don't know how to use a specific branch to work with a team (I work daily with the addon manager) but if you can explain how to have commit right... or explain me how to share source code with a specific branch. Thanks, Julien. Maybe things have changed since? http://markmail.org/message/i7fnxid55cq5uiiz Jacques
Re: Theme bootstrap
Hi Julien, I think it might be a bit challenging and early to start creating teams specialized in certain functions this early on. We did not yet define what we're going to do nor do we have a real feel for the size of this job and the best way to split efforts, not to mention that some of the tasks are probably dependent on each other. If I may suggest instead, we need to perhaps go through the tasks themselves and see what needs to be accomplished. To that end, I would focus on the deliverables themselves in the beginning such as: - Identify the major milestones or objectives - Discuss and decide upon the best methodology for implementation of the above objectives - Decide on a collaboration platform (in addition to what exists) if any. - Dive into code directly and just hand off tasks to volunteers who find them interesting / appealing from the team Once we get the project into momentum and you have enough interested and dedicated people then you can put some structure and specialization into it. Now to that end, I would suggest the following major milestones as necessary - Integration of bootstrap and its dependencies to the framework, specifically into the widget system - The utilization of bootstrap into the themes (each theme as a milestone) - Documentation including XSD file definitions, wiki, DocBook stuff etc ... - Standardization of the UI everywhere (perhaps each component as a milestone) What do you think? Taher Alkhateeb On Tue, Oct 21, 2014 at 11:18 AM, Julien NICOLAS julien.nico...@nomaka.fr wrote: Hi, My apologize for answering late, I was deep under the annual balance sheet for my company... Thanks Jonatan for informations. I try to find specific theme for the front end in the branch that you told me but I can't find were it can be enable... I didnt' search a lot so maybe it was just closed to my nose and I didn't seen it... ^^ Anyway I think a lot about the work we have to do and I think it could be interesting to go deeper in the GUI modifications. Including bootstrap framework in OFBiz will be a step but maybe we can go ahead and modify best practices of screen creation. Define a design pattern that developers can follow to create standardized screens. So we can define teams to work simultaneously : - Team 1 - Framework modifications - Team 2 - List actual standard screens, list actual tools and send survey to know tools that people need in the GUI (like breadcrumb, better treeview, calendar, etc.) - Team 3 - Create the new GUI design. Define new standardization for screen listed by Team 2. A fourth team could be work on new tools integration, tests and validations. Maybe it's too ambitious and we have to go step by step but I think if we have enough good soul to work on, we can do it ! Let me know your feeling about this. Julien. PS : I can't modify the wiki that contain bootstrap integration definition. Is it possible to have modifications right ? Maybe it's better to create specific wiki page ? Le 14/10/2014 22:52, Jonatan Soto a écrit : Hi all, I made a similar proposition a year ago (see http://markmail.org/message/jc7nfodhtoordqli) but unfortunately I couldn't find the time to work on that. I'm not sure if I'll be able to join on this but I'll try. On the other hand, I seem to remember that there was a branch already created for this ( https://fisheye6.atlassian.com/browse/ofbiz/branches/ frontendNewTheme2013-05-10) and a Jira ticket (https://issues.apache.org/jira/browse/OFBIZ-5040). Cheers, On Tue, Oct 14, 2014 at 8:32 AM, Adrian Crum adrian.c...@sandglass-software.com wrote: You can create a branch for this effort. Adrian Crum Sandglass Software www.sandglass-software.com On 10/14/2014 1:44 AM, Nicolas Malin wrote: Hi, The best way will be open a issue and manage by sub task each step. After that dev mailing list is good to sharing. Webconf and jabber are interesting for dynamic and quick exchange but keep in mind to report the talking result on the mailing or issue. It's important for the follow-up :) Nicolas Le 2014-10-13 09:56, Julien NICOLAS a écrit : Hi Taher, I think that we can use the OFBiz wiki to write the action plan and tasks to do, etc. I was thinking about regular webconf and we can be connected via jabber. But maybe ofbiz dev use other collaborative tools ? Any suggestions ? Regards, Julien. Le 13/10/2014 09:48, Taher Alkhateeb a écrit : Hi Nicolas, Great! I'm rubbing hands in excitement. What is the next action now? open a JIRA, have a discussion on mailing list? Furthermore, such a project requires a lot of collaboration. Do we have a platform or a solution for easier collaboration on this project? Regards, Taher Alkhateeb - Original Message - From: Nicolas Malin malin.nico...@librenberry.net To: u...@ofbiz.apache.org Sent: Monday, 13 October, 2014 4:47:05 AM Subject: Re: Theme bootstrap Hi all, I
Re: Theme bootstrap
Looks like a very professional approach. Ron On 21/10/2014 12:26 PM, Taher Alkhateeb wrote: Hi Julien, I think it might be a bit challenging and early to start creating teams specialized in certain functions this early on. We did not yet define what we're going to do nor do we have a real feel for the size of this job and the best way to split efforts, not to mention that some of the tasks are probably dependent on each other. If I may suggest instead, we need to perhaps go through the tasks themselves and see what needs to be accomplished. To that end, I would focus on the deliverables themselves in the beginning such as: - Identify the major milestones or objectives - Discuss and decide upon the best methodology for implementation of the above objectives - Decide on a collaboration platform (in addition to what exists) if any. - Dive into code directly and just hand off tasks to volunteers who find them interesting / appealing from the team Once we get the project into momentum and you have enough interested and dedicated people then you can put some structure and specialization into it. Now to that end, I would suggest the following major milestones as necessary - Integration of bootstrap and its dependencies to the framework, specifically into the widget system - The utilization of bootstrap into the themes (each theme as a milestone) - Documentation including XSD file definitions, wiki, DocBook stuff etc ... - Standardization of the UI everywhere (perhaps each component as a milestone) What do you think? Taher Alkhateeb On Tue, Oct 21, 2014 at 11:18 AM, Julien NICOLAS julien.nico...@nomaka.fr wrote: Hi, My apologize for answering late, I was deep under the annual balance sheet for my company... Thanks Jonatan for informations. I try to find specific theme for the front end in the branch that you told me but I can't find were it can be enable... I didnt' search a lot so maybe it was just closed to my nose and I didn't seen it... ^^ Anyway I think a lot about the work we have to do and I think it could be interesting to go deeper in the GUI modifications. Including bootstrap framework in OFBiz will be a step but maybe we can go ahead and modify best practices of screen creation. Define a design pattern that developers can follow to create standardized screens. So we can define teams to work simultaneously : - Team 1 - Framework modifications - Team 2 - List actual standard screens, list actual tools and send survey to know tools that people need in the GUI (like breadcrumb, better treeview, calendar, etc.) - Team 3 - Create the new GUI design. Define new standardization for screen listed by Team 2. A fourth team could be work on new tools integration, tests and validations. Maybe it's too ambitious and we have to go step by step but I think if we have enough good soul to work on, we can do it ! Let me know your feeling about this. Julien. PS : I can't modify the wiki that contain bootstrap integration definition. Is it possible to have modifications right ? Maybe it's better to create specific wiki page ? Le 14/10/2014 22:52, Jonatan Soto a écrit : Hi all, I made a similar proposition a year ago (see http://markmail.org/message/jc7nfodhtoordqli) but unfortunately I couldn't find the time to work on that. I'm not sure if I'll be able to join on this but I'll try. On the other hand, I seem to remember that there was a branch already created for this ( https://fisheye6.atlassian.com/browse/ofbiz/branches/ frontendNewTheme2013-05-10) and a Jira ticket (https://issues.apache.org/jira/browse/OFBIZ-5040). Cheers, On Tue, Oct 14, 2014 at 8:32 AM, Adrian Crum adrian.c...@sandglass-software.com wrote: You can create a branch for this effort. Adrian Crum Sandglass Software www.sandglass-software.com On 10/14/2014 1:44 AM, Nicolas Malin wrote: Hi, The best way will be open a issue and manage by sub task each step. After that dev mailing list is good to sharing. Webconf and jabber are interesting for dynamic and quick exchange but keep in mind to report the talking result on the mailing or issue. It's important for the follow-up :) Nicolas Le 2014-10-13 09:56, Julien NICOLAS a écrit : Hi Taher, I think that we can use the OFBiz wiki to write the action plan and tasks to do, etc. I was thinking about regular webconf and we can be connected via jabber. But maybe ofbiz dev use other collaborative tools ? Any suggestions ? Regards, Julien. Le 13/10/2014 09:48, Taher Alkhateeb a écrit : Hi Nicolas, Great! I'm rubbing hands in excitement. What is the next action now? open a JIRA, have a discussion on mailing list? Furthermore, such a project requires a lot of collaboration. Do we have a platform or a solution for easier collaboration on this project? Regards, Taher Alkhateeb - Original Message - From: Nicolas Malin malin.nico...@librenberry.net To: u...@ofbiz.apache.org Sent: Monday, 13 October, 2014 4:47:05 AM Subject: Re: Theme
Re: JMeter examples
Hi, Our team has build set of JMeter tests for OOTB. They are ASL 2.0 licensed. You can find them on following URL, https://github.com/ofbizecosystem/evolvingofbiz-loadtest Ashish put together lots of documents as blog posts http://www.hotwaxmedia.com/author/ashish/ Feel free to use them as you find suitable. Thanks and Regards Anil Patel COO Hotwax Media Inc http://www.hotwaxmedia.com/ ApacheCon US 2014 Silver Sponsor http://na.apachecon.com/sponsor/our-sponsors On Oct 21, 2014, at 11:08 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi, I know this might look a bit external, but I wonder if we could not provide some simple JMeter load tests OOTB? Jacques
Re: JMeter examples
Jacques, Having some performance benchmarks is a good thing. And if the benchmark shows favourable results it will surely help adoption. Implementing it into a ci environment doing the tests on a regular basis against e.g. demo-stable should be feasible. 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, Oct 21, 2014 at 5:08 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi, I know this might look a bit external, but I wonder if we could not provide some simple JMeter load tests OOTB? Jacques
Re: [DISCUSSION] JIRA issues for web and wiki pages
Jacques, The problem is indeed where to post the issues. There is no solution available to do patches to pages in the website and improvement comments in the restricted spaces are all over the place. And regarding the latter aspect these comments can stay visible for quite some time due to busy schedules (and other interests) of those capable to implement the changes. Having those comments there for a longer time is not good regarding branding and adoption. Having a JIRA setup for the website and restricted spaces will provide the one place and will create insights about what is still open, what is fixed and and when. Plus it helps identifying those committers that could become committers. All in all not a bad suggestion and improvement. 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, Oct 21, 2014 at 5:01 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: I believe, the problem is more about people not knowing where to post things, else of course Jira is a perfect fit. Though I (hopefully I'm not alone) normally monitor Confluence (including comments) but https://issues.apache.org/jira/browse/INFRA-8323 Anyway I normally receive all changes by mail. Pierre, do you have something specific in mind about overlooked comments, I mean a list, etc.? Jacques Le 21/10/2014 14:43, Ron Wheeler a écrit : It would be good to have a well organized and supported system for tracking defects of all types including documentation. The JIRA has a very very helpful features that would allow us to identify the importance of problems, any version dependencies, assigned person, etc. Ron On 21/10/2014 7:45 AM, Pierre Smits wrote: Hi all, Currently we only register issues related to the OFBiz code. But we also see a lot of comments in wiki pages regarding corrections. These comments can exists quite a long time and it seems that these are frequently overlooked. Should we not also have a setup in JIRA regarding the web and wiki pages? This helps us to stay aware of bugs and improvements thereof, and help us to track contributors and patches. Having JIRA issues for this seems to be done also in a number of other Apache projects. 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] [Created] (OFBIZ-5834) Error during remove supplier product
Hoan Dang Van created OFBIZ-5834: Summary: Error during remove supplier product Key: OFBIZ-5834 URL: https://issues.apache.org/jira/browse/OFBIZ-5834 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Trunk Reporter: Hoan Dang Van When i remove supplier of product that has minimumOrderQuantity is greater 0, there was have some error. I detected that when i selected language is the Vietnamese, that error appeared and when i selected language is english , that error didn't occur -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5834) Error during remove supplier product
[ https://issues.apache.org/jira/browse/OFBIZ-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoan Dang Van updated OFBIZ-5834: - Description: When i remove supplier of product that has minimumOrderQuantity is greater 0, there was have some error. I detected that when i selected language is the Vietnamese, that error appeared and when i selected language is english , that error didn't occur Can everyone help me fix this issue? was: When i remove supplier of product that has minimumOrderQuantity is greater 0, there was have some error. I detected that when i selected language is the Vietnamese, that error appeared and when i selected language is english , that error didn't occur Error during remove supplier product Key: OFBIZ-5834 URL: https://issues.apache.org/jira/browse/OFBIZ-5834 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Trunk Reporter: Hoan Dang Van When i remove supplier of product that has minimumOrderQuantity is greater 0, there was have some error. I detected that when i selected language is the Vietnamese, that error appeared and when i selected language is english , that error didn't occur Can everyone help me fix this issue? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5834) Error during remove supplier product
[ https://issues.apache.org/jira/browse/OFBIZ-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoan Dang Van closed OFBIZ-5834. Resolution: Duplicate Sorry for raise this issue. I appeared that it duplicated with https://issues.apache.org/jira/browse/OFBIZ-4769 Error during remove supplier product Key: OFBIZ-5834 URL: https://issues.apache.org/jira/browse/OFBIZ-5834 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Trunk Reporter: Hoan Dang Van When i remove supplier of product that has minimumOrderQuantity is greater 0, there was have some error. I detected that when i selected language is the Vietnamese, that error appeared and when i selected language is english , that error didn't occur Can everyone help me fix this issue? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: UOM of products
Hi Julien Yes, My case is the same as your case. I also read your issue, it is good idea. I want to test it with you. Can you show me the way test it with you Thanks -- View this message in context: http://ofbiz.135035.n4.nabble.com/UOM-of-products-tp4657073p4657219.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
