OFBiz Value Proposition! What is it? And to you? (was Re: Passport Component for OAuth2)

2015-03-23 Thread Pierre Smits
Hi All, Gavin, Starting a new thread. For the build up, see http://ofbiz.markmail.org/message/pf7lnzjwow4g4igj?q=passport+oauth2+order:date-forward Our current homepage states as the value proposition the following: Apache OFBiz™ is an open source product for the automation of enterprise process

Re: [PROPOSAL] Move special purpose/jetty component to OFBiz Attic

2015-03-23 Thread Deepak Dixit
+1 Thanks & Regards — Deepak Dixit > On Mar 23, 2015, at 4:53 PM, Pierre Smits wrote: > > *Rational:* > The special purpose/jetty component has been intended as a specific > variation on the special purpose/appserver component that we decided to > move to OFBiz Attic recently. As this is a spe

[jira] [Updated] (OFBIZ-6204) createProductionRunsForOrder to create OrderItemWorkFulfillment for all mandatory preceeding production runs

2015-03-23 Thread Christian Carlow (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6204: Attachment: OFBIZ-6204.patch This patch passes the orderId and orderItemSeqId to BOMNode.c

[jira] [Created] (OFBIZ-6204) createProductionRunsForOrder to create OrderItemWorkFulfillment for all mandatory preceeding production runs

2015-03-23 Thread Christian Carlow (JIRA)
Christian Carlow created OFBIZ-6204: --- Summary: createProductionRunsForOrder to create OrderItemWorkFulfillment for all mandatory preceeding production runs Key: OFBIZ-6204 URL: https://issues.apache.org/jira/bro

Re: [PROPOSAL] Move special purpose/jetty component to OFBiz Attic

2015-03-23 Thread Nicolas Malin
+1 Le 23/03/2015 12:23, Pierre Smits a écrit : *Rational:* The special purpose/jetty component has been intended as a specific variation on the special purpose/appserver component that we decided to move to OFBiz Attic recently. As this is a specific purpose component that shares the same faith

Re: [PROPOSAL] Move special purpose/jetty component to OFBiz Attic

2015-03-23 Thread Adrian Crum
+1 Adrian Crum Sandglass Software www.sandglass-software.com On 3/23/2015 11:23 AM, Pierre Smits wrote: *Rational:* The special purpose/jetty component has been intended as a specific variation on the special purpose/appserver component that we decided to move to OFBiz Attic recently. As this i

[jira] [Closed] (OFBIZ-6194) bi.properties file is missing licence header

2015-03-23 Thread Pierre Smits (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-6194. --- Fixed in revision: http://svn.apache.org/r1668660 Thanks for the commit Jacopo. > bi.properties file is

[jira] [Commented] (OFBIZ-6194) bi.properties file is missing licence header

2015-03-23 Thread Pierre Smits (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376053#comment-14376053 ] Pierre Smits commented on OFBIZ-6194: - Thanks Jacopo. Will do. > bi.properties file i

[jira] [Updated] (OFBIZ-6193) Have configuration options for bi

2015-03-23 Thread Pierre Smits (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6193: Attachment: OFBIZ-6193-BiOFBizController.patch This patch addresses the inclusion of BISystemPropert

[jira] [Commented] (OFBIZ-6194) bi.properties file is missing licence header

2015-03-23 Thread Jacopo Cappellato (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376016#comment-14376016 ] Jacopo Cappellato commented on OFBIZ-6194: -- Pierre, please close the issue after

[jira] [Assigned] (OFBIZ-6194) bi.properties file is missing licence header

2015-03-23 Thread Jacopo Cappellato (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato reassigned OFBIZ-6194: Assignee: Pierre Smits (was: Jacopo Cappellato) > bi.properties file is missing li

[jira] [Assigned] (OFBIZ-6194) bi.properties file is missing licence header

2015-03-23 Thread Jacopo Cappellato (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato reassigned OFBIZ-6194: Assignee: Jacopo Cappellato (was: Pierre Smits) > bi.properties file is missing li

Re: [PROPOSAL] Move special purpose/jetty component to OFBiz Attic

2015-03-23 Thread Gil portenseigne
+1 Gil On 23/03/2015 12:23, Pierre Smits wrote: *Rational:* The special purpose/jetty component has been intended as a specific variation on the special purpose/appserver component that we decided to move to OFBiz Attic recently. As this is a specific purpose component that shares the same fait

Re: Release Strategy and Branch Support

2015-03-23 Thread Pierre Smits
No, such is not needed. Through consensus regarding code change the project implicitly state what is in releases. Releases are supported. Of course, each contributor can decide for himself what he wants to support. An individual contributor is not the community, hence not the project. Best regard

Re: Release Strategy and Branch Support

2015-03-23 Thread Jacopo Cappellato
The community as a whole supports OFBiz and its releases. Jacopo On Mar 23, 2015, at 3:38 PM, Ron Wheeler wrote: > Doe this have an impact on how the OFBiz project defines "supported release". > - We support a release but only the parts that we care about! > > Each contributor gets to decide

Re: Release Strategy and Branch Support

2015-03-23 Thread Ron Wheeler
Doe this have an impact on how the OFBiz project defines "supported release". - We support a release but only the parts that we care about! Each contributor gets to decide what release they support. Do we need to publish a list of committers for each release or is it by module or feature? Ron

Re: [PROPOSAL] Move special purpose/jetty component to OFBiz Attic

2015-03-23 Thread Michael Brohl
+1 Michael Brohl www.ecomify.de Am 23.03.15 um 12:23 schrieb Pierre Smits: *Rational:* The special purpose/jetty component has been intended as a specific variation on the special purpose/appserver component that we decided to move to OFBiz Attic recently. As this is a specific purpose componen

Re: [PROPOSAL] Move special purpose/jetty component to OFBiz Attic

2015-03-23 Thread Jacques Le Roux
+1 Jacques Le 23/03/2015 12:23, Pierre Smits a écrit : *Rational:* The special purpose/jetty component has been intended as a specific variation on the special purpose/appserver component that we decided to move to OFBiz Attic recently. As this is a specific purpose component that shares the sa

[PROPOSAL] Move special purpose/jetty component to OFBiz Attic

2015-03-23 Thread Pierre Smits
*Rational:* The special purpose/jetty component has been intended as a specific variation on the special purpose/appserver component that we decided to move to OFBiz Attic recently. As this is a specific purpose component that shares the same faith as appserver (with respect to working with current

Re: Release Strategy and Branch Support

2015-03-23 Thread Pierre Smits
A simple statement as 'it applies to rX.Y too' or changing the applicable version of the JIRA is be considered as such. But of course, that may always be verified. Best regards, Pierre Smits *ORRTIZ.COM * Services & Solutions for Cloud- Based Manufacturing, Professional Se

Re: Release Strategy and Branch Support

2015-03-23 Thread Jacopo Cappellato
+1 Especially if the patch is for a bug that has been already committed to the trunk and the contributor has prepared it for a specific branch and properly tested it. Jacopo On Mar 23, 2015, at 9:59 AM, Pierre Smits wrote: > As soon as a bug fix ticket pertaining to a specific release branc

Re: Release Strategy and Branch Support

2015-03-23 Thread Pierre Smits
As soon as a bug fix ticket pertaining to a specific release branch is created in JIRA, the community should put its best effort in to get it resolved. When a that ticket has a patch, the committers should treat it with a higher priority. That doesn't mean that the project is obliged to have it i

Re: Release Strategy and Branch Support

2015-03-23 Thread Jacopo Cappellato
I don't see a specific problem here; I mean, this is a community driven project and all tasks will need a contribution from the community in order to be implemented, including backports. If something is not backported to release X.Y and someone is interested in it then the person could implement

[jira] [Commented] (OFBIZ-6203) Create/update addresses with special characters from front-end, like :- ä

2015-03-23 Thread Paramjit Saini (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375504#comment-14375504 ] Paramjit Saini commented on OFBIZ-6203: --- Hi Jacques, Yes, i have checked "https://i

Re: Release Strategy and Branch Support

2015-03-23 Thread Jacques Le Roux
Ha just a small change I wrote that we should state in download page that *not all bug fixes are backported to all living release branches* Should be *despite our best effort, not all bug fixes are backported to all living release branches* ;) Jacques Le 22/03/2015 14:49, Ron Wheeler a écrit :

[jira] [Closed] (OFBIZ-6203) Create/update addresses with special characters from front-end, like :- ä

2015-03-23 Thread Jacques Le Roux (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6203. -- Resolution: Duplicate Thanks for report Paramjit, I believe it's a duplicate of OFBIZ-5929. SO I