[jira] [Commented] (OFBIZ-6271) build management with maven
[ https://issues.apache.org/jira/browse/OFBIZ-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524204#comment-14524204 ] Adam Heath commented on OFBIZ-6271: --- Ok, quick update. Building a single component is not possible, by going into applications/product, and doing a "mvn clean compile". However, there is a maven way to do it: == mvn -pl org.apache.ofbiz:ofbiz-product compile == Doing this from the top-level will then deal with just the "list" of artifacts(you can give several). Also, you can use "-am" which will also run the goals against everything the project list *depends* on, which is actually way cool. == mvn -am -pl org.apache.ofbiz:ofbiz-product clean package == The above command will not only deal with product, but base, entity, security, service, common, content, party, webapp. Note, that widget and entityext(and others) are not included. > build management with maven > --- > > Key: OFBIZ-6271 > URL: https://issues.apache.org/jira/browse/OFBIZ-6271 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Reporter: Adam Heath >Priority: Minor > Attachments: console.log > > > This is a new build system; the primary goal will be to not require any > changes to existing ofbiz layouts(for backwards compatibility, at least > initially). > These pom.xml files are completely new; the existing build.xml infrastructure > will continue to exist. The existing build.xml will never call into > maven(which is what processes the pom.xml), and maven will never call into > build.xml either. > I have already committed a working pom.xml for the top level, and > framework/start. Shortly, I will be adding framework/base and > framework/entity, but into this branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6323) LookupProductAndPrice ajaxLookup should only return DEFAULT_PRICE rather than all the price types
[ https://issues.apache.org/jira/browse/OFBIZ-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Rae updated OFBIZ-6323: --- Attachment: OFBIZ-6323.patch > LookupProductAndPrice ajaxLookup should only return DEFAULT_PRICE rather than > all the price types > - > > Key: OFBIZ-6323 > URL: https://issues.apache.org/jira/browse/OFBIZ-6323 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > 14.12.01 >Reporter: Forrest Rae > Attachments: OFBIZ-6323.patch > > > The LookUpProductPrice ajaxLookup leverages the same LookupDecorator screen > that is used for more advanced product queries. The results of the request > display all the different price types configured for a product This is > confusing for the user when adding an item to a quote. The attached patch > adds additional conditionalFields to the search criteria. > I've searched the code base for areas where this change might adversely > affect usability and didn't see any cases of that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6323) LookupProductAndPrice ajaxLookup should only return DEFAULT_PRICE rather than all the price types
Forrest Rae created OFBIZ-6323: -- Summary: LookupProductAndPrice ajaxLookup should only return DEFAULT_PRICE rather than all the price types Key: OFBIZ-6323 URL: https://issues.apache.org/jira/browse/OFBIZ-6323 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Trunk, Release Branch 14.12, Release Branch 13.07, 14.12.01 Reporter: Forrest Rae The LookUpProductPrice ajaxLookup leverages the same LookupDecorator screen that is used for more advanced product queries. The results of the request display all the different price types configured for a product This is confusing for the user when adding an item to a quote. The attached patch adds additional conditionalFields to the search criteria. I've searched the code base for areas where this change might adversely affect usability and didn't see any cases of that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6305) German translations for various applications
[ https://issues.apache.org/jira/browse/OFBIZ-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Geisert reassigned OFBIZ-6305: Assignee: Christian Geisert > German translations for various applications > > > Key: OFBIZ-6305 > URL: https://issues.apache.org/jira/browse/OFBIZ-6305 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Upcoming Branch >Reporter: Martin Becker >Assignee: Christian Geisert > Attachments: OFBIZ-6305-ProductUiLabels.patch > > > We would like to contribute missing german translations for the OFBiz > applications based on the current trunk. There will arrive patches for this > per application within this ticket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6233) When skip-start is used the focus-field-name feature does not work correctly
[ https://issues.apache.org/jira/browse/OFBIZ-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6233: --- Issue Type: Sub-task (was: Bug) Parent: OFBIZ-6321 > When skip-start is used the focus-field-name feature does not work correctly > > > Key: OFBIZ-6233 > URL: https://issues.apache.org/jira/browse/OFBIZ-6233 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Jacques Le Roux >Priority: Minor > Labels: focus-field-name, skip-start > > I have a widget-form composed of 4 parts (forms) with skip-end in the 1st > form, skip-start and skip-end used in both meddle parts (2nd and 3rd) and > skip-start in last one. I did not find a way to have the focus-field-name > working on the 1st part. I had also to put something into focus-field-name > for the last part else got non blocking js errors related to > parentModel.focusFieldName. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6233) When skip-start is used the focus-field-name feature does not work correctly
[ https://issues.apache.org/jira/browse/OFBIZ-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523314#comment-14523314 ] Jacques Le Roux commented on OFBIZ-6233: This definitively does not work, moreover you need to add a dummy focus-field-name to the last form to prevent a js error related to parentModel.focusFieldName > When skip-start is used the focus-field-name feature does not work correctly > > > Key: OFBIZ-6233 > URL: https://issues.apache.org/jira/browse/OFBIZ-6233 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Jacques Le Roux >Priority: Minor > Labels: focus-field-name, skip-start > > I have a widget-form composed of 4 parts (forms) with skip-end in the 1st > form, skip-start and skip-end used in both meddle parts (2nd and 3rd) and > skip-start in last one. I did not find a way to have the focus-field-name > working on the 1st part. I had also to put something into focus-field-name > for the last part else got non blocking js errors related to > parentModel.focusFieldName. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Photo or Avatar for Committers and PMC Members List
Done Jacques Le 01/05/2015 14:16, Michael Brohl a écrit : +1 Am 01.05.2015 um 12:40 schrieb Jacques Le Roux : I had a better idea. Since we have now a strict Confluence policy for spam and only contributors are allowed to modify the wiki, I propose we move this page, and all others ASAP, to the wiki. Then contributors will be able to complete this page themselves and contribute to other pages as well. Sharing more will empower the community :) Jacques Le 01/05/2015 08:54, Jacques Le Roux a écrit : Done Jacques Le 01/05/2015 08:19, Jacques Le Roux a écrit : Ha indeed forgot all is blocked there. Good idea Michael, I will do so :) Jacques Le 30/04/2015 22:54, Michael Brohl a écrit : Hi Jacques, seems I cannot edit and post comments on the Wiki page :-/ I don't want to pollute this ML with this minor thread so maybe you can check this and add a short how-to at the contributors page for adding images (or links to images) to the page? Not an urgent task though... Thanks and a happy 1st May / Fête du Travail, Michael Brohl ecomify GmbH www.ecomify.de Am 30.04.15 um 18:29 schrieb Jacques Le Roux: Hi Michael, I think the better way is to give a link to an image, when can then use it directly. Post it as a comment and we will add it. We have a plan to merge all OFBiz Confluence workspaces in the one accessible by contributors (aka wiki) but it's not done yet, nor even planned :/ Thanks Jacques
[jira] [Created] (OFBIZ-6322) Widget form: renderFormClose not called when skip-start or skip-end is used
Jacques Le Roux created OFBIZ-6322: -- Summary: Widget form: renderFormClose not called when skip-start or skip-end is used Key: OFBIZ-6322 URL: https://issues.apache.org/jira/browse/OFBIZ-6322 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Priority: Minor Fix For: Upcoming Branch renderFormClose is not called when skip-start or skip-end is used, hence jsvalidate is not present -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6139) Lookup fields break when used with a form having skip-start="true"
[ https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6139: --- Issue Type: Sub-task (was: Bug) Parent: OFBIZ-6321 > Lookup fields break when used with a form having skip-start="true" > -- > > Key: OFBIZ-6139 > URL: https://issues.apache.org/jira/browse/OFBIZ-6139 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Labels: lookup > Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch > > > We neglected this aspect so far, adding a "form-name" attribute to the lookup > element fixes it. You then need also to set the correct id-name value on > field element. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-2282) Form Widget: skip-start breaks date-time
[ https://issues.apache.org/jira/browse/OFBIZ-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-2282: --- Issue Type: Sub-task (was: Bug) Parent: OFBIZ-6321 > Form Widget: skip-start breaks date-time > > > Key: OFBIZ-2282 > URL: https://issues.apache.org/jira/browse/OFBIZ-2282 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Chris Howe >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 14.12.01, Upcoming Branch > > > When a from widget has the attribute of skip-start="true", the javascript > creation references the incorrect DOM object. > ie > > > > will result in the creation of the following > javascript call: javascript:call_cal(document.middleForm.date,''); should > instead be: > javascript call: javascript:call_cal(document.beginForm.date,''); > or even better the super form name should be a variable. > The second option would require an additional attribute in the form > definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-3920) HtmlFormRenderer : with attribute skip-start, lookup fields are broken
[ https://issues.apache.org/jira/browse/OFBIZ-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-3920: --- Issue Type: Sub-task (was: Bug) Parent: OFBIZ-6321 > HtmlFormRenderer : with attribute skip-start, lookup fields are broken > -- > > Key: OFBIZ-3920 > URL: https://issues.apache.org/jira/browse/OFBIZ-3920 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch > > Attachments: skipStartWithLookup.patch > > > When you want to merge to form and use skip-start="true" on the second form, > all contained lookup are broken. In this case, the javascript used to call > Lookup screen are using the form name eg : ' href="javascript:call_fieldlookupLayer( document.form2.lookupfield, 'Tagert', > ...)', but with skip-start, the form name isn't present. > A possible solution is to force lookup field id, but it's not managed on > htmlFormMacroLibrary.ftl. I will submit a patch to make this possible. > I don't manage problem on descriptionField, this would need to change > ModelFormRender and it's a little bit more complicated ;) > Nicolas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6256) Anonymous account creation doesn't work anymore
[
https://issues.apache.org/jira/browse/OFBIZ-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523278#comment-14523278
]
Taher Alkhateeb commented on OFBIZ-6256:
Hi,
I just tried to create a customer on demo and it works.
> Anonymous account creation doesn't work anymore
> ---
>
> Key: OFBIZ-6256
> URL: https://issues.apache.org/jira/browse/OFBIZ-6256
> Project: OFBiz
> Issue Type: Bug
> Components: specialpurpose/ecommerce
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Priority: Blocker
> Labels: registration
>
> When registering a new account for ecommerce (as an anonymous user) the
> process doesn't run to succes in
> http://demo-trunk-ofbiz.apache.org/ecommerce/control/createcustomer, but
> results in:
> {code}
> ERROR: Could not complete the Create Customer
> [file:/home/ofbizDemo/trunk/specialpurpose/ecommerce/script/org/ofbiz/ecommerce/customer/CustomerEvents.xml#createCustomer]
> process [problem invoking the [createPartyRole] service with the map named
> [partyRoleContext] containing [{roleTypeId=CUSTOMER, partyId=10002,
> locale=en_US, userLogin=[GenericEntity:UserLogin][createdStamp,2015-04-16
> 19:25:33.325(java.sql.Timestamp)][createdTxStamp,2015-04-16
> 19:25:33.229(java.sql.Timestamp)][currentPassword,$SHA$bY.7$RUKs-4-SsK3eNQOrTh8EoyEXnJI(java.lang.String)][disabledDateTime,null()][enabled,null()][externalAuthId,null()][hasLoggedOut,null()][isSystem,null()][lastCurrencyUom,null()][lastLocale,null()][lastTimeZone,null()][lastUpdatedStamp,2015-04-16
> 19:25:33.325(java.sql.Timestamp)][lastUpdatedTxStamp,2015-04-16
> 19:25:33.229(java.sql.Timestamp)][partyId,10002(java.lang.String)][passwordHint,null()][requirePasswordChange,null()][successiveFailedLogins,null()][userLdapDn,null()][userLoginId,tester(java.lang.String)]}]:
> You must be logged in to complete the [Party role permission logic] process.]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6233) When skip-start is used the focus-field-name feature does not work correctly
[ https://issues.apache.org/jira/browse/OFBIZ-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523279#comment-14523279 ] Jacques Le Roux commented on OFBIZ-6233: I wonder if this is really related with skip-start, could be related to js I use in the same form, I will try that... > When skip-start is used the focus-field-name feature does not work correctly > > > Key: OFBIZ-6233 > URL: https://issues.apache.org/jira/browse/OFBIZ-6233 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Jacques Le Roux >Priority: Minor > Labels: focus-field-name, skip-start > > I have a widget-form composed of 4 parts (forms) with skip-end in the 1st > form, skip-start and skip-end used in both meddle parts (2nd and 3rd) and > skip-start in last one. I did not find a way to have the focus-field-name > working on the 1st part. I had also to put something into focus-field-name > for the last part else got non blocking js errors related to > parentModel.focusFieldName. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6170) You can't rely on Lookup field description-field-name attribute in a form having skip-start="true"
[ https://issues.apache.org/jira/browse/OFBIZ-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6170: --- Issue Type: Sub-task (was: Bug) Parent: OFBIZ-6321 > You can't rely on Lookup field description-field-name attribute in a form > having skip-start="true" > -- > > Key: OFBIZ-6170 > URL: https://issues.apache.org/jira/browse/OFBIZ-6170 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch > > > We neglected this aspect so far, I spent some time on it today and I must say > the solution is really not obvious. I wrote most parts of that on the js > side, so I will try to have a new look. Maybe a small change in the model > will be needed; like I did for OFBIZ-6139 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6321) Widget form skip-start umbrella issue
Jacques Le Roux created OFBIZ-6321: -- Summary: Widget form skip-start umbrella issue Key: OFBIZ-6321 URL: https://issues.apache.org/jira/browse/OFBIZ-6321 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Priority: Minor Fix For: Upcoming Branch This is an umbrella issue to gather all related Widget form skip-start issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6217) fix warnings in trunk on java source code
[ https://issues.apache.org/jira/browse/OFBIZ-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taher Alkhateeb closed OFBIZ-6217. -- Resolution: Implemented partially implemented > fix warnings in trunk on java source code > - > > Key: OFBIZ-6217 > URL: https://issues.apache.org/jira/browse/OFBIZ-6217 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Taher Alkhateeb >Assignee: Adrian Crum >Priority: Minor > Labels: java, warning > Fix For: Upcoming Branch > > Attachments: OFBIZ-6217-patch-4.patch, remove_unused_imports.patch, > warnings_patch_2.patch, warnings_patch_2.patch > > > Right now, we have 528 warnings on trunk out of which 238 are about raw types > and 118 never used imports. So we can already eliminate most of the warning > quite quickly. > I will issue multiple patches to resolve most of these warnings. It might be > a bit of a challenge to eliminate the raw types because the generics are not > always deducable from the code especially when relying on external APIs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6217) fix warnings in trunk on java source code
[ https://issues.apache.org/jira/browse/OFBIZ-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523220#comment-14523220 ] Taher Alkhateeb commented on OFBIZ-6217: Okay. Closing this issue then. > fix warnings in trunk on java source code > - > > Key: OFBIZ-6217 > URL: https://issues.apache.org/jira/browse/OFBIZ-6217 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Taher Alkhateeb >Assignee: Adrian Crum >Priority: Minor > Labels: java, warning > Fix For: Upcoming Branch > > Attachments: OFBIZ-6217-patch-4.patch, remove_unused_imports.patch, > warnings_patch_2.patch, warnings_patch_2.patch > > > Right now, we have 528 warnings on trunk out of which 238 are about raw types > and 118 never used imports. So we can already eliminate most of the warning > quite quickly. > I will issue multiple patches to resolve most of these warnings. It might be > a bit of a challenge to eliminate the raw types because the generics are not > always deducable from the code especially when relying on external APIs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
buildbot success in ASF Buildbot on ofbiz-trunk
The Buildbot has detected a restored build on builder ofbiz-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-trunk/builds/859 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' triggered this build Build Source Stamp: [branch ofbiz/trunk] 1677123 Blamelist: jleroux Build succeeded! Sincerely, -The Buildbot
buildbot exception in ASF Buildbot on ofbiz-branch14
The Buildbot has detected a build exception on builder ofbiz-branch14 while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-branch14/builds/110 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz14-commit' triggered this build Build Source Stamp: [branch ofbiz/branches/release14.12] 1677124 Blamelist: jleroux BUILD FAILED: exception upload_1 Sincerely, -The Buildbot
Re: Photo or Avatar for Committers and PMC Members List
+1 > Am 01.05.2015 um 12:40 schrieb Jacques Le Roux : > > I had a better idea. Since we have now a strict Confluence policy for spam > and only contributors are allowed to modify the wiki, I propose we move > this page, and all others ASAP, to the wiki. Then contributors will be able > to complete this page themselves and contribute to other pages as well. > Sharing more will empower the community :) > > Jacques > > Le 01/05/2015 08:54, Jacques Le Roux a écrit : >> Done >> >> Jacques >> >> Le 01/05/2015 08:19, Jacques Le Roux a écrit : >>> Ha indeed forgot all is blocked there. Good idea Michael, I will do so :) >>> >>> Jacques >>> >>> Le 30/04/2015 22:54, Michael Brohl a écrit : Hi Jacques, seems I cannot edit and post comments on the Wiki page :-/ I don't want to pollute this ML with this minor thread so maybe you can check this and add a short how-to at the contributors page for adding images (or links to images) to the page? Not an urgent task though... Thanks and a happy 1st May / Fête du Travail, Michael Brohl ecomify GmbH www.ecomify.de > Am 30.04.15 um 18:29 schrieb Jacques Le Roux: > Hi Michael, > > I think the better way is to give a link to an image, when can then use > it directly. Post it as a comment and we will add it. We have a plan to > merge all OFBiz Confluence workspaces in the one accessible by > contributors (aka wiki) but it's not done yet, nor even planned :/ > > Thanks > > Jacques >> smime.p7s Description: S/MIME cryptographic signature
[jira] [Commented] (OFBIZ-6120) Allow FOP to support for -Dportoffset
[ https://issues.apache.org/jira/browse/OFBIZ-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523126#comment-14523126 ] Jacques Le Roux commented on OFBIZ-6120: Thanks to Deepak's report, I fixed the way the FOP baseUrl was set in trunk r1677123 R14.12 r1677124 R13.07 r1677125 > Allow FOP to support for -Dportoffset > > > Key: OFBIZ-6120 > URL: https://issues.apache.org/jira/browse/OFBIZ-6120 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Christian Carlow >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: 14.12.01, 13.07.02, Upcoming Branch > > Attachments: OFBIZ-6120.patch > > > FOP images do not appear when portoffset used: > 2015-02-28 18:12:12,249 |http-bio-8445-exec-4 |ApacheFopWorker > |I| FOP FontBaseURL: file:/home/anon/workspace/ofbiz/framework/webapp/config/ > 2015-02-28 18:12:12,254 |http-bio-8445-exec-4 |FOP > |D| target-resolution set to: 72.0dpi (px2mm=0.3528) > 2015-02-28 18:12:12,593 |http-bio-8445-exec-4 |FOP > |E| Error with opening URL > 'http://localhost:8080/content/control/stream?contentId=10004': Connection > refused > 2015-02-28 18:12:12,616 |http-bio-8445-exec-4 |FOUserAgent > |E| Image not found. URI: /content/control/stream?contentId=10004. (See > position 40:158) > 2015-02-28 18:12:12,715 |http-bio-8445-exec-4 |FOUserAgent > |W| Font "NotoSans,normal,700" not found. Substituting with > "NotoSans,normal,400". > 2015-02-28 18:12:12,957 |http-bio-8445-exec-4 |FOUserAgent > |W| Line 1 of a paragraph overflows the available area by 567 millipoints. > (See position 270:61) > 2015-02-28 18:12:13,001 |http-bio-8445-exec-4 |FOUserAgent > |W| Content overflows the viewport of the fo:region-before on page 1 in > block-progression direction by 19200 millipoints. (See position 30:58) > 2015-02-28 18:12:13,026 |http-bio-8445-exec-4 |FOUserAgent > |E| Image not found. URI: /content/control/stream?contentId=10004. (No > context info available) > 2015-02-28 18:12:13,104 |http-bio-8445-exec-4 |ServerHitBin > |I| Visit delegatorName=default, ServerHitBin delegatorName=default -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Photo or Avatar for Committers and PMC Members List
+1 On May 1, 2015, at 12:40 PM, Jacques Le Roux wrote: > I had a better idea. Since we have now a strict Confluence policy for spam > and only contributors are allowed to modify the wiki, I propose we move this > page, and all others ASAP, to the wiki. Then contributors will be able to > complete this page themselves and contribute to other pages as well. Sharing > more will empower the community :) > > Jacques > > Le 01/05/2015 08:54, Jacques Le Roux a écrit : >> Done >> >> Jacques >> >> Le 01/05/2015 08:19, Jacques Le Roux a écrit : >>> Ha indeed forgot all is blocked there. Good idea Michael, I will do so :) >>> >>> Jacques >>> >>> Le 30/04/2015 22:54, Michael Brohl a écrit : Hi Jacques, seems I cannot edit and post comments on the Wiki page :-/ I don't want to pollute this ML with this minor thread so maybe you can check this and add a short how-to at the contributors page for adding images (or links to images) to the page? Not an urgent task though... Thanks and a happy 1st May / Fête du Travail, Michael Brohl ecomify GmbH www.ecomify.de Am 30.04.15 um 18:29 schrieb Jacques Le Roux: > Hi Michael, > > I think the better way is to give a link to an image, when can then use > it directly. Post it as a comment and we will add it. We have a plan to > merge all OFBiz Confluence workspaces in the one accessible by > contributors (aka wiki) but it's not done yet, nor even planned :/ > > Thanks > > Jacques > >>> >>
Re: Photo or Avatar for Committers and PMC Members List
Thanks, Jacques! Regards, Michael > Am 01.05.2015 um 08:54 schrieb Jacques Le Roux : > > Done > > Jacques > > Le 01/05/2015 08:19, Jacques Le Roux a écrit : >> Ha indeed forgot all is blocked there. Good idea Michael, I will do so :) >> >> Jacques >> >> Le 30/04/2015 22:54, Michael Brohl a écrit : >>> Hi Jacques, >>> >>> seems I cannot edit and post comments on the Wiki page :-/ >>> >>> I don't want to pollute this ML with this minor thread so maybe you can >>> check this and add a short how-to at the contributors page for adding >>> images (or links to images) to the page? Not an urgent task though... >>> >>> Thanks and a happy 1st May / Fête du Travail, >>> >>> Michael Brohl >>> ecomify GmbH >>> www.ecomify.de >>> Am 30.04.15 um 18:29 schrieb Jacques Le Roux: Hi Michael, I think the better way is to give a link to an image, when can then use it directly. Post it as a comment and we will add it. We have a plan to merge all OFBiz Confluence workspaces in the one accessible by contributors (aka wiki) but it's not done yet, nor even planned :/ Thanks Jacques >> smime.p7s Description: S/MIME cryptographic signature
Re: Photo or Avatar for Committers and PMC Members List
I had a better idea. Since we have now a strict Confluence policy for spam and only contributors are allowed to modify the wiki, I propose we move this page, and all others ASAP, to the wiki. Then contributors will be able to complete this page themselves and contribute to other pages as well. Sharing more will empower the community :) Jacques Le 01/05/2015 08:54, Jacques Le Roux a écrit : Done Jacques Le 01/05/2015 08:19, Jacques Le Roux a écrit : Ha indeed forgot all is blocked there. Good idea Michael, I will do so :) Jacques Le 30/04/2015 22:54, Michael Brohl a écrit : Hi Jacques, seems I cannot edit and post comments on the Wiki page :-/ I don't want to pollute this ML with this minor thread so maybe you can check this and add a short how-to at the contributors page for adding images (or links to images) to the page? Not an urgent task though... Thanks and a happy 1st May / Fête du Travail, Michael Brohl ecomify GmbH www.ecomify.de Am 30.04.15 um 18:29 schrieb Jacques Le Roux: Hi Michael, I think the better way is to give a link to an image, when can then use it directly. Post it as a comment and we will add it. We have a plan to merge all OFBiz Confluence workspaces in the one accessible by contributors (aka wiki) but it's not done yet, nor even planned :/ Thanks Jacques
FYI: Git 2.4 released
Forward from Twitter: Git 2.4 Released: atomic pushes, push to deploy, and other useful features https://t.co/ADfKUw9hAF -- Michael www.ecomify.de smime.p7s Description: S/MIME cryptographic signature
Re: Photo or Avatar for Committers and PMC Members List
Done Jacques Le 01/05/2015 08:19, Jacques Le Roux a écrit : Ha indeed forgot all is blocked there. Good idea Michael, I will do so :) Jacques Le 30/04/2015 22:54, Michael Brohl a écrit : Hi Jacques, seems I cannot edit and post comments on the Wiki page :-/ I don't want to pollute this ML with this minor thread so maybe you can check this and add a short how-to at the contributors page for adding images (or links to images) to the page? Not an urgent task though... Thanks and a happy 1st May / Fête du Travail, Michael Brohl ecomify GmbH www.ecomify.de Am 30.04.15 um 18:29 schrieb Jacques Le Roux: Hi Michael, I think the better way is to give a link to an image, when can then use it directly. Post it as a comment and we will add it. We have a plan to merge all OFBiz Confluence workspaces in the one accessible by contributors (aka wiki) but it's not done yet, nor even planned :/ Thanks Jacques
Re: VOTE RESULT: Begin Replacing OFBiz Framework With Moqui
At least Adrian brought this on the table and it was worth beginning to discuss :) We know now that nobody would do it w/o a PoC Jacques Le 01/05/2015 08:10, Jacopo Cappellato a écrit : On Apr 30, 2015, at 11:12 PM, David E. Jones wrote: This doesn’t seem to represent the responses very well. My vote shouldn’t be considered a +1 unless my interpretation of the proposal (as a PoC in a branch) was correct, and I saw no comment on that… in fact from this message it seems that is explicitly NOT what the vote was supposed to be about based on the comment that doing a PoC in a branch requires no vote. I had the same thought: for example, I didn't understand why David's and my vote have been classified as +1 and -1 respectively when I have clearly mentioned: "+1 to this proposal by David". Jacopo Overall the vote proposal and discussion thread was very confusing, I don’t see how you could get any sort of vote count out of it… most people replied with multiple votes with different clarifications! This VOTE RESULT never should have been done, the vote should simply have been cancelled or reframed. -David On 30 Apr 2015, at 00:55, Adrian Crum wrote: Here is the tally of the votes. This was a challenge because many replies included votes for other things, so this tally represents my best effort at counting votes for the original subject. PMC Members (Binding) - +0 | 2 (Adam Heath, Jacques Le Roux) +1 | 1 (David Jones) -1 | 3 (Nicolas Malin, Scott Gray, Jacopo Cappellato) Others (non-Binding) +0 | 1 (Adrian Crum) -1 | 2 (Ron Wheeler, Martin Becker) The vote failed to pass with 3 -1 votes and 1 +1 vote. The replies included a discussion about creating a POC branch to explore the subject further. That can be done without a vote, so I will consider this vote closed. Adrian Crum Sandglass Software www.sandglass-software.com On 4/26/2015 3:44 PM, Adrian Crum wrote: As was discussed last week, there is some interest in replacing some (or all) of OFBiz with Moqui (http://www.moqui.org/framework/index.html). To the scope reasonable, I propose that we begin by converting the following parts of the OFBiz framework with Moqui: Entity Engine Service Engine Security Other parts of the OFBiz framework could be converted as well, but I think this would be a good starting point, and if is successful, then more of OFBiz can be converted later. I believe we can create a thunk component to help solve compatibility problems, but that is a separate discussion. I only mention it here in case compatibility concerns might influence a vote.
