[jira] Jacques Le Roux shared "INFRA-20439: Allow the OFBiz commiters to see Github Dependabot alerts" with you
Jacques Le Roux shared an issue with you - FYI > Allow the OFBiz commiters to see Github Dependabot alerts > - > > Key: INFRA-20439 > URL: https://issues.apache.org/jira/browse/INFRA-20439 > Project: Infrastructure > Issue Type: Improvement > Components: Github >Reporter: Jacques Le Roux >Priority: Major > > Following this message > https://lists.apache.org/thread.html/rf2ee82a79a2cfa552280428f497bc13bb5cdb3abd92eb65445a17dc4%40%3Cusers.infra.apache.org%3E > we would like to be able to see the content of Github Dependabot alerts. > Please let us know if you need more information, like the list of committers. > But I guess it's OK because this list will evolve so I guess you use a > substitute name for that > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-7957) RateAmount is not found when the level is 'WorkEffort'
Montalbano Florian created OFBIZ-7957:
-
Summary: RateAmount is not found when the level is 'WorkEffort'
Key: OFBIZ-7957
URL: https://issues.apache.org/jira/browse/OFBIZ-7957
Project: OFBiz
Issue Type: Bug
Components: accounting
Affects Versions: Trunk
Reporter: Montalbano Florian
When you create a RateAmount, you can determine for which WorkEffort it should
apply. But when this RateAmount is retrieved for a specific WorkEffort, it
fails to find the good RateAmount.
The problem comes from the check done to retrieve the RateAmount at a
WorkEffort level. This is the used check :
{code}
{code}
In this 'entity-and', the partyId is set as a constraint. But it is possible to
enable a special RateAmount only for a WorkEffort without regarding the partyId.
I think we have 2 options here :
- Remove the partyId constraint but then the retrieving may be less accurate
- Make the retrieving more accurate by checking first the WorkEffort, then from
the retrieved list, check if the partyId matches and finally from this second
retrieval, check if the emplPositionTypeId match. At the end, we would have the
most accurate RateAmount.
What do you think of it ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421762#comment-15421762 ] Jacques Le Roux edited comment on OFBIZ-6184 at 8/16/16 1:27 PM: - I'm not strictly against it, it seems to me that ar and ap should be used rather than accounting. But I still not clearly see what this variable is bringing. It's set in main-decoratorS and skipped by createFieldNamesToSkip.createFieldNamesToSkip(), so what? Do I miss something? was (Author: jacques.le.roux): I'm not strictly against it, it seems to me that ar and ap should be used rather than accounting. But I still not clearly see that this variable is bringing. It's set in main-decoratorS and skipped by createFieldNamesToSkip.createFieldNamesToSkip(), so what? Do I miss something? > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-7910. -- Resolution: Implemented Fix Version/s: Upcoming Branch Thanks Taher, Pierre, Wai, Taher your patch is in trunk at revision: 1756515 I simply "svn:ignored" the libs folder since only specific users libs will get there > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: ADD_LIB.patch, OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421762#comment-15421762 ] Jacques Le Roux commented on OFBIZ-6184: I'm not strictly against it, it seems to me that ar and ap should be used rather than accounting. But I still not clearly see that this variable is bringing. It's set in main-decoratorS and skipped by createFieldNamesToSkip.createFieldNamesToSkip(), so what? Do I miss something? > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[ https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421744#comment-15421744 ] Jacques Le Roux commented on OFBIZ-7951: Thanks Taher, I need to review the OFBiz Gradle files in details now, to avoid such errors in the future! > remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build > script > - > > Key: OFBIZ-7951 > URL: https://issues.apache.org/jira/browse/OFBIZ-7951 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Fix For: Upcoming Branch > > > The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API > in the JVM arguments. However, given that this has no effect on system > performance, we should make all tasks secure by default (ofbiz, ofbizDebug, > ofbizBackground) and remove the secure tasks. This has the benefit of > reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7956) Updating various Dutch labels in WorkEffortUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7956: Attachment: OFBIZ-7956-WorkEffortUiLabels.xml.patch This patch addresses the issue. > Updating various Dutch labels in WorkEffortUiLabels.xml > --- > > Key: OFBIZ-7956 > URL: https://issues.apache.org/jira/browse/OFBIZ-7956 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7956-WorkEffortUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7956) Updating various Dutch labels in WorkEffortUiLabels.xml
Pierre Smits created OFBIZ-7956: --- Summary: Updating various Dutch labels in WorkEffortUiLabels.xml Key: OFBIZ-7956 URL: https://issues.apache.org/jira/browse/OFBIZ-7956 Project: OFBiz Issue Type: Improvement Components: workeffort Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[ https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421594#comment-15421594 ] Taher Alkhateeb commented on OFBIZ-7951: Hi Jacques, yeah those are createOfbizBackgroundCommandTask and spawnProcess. These two functions use the java ProcessBuilder API to fork a new process with output redirected to /runtime/logs/console.log and this is how OFBiz is started in the background. In fact, what happens exactly is that Gradle calls Gradle but in a new process. Anyway, I tried a few more tests on my computer and I think it is relatively stable now. Thank you again for catching the bug and reporting it, and a few more tests would be great if you can spare some. > remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build > script > - > > Key: OFBIZ-7951 > URL: https://issues.apache.org/jira/browse/OFBIZ-7951 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Fix For: Upcoming Branch > > > The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API > in the JVM arguments. However, given that this has no effect on system > performance, we should make all tasks secure by default (ofbiz, ofbizDebug, > ofbizBackground) and remove the secure tasks. This has the benefit of > reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421581#comment-15421581 ] Pierre Smits commented on OFBIZ-6184: - It was important enough for me to create the issue. It is nothing more than a moot point in your point of view. > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421553#comment-15421553 ] Jacques Le Roux commented on OFBIZ-6184: It seems we are digressing now :), so what, not an issue? > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[ https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421533#comment-15421533 ] Jacques Le Roux commented on OFBIZ-7951: Thanks Taher, Yes I saw that it was not a correct fix when I used it for the trunk demo, and actually even locally before. I wanted something working for the trunk demo and thought I could fix it later. I did not see the bq. two full (and difficult to write) functions in build.gradle orphaned with nothing calling them. though > remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build > script > - > > Key: OFBIZ-7951 > URL: https://issues.apache.org/jira/browse/OFBIZ-7951 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Fix For: Upcoming Branch > > > The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API > in the JVM arguments. However, given that this has no effect on system > performance, we should make all tasks secure by default (ofbiz, ofbizDebug, > ofbizBackground) and remove the secure tasks. This has the benefit of > reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[ https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421481#comment-15421481 ] Taher Alkhateeb commented on OFBIZ-7951: Okay, thank you for reporting this, it is properly fixed in r1756407. The correct solution was to convert the "os" from a variable to a project property. Now the system behaves correctly. Be careful with these changes Jacques you just rendered two full (and difficult to write) functions in build.gradle orphaned with nothing calling them. You also made ofbizBackground operate in the foreground, which is just useless, this is no different from saying ./gradlew ofbiz. Anyway, some further help with testing is appreciated if you can spare some time. Thank you. > remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build > script > - > > Key: OFBIZ-7951 > URL: https://issues.apache.org/jira/browse/OFBIZ-7951 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Fix For: Upcoming Branch > > > The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API > in the JVM arguments. However, given that this has no effect on system > performance, we should make all tasks secure by default (ofbiz, ofbizDebug, > ofbizBackground) and remove the secure tasks. This has the benefit of > reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[ https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421466#comment-15421466 ] Taher Alkhateeb commented on OFBIZ-7951: Jacques this fix is incorrect, now ofbizBackground is in the foreground and you left functions orphaned in the code! I will revert your work and fix this > remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build > script > - > > Key: OFBIZ-7951 > URL: https://issues.apache.org/jira/browse/OFBIZ-7951 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Fix For: Upcoming Branch > > > The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API > in the JVM arguments. However, given that this has no effect on system > performance, we should make all tasks secure by default (ofbiz, ofbizDebug, > ofbizBackground) and remove the secure tasks. This has the benefit of > reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421404#comment-15421404 ] Pierre Smits commented on OFBIZ-6184: - Splitting them up into separate components is also an option, as it offers choice. Faciltymgr is not something that is used very often in a Professional Services Organisation. > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421400#comment-15421400 ] Jacques Le Roux commented on OFBIZ-6184: Wait if we consider that we have 3 web apps in the accouting component, as we have 2 under the product component, then it's not consistent (we have there catalogmgr and facilitymgr) It's though a moot point, because the AR and AP web apps are only covering specialisation of the accounting one. Other opinions? > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6303) Remove EventReminders.properties as it has been declared deprecated
[ https://issues.apache.org/jira/browse/OFBIZ-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6303. -- Resolution: Done Assignee: Jacques Le Roux (was: Pierre Smits) Fix Version/s: Upcoming Branch Thanks Pierre, I removed the file at revision 1756404. > Remove EventReminders.properties as it has been declared deprecated > --- > > Key: OFBIZ-6303 > URL: https://issues.apache.org/jira/browse/OFBIZ-6303 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > Attachments: OFBIZ-6303-WorkEffortReminder.patch > > > The last change came with r1040914. In the comments of the file it is stated > that an example is incorporated in WorkEffortTypeData.xml. The example exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7955) Convert current wiki FAQ page TOC to automated one
Jacques Le Roux created OFBIZ-7955: -- Summary: Convert current wiki FAQ page TOC to automated one Key: OFBIZ-7955 URL: https://issues.apache.org/jira/browse/OFBIZ-7955 Project: OFBiz Issue Type: Task Components: Confluence Reporter: Jacques Le Roux Assignee: Jacques Le Roux Priority: Minor All is in the title, I used anchor there before the TOC macro was available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6303) Remove EventReminders.properties as it has been declared deprecated
[ https://issues.apache.org/jira/browse/OFBIZ-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421261#comment-15421261 ] Jacques Le Roux commented on OFBIZ-6303: Ah got it :D > Remove EventReminders.properties as it has been declared deprecated > --- > > Key: OFBIZ-6303 > URL: https://issues.apache.org/jira/browse/OFBIZ-6303 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-6303-WorkEffortReminder.patch > > > The last change came with r1040914. In the comments of the file it is stated > that an example is incorporated in WorkEffortTypeData.xml. The example exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7796) Running OFBiz as a service fails
[ https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421227#comment-15421227 ] Pierre Smits commented on OFBIZ-7796: - I surmise that Taher is projecting how he would like things to be in production environments of adopters. In a production environment one doesn't use repositories (of any kind), just executable ready solutions to minimise risks. > Running OFBiz as a service fails > > > Key: OFBIZ-7796 > URL: https://issues.apache.org/jira/browse/OFBIZ-7796 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk > Environment: Ubuntu 16.04, openjdk-8-jdk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch, > OFBIZ-7796-rc.ofbiz.for.debian-v2.patch > > > In a new ubuntu environment I performed a checkout from trunk and ran the > loadDefault build script. > After this had completed, I moved the ofbiz directory from my user folder to > the /opt folder, and configured the Ubuntu environment to be able to run > OFBiz as a service. > This entails: > * deploy a script in /etc/init.d > * set the correct permissions of the service script > * create the service user > * changed the owner and ownergroup of the files and folders in /opt/ofbiz > and then fire the service: > sudo /etc/init.d/ofbiz start > This normally starts the proces java -jar ofbiz.jar > But now nothing happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7921) Incorporate the readme for the bizznesstime theme
[ https://issues.apache.org/jira/browse/OFBIZ-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421222#comment-15421222 ] Pierre Smits commented on OFBIZ-7921: - Did I do that? My apologies. I will provide a new patch file. > Incorporate the readme for the bizznesstime theme > - > > Key: OFBIZ-7921 > URL: https://issues.apache.org/jira/browse/OFBIZ-7921 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: Upcoming Branch > > Attachments: OFBIZ-7921-bizznesstime.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421220#comment-15421220 ] Pierre Smits commented on OFBIZ-6184: - To keep consistency with all other applications? Feel free to execute a search/find action regarding ' Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6303) Remove EventReminders.properties as it has been declared deprecated
[ https://issues.apache.org/jira/browse/OFBIZ-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421217#comment-15421217 ] Pierre Smits commented on OFBIZ-6303: - I don't know what your reasoning regarding that would be, but the entire file is superfluous. ;) > Remove EventReminders.properties as it has been declared deprecated > --- > > Key: OFBIZ-6303 > URL: https://issues.apache.org/jira/browse/OFBIZ-6303 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-6303-WorkEffortReminder.patch > > > The last change came with r1040914. In the comments of the file it is stated > that an example is incorporated in WorkEffortTypeData.xml. The example exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7953) Updating various labels in CommonUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7953: Attachment: OFBIZ-7953-CommonUiLabels.xml.patch This patch addresses the issues mentioned in the comment by Jacques. > Updating various labels in CommonUiLabels.xml > - > > Key: OFBIZ-7953 > URL: https://issues.apache.org/jira/browse/OFBIZ-7953 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7953-CommonUiLabels.xml.patch, > OFBIZ-7953-CommonUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OFBIZ-7782) Duplicates of .properties and Label files appear in ${ofbizRootName}.jar
[
https://issues.apache.org/jira/browse/OFBIZ-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits reopened OFBIZ-7782:
-
Reopening as applying a trick in a development environment to hide some files
doesn't remove useless bloatware from a .jar file intended to be used in a
production environment.
> Duplicates of .properties and Label files appear in ${ofbizRootName}.jar
>
>
> Key: OFBIZ-7782
> URL: https://issues.apache.org/jira/browse/OFBIZ-7782
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
> Attachments: Screen Shot 2016-07-13 at 10.05.43.png
>
>
> With the switch to gradle/gradlew .properties and the label definition files
> get duplicated into the build folder. See attached screenshot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420831#comment-15420831 ] Jacques Le Roux commented on OFBIZ-6184: Could you provide more details about what this change brings up? > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7953) Updating various labels in CommonUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420829#comment-15420829 ] Jacques Le Roux commented on OFBIZ-7953: This is certainly wrong + +Class +Événement The rest sounds good to me. As it's mostly "nl" addition I let our qualified committer ([~hansbak]) check this part > Updating various labels in CommonUiLabels.xml > - > > Key: OFBIZ-7953 > URL: https://issues.apache.org/jira/browse/OFBIZ-7953 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7953-CommonUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6303) Remove EventReminders.properties as it has been declared deprecated
[ https://issues.apache.org/jira/browse/OFBIZ-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420826#comment-15420826 ] Jacques Le Roux commented on OFBIZ-6303: Why would I remove the license header? > Remove EventReminders.properties as it has been declared deprecated > --- > > Key: OFBIZ-6303 > URL: https://issues.apache.org/jira/browse/OFBIZ-6303 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-6303-WorkEffortReminder.patch > > > The last change came with r1040914. In the comments of the file it is stated > that an example is incorporated in WorkEffortTypeData.xml. The example exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-5994) Have view-entity AgreementAndRole removed
[ https://issues.apache.org/jira/browse/OFBIZ-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-5994. -- Resolution: Done Fix Version/s: Upcoming Branch Thanks Pierre, your modified patch is in trunk at revision 1756365. > Have view-entity AgreementAndRole removed > - > > Key: OFBIZ-5994 > URL: https://issues.apache.org/jira/browse/OFBIZ-5994 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk, Upcoming Branch >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Minor > Labels: agreement(s), role, roles > Fix For: Upcoming Branch > > Attachments: OFBIZ-5994-AgreementAndRole.patch > > > The view-entity is not referenced in any Screen, Form and Service definition. > Having this in the entity-model is superfluous. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7767) Have gradle produce logs
[ https://issues.apache.org/jira/browse/OFBIZ-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-7767. -- Resolution: Not A Problem Assignee: Jacques Le Roux It seems to me that this has been clarified and is no longer an issue > Have gradle produce logs > > > Key: OFBIZ-7767 > URL: https://issues.apache.org/jira/browse/OFBIZ-7767 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Minor > > Currently executing gradle tasks doesn't generate logs. > This is related to traceability of where 3rd party libraries (jar files) are > downloaded from and where they are placed in folder structures and which are > used in the various deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7782) Duplicates of .properties and Label files appear in ${ofbizRootName}.jar
[
https://issues.apache.org/jira/browse/OFBIZ-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-7782.
--
Resolution: Not A Problem
Not a problem as long as none have been clearly identified
> Duplicates of .properties and Label files appear in ${ofbizRootName}.jar
>
>
> Key: OFBIZ-7782
> URL: https://issues.apache.org/jira/browse/OFBIZ-7782
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
> Attachments: Screen Shot 2016-07-13 at 10.05.43.png
>
>
> With the switch to gradle/gradlew .properties and the label definition files
> get duplicated into the build folder. See attached screenshot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7782) Duplicates of .properties and Label files appear in ${ofbizRootName}.jar
[
https://issues.apache.org/jira/browse/OFBIZ-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420778#comment-15420778
]
Jacques Le Roux commented on OFBIZ-7782:
On this point: I put an advice about using https://nodj.github.io/AutoDeriv/ at
https://cwiki.apache.org/confluence/display/OFBIZ/Eclipse+Tips#EclipseTips-Hidefoldersfromsearches
> Duplicates of .properties and Label files appear in ${ofbizRootName}.jar
>
>
> Key: OFBIZ-7782
> URL: https://issues.apache.org/jira/browse/OFBIZ-7782
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
> Attachments: Screen Shot 2016-07-13 at 10.05.43.png
>
>
> With the switch to gradle/gradlew .properties and the label definition files
> get duplicated into the build folder. See attached screenshot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7796) Running OFBiz as a service fails
[ https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420769#comment-15420769 ] Jacques Le Roux commented on OFBIZ-7796: Beware, on trunk demo I had to use "gradlew terminateOfbiz" to completly shutdown OFBiz in all cases... > Running OFBiz as a service fails > > > Key: OFBIZ-7796 > URL: https://issues.apache.org/jira/browse/OFBIZ-7796 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk > Environment: Ubuntu 16.04, openjdk-8-jdk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch, > OFBIZ-7796-rc.ofbiz.for.debian-v2.patch > > > In a new ubuntu environment I performed a checkout from trunk and ran the > loadDefault build script. > After this had completed, I moved the ofbiz directory from my user folder to > the /opt folder, and configured the Ubuntu environment to be able to run > OFBiz as a service. > This entails: > * deploy a script in /etc/init.d > * set the correct permissions of the service script > * create the service user > * changed the owner and ownergroup of the files and folders in /opt/ofbiz > and then fire the service: > sudo /etc/init.d/ofbiz start > This normally starts the proces java -jar ofbiz.jar > But now nothing happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7796) Running OFBiz as a service fails
[ https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420762#comment-15420762 ] Jacques Le Roux commented on OFBIZ-7796: Actually as Taher suggested, in production you can change the repository and not use jcenter but your own, this to avoid possible issues on jcenter. You though need to prodive a well formated repository. Accordind to https://docs.gradle.org/current/userguide/artifact_dependencies_tutorial.html#N10660 bq. A repository is really just a collection of files, organized by group, name and version. Gradle understands several different repository formats, such as Maven and Ivy, and several different ways of accessing the repository, such as using the local file system or HTTP. > Running OFBiz as a service fails > > > Key: OFBIZ-7796 > URL: https://issues.apache.org/jira/browse/OFBIZ-7796 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk > Environment: Ubuntu 16.04, openjdk-8-jdk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch, > OFBIZ-7796-rc.ofbiz.for.debian-v2.patch > > > In a new ubuntu environment I performed a checkout from trunk and ran the > loadDefault build script. > After this had completed, I moved the ofbiz directory from my user folder to > the /opt folder, and configured the Ubuntu environment to be able to run > OFBiz as a service. > This entails: > * deploy a script in /etc/init.d > * set the correct permissions of the service script > * create the service user > * changed the owner and ownergroup of the files and folders in /opt/ofbiz > and then fire the service: > sudo /etc/init.d/ofbiz start > This normally starts the proces java -jar ofbiz.jar > But now nothing happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7921) Incorporate the readme for the bizznesstime theme
[
https://issues.apache.org/jira/browse/OFBIZ-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420757#comment-15420757
]
Jacques Le Roux commented on OFBIZ-7921:
Seems a not amended C/P (Asset+Management)
{quote}
+The bizznesstime theme component offers an alternative presentation.
+For more information about this component visit the product page in the OFBiz
+WIKI, which can be found at
+https://cwiki.apache.org/confluence/display/OFBIZ/Asset+Management
+
+JIRA issues related to this component can be found at
+ https://issues.apache.org/jira/browse/OFBIZ/component/12311644
+
+Committed revisions can be viewed at
+http://svn.apache.org/viewvc/ofbiz/trunk/specialpurpose/assetmaint/
{quote}
> Incorporate the readme for the bizznesstime theme
> -
>
> Key: OFBIZ-7921
> URL: https://issues.apache.org/jira/browse/OFBIZ-7921
> Project: OFBiz
> Issue Type: Sub-task
> Components: themes
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7921-bizznesstime.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-7954) Add NLP function to parse text content
Shi Jinghai created OFBIZ-7954: -- Summary: Add NLP function to parse text content Key: OFBIZ-7954 URL: https://issues.apache.org/jira/browse/OFBIZ-7954 Project: OFBiz Issue Type: Improvement Affects Versions: Trunk Reporter: Shi Jinghai Assignee: Shi Jinghai Priority: Minor NLP(Natural Language Processing) is an amazing tech can help us to improve our beloved OFBiz. NLP can be used to train your own model to parse product attributes and understand what it is, before importing the product, or used as an online CRM text robot to answer simple questions. We will try to add a new nlp component, and we hope we can get some help from the community. AFAIK, two apache projects are working on NLP: http://tika.apache.org/ http://opennlp.apache.org/ The Stanford NLP is used in tika: http://nlp.stanford.edu/ While implementing this component, we found an ebay paper on this topic is very useful: http://aclweb.org/anthology/D/D11/D11-1144.pdf Kind Regards, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[ https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-7951. -- Resolution: Fixed Fix Version/s: Upcoming Branch Bug fixed at r1756351 > remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build > script > - > > Key: OFBIZ-7951 > URL: https://issues.apache.org/jira/browse/OFBIZ-7951 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > Fix For: Upcoming Branch > > > The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API > in the JVM arguments. However, given that this has no effect on system > performance, we should make all tasks secure by default (ofbiz, ofbizDebug, > ofbizBackground) and remove the secure tasks. This has the benefit of > reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420517#comment-15420517 ] Pierre Smits commented on OFBIZ-6184: - Ping? > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5994) Have view-entity AgreementAndRole removed
[ https://issues.apache.org/jira/browse/OFBIZ-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420516#comment-15420516 ] Pierre Smits commented on OFBIZ-5994: - Ping? > Have view-entity AgreementAndRole removed > - > > Key: OFBIZ-5994 > URL: https://issues.apache.org/jira/browse/OFBIZ-5994 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk, Upcoming Branch >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Minor > Labels: agreement(s), role, roles > Attachments: OFBIZ-5994-AgreementAndRole.patch > > > The view-entity is not referenced in any Screen, Form and Service definition. > Having this in the entity-model is superfluous. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7953) Updating various labels in CommonUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7953: Attachment: OFBIZ-7953-CommonUiLabels.xml.patch This patch addresses the issue. > Updating various labels in CommonUiLabels.xml > - > > Key: OFBIZ-7953 > URL: https://issues.apache.org/jira/browse/OFBIZ-7953 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7953-CommonUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7953) Updating various labels in CommonUiLabels.xml
Pierre Smits created OFBIZ-7953: --- Summary: Updating various labels in CommonUiLabels.xml Key: OFBIZ-7953 URL: https://issues.apache.org/jira/browse/OFBIZ-7953 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6556) Have the means to create a cmssite component in the hot-deploy folder
[ https://issues.apache.org/jira/browse/OFBIZ-6556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420508#comment-15420508 ] Pierre Smits commented on OFBIZ-6556: - Ping? > Have the means to create a cmssite component in the hot-deploy folder > - > > Key: OFBIZ-6556 > URL: https://issues.apache.org/jira/browse/OFBIZ-6556 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-6556-CmsSiteCreator.patch > > > The create-component functionality enables a quick start to create hot-deploy > components for developers. > We should have the same kind of functionality to create cmssite components in > the hot-deploy folder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5959) Add lifespan fields to PartyRole and dependency refactoring
[ https://issues.apache.org/jira/browse/OFBIZ-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-5959: Attachment: OFBIZ-5959-party-entitymodel.xml.patch This is a revised patch file addressing the relocation of entity-model files from individual components to the datamodel component. > Add lifespan fields to PartyRole and dependency refactoring > --- > > Key: OFBIZ-5959 > URL: https://issues.apache.org/jira/browse/OFBIZ-5959 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits > Labels: role, roles > Attachments: OFBIZ-5959-party-entitymodel.xml.patch > > > Currently the assignments of roles to parties are boolean (there or not > there). > However, these role assignments also have a lifespan. This can be achieved by > adding fromDate and thruDate fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-5959) Add lifespan fields to PartyRole and dependency refactoring
[ https://issues.apache.org/jira/browse/OFBIZ-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5959: --- Assignee: Pierre Smits > Add lifespan fields to PartyRole and dependency refactoring > --- > > Key: OFBIZ-5959 > URL: https://issues.apache.org/jira/browse/OFBIZ-5959 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: role, roles > Attachments: OFBIZ-5959-party-entitymodel.xml.patch > > > Currently the assignments of roles to parties are boolean (there or not > there). > However, these role assignments also have a lifespan. This can be achieved by > adding fromDate and thruDate fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6303) Remove EventReminders.properties as it has been declared deprecated
[ https://issues.apache.org/jira/browse/OFBIZ-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420497#comment-15420497 ] Pierre Smits commented on OFBIZ-6303: - Ping? > Remove EventReminders.properties as it has been declared deprecated > --- > > Key: OFBIZ-6303 > URL: https://issues.apache.org/jira/browse/OFBIZ-6303 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-6303-WorkEffortReminder.patch > > > The last change came with r1040914. In the comments of the file it is stated > that an example is incorporated in WorkEffortTypeData.xml. The example exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7918) Improve Dutch labels regarding accounting reports
[ https://issues.apache.org/jira/browse/OFBIZ-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420496#comment-15420496 ] Pierre Smits commented on OFBIZ-7918: - Ping? > Improve Dutch labels regarding accounting reports > - > > Key: OFBIZ-7918 > URL: https://issues.apache.org/jira/browse/OFBIZ-7918 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7918-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7921) Incorporate the readme for the bizznesstime theme
[ https://issues.apache.org/jira/browse/OFBIZ-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420495#comment-15420495 ] Pierre Smits commented on OFBIZ-7921: - Ping? > Incorporate the readme for the bizznesstime theme > - > > Key: OFBIZ-7921 > URL: https://issues.apache.org/jira/browse/OFBIZ-7921 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: Upcoming Branch > > Attachments: OFBIZ-7921-bizznesstime.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[
https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420492#comment-15420492
]
Jacques Le Roux commented on OFBIZ-7951:
Same on linux
{code}
ofbizDemo@ofbiz-vm:~/trunk$ ./gradlew --stacktrace "ofbizBackground --start"
FAILURE: Build failed with an exception.
* Where:
Build file '/home/ofbizDemo/trunk/build.gradle' line: 761
* What went wrong:
Could not find property 'os' on root project 'ofbiz'.
* Try:
Run with --info or --debug option to get more log output.
* Exception is:
groovy.lang.MissingPropertyException: Could not find property 'os' on root
project 'ofbiz'.
at
org.gradle.api.internal.AbstractDynamicObject.propertyMissingException(AbstractDynamicObject.java:43)
at
org.gradle.api.internal.AbstractDynamicObject.getProperty(AbstractDynamicObject.java:35)
at
org.gradle.api.internal.CompositeDynamicObject.getProperty(CompositeDynamicObject.java:97)
at
org.gradle.groovy.scripts.BasicScript.propertyMissing(BasicScript.java:66)
at org.gradle.groovy.scripts.Script.getProperty(Script.java:56)
at
build_g9a0vr11pt3xrbvhhnl5xaag.createOfbizBackgroundCommandTask(/home/ofbizDemo/trunk/build.gradle:761)
at
build_g9a0vr11pt3xrbvhhnl5xaag$_run_closure35.doCall(/home/ofbizDemo/trunk/build.gradle:734)
{code}
> remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build
> script
> -
>
> Key: OFBIZ-7951
> URL: https://issues.apache.org/jira/browse/OFBIZ-7951
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>
> The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API
> in the JVM arguments. However, given that this has no effect on system
> performance, we should make all tasks secure by default (ofbiz, ofbizDebug,
> ofbizBackground) and remove the secure tasks. This has the benefit of
> reducing the number of tasks users need to be aware of.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[
https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reopened OFBIZ-7951:
We have a problem, on Windows at least:
{code}
C:\projectASF-Mars\ofbiz>gradlew --stacktrace ofbizBackground
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
FAILURE: Build failed with an exception.
* Where:
Build file 'C:\projectASF-Mars\ofbiz\build.gradle' line: 761
* What went wrong:
Could not find property 'os' on root project 'ofbiz'.
* Try:
Run with --info or --debug option to get more log output.
* Exception is:
groovy.lang.MissingPropertyException: Could not find property 'os' on root
project 'ofbiz'.
at
org.gradle.api.internal.AbstractDynamicObject.propertyMissingException(AbstractDynamicObject.java:43)
at
org.gradle.api.internal.AbstractDynamicObject.getProperty(AbstractDynamicObject.java:35)
at
org.gradle.api.internal.CompositeDynamicObject.getProperty(CompositeDynamicObject.java:97)
at
org.gradle.groovy.scripts.BasicScript.propertyMissing(BasicScript.java:66)
at org.gradle.groovy.scripts.Script.getProperty(Script.java:56)
at
build_146dpgoos7lwgtdjesm7a07a.createOfbizBackgroundCommandTask(C:\projectASF-Mars\ofbiz\build.gradle:761)
at
build_146dpgoos7lwgtdjesm7a07a$_run_closure35.doCall(C:\projectASF-Mars\ofbiz\build.gradle:734)
{code}
> remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build
> script
> -
>
> Key: OFBIZ-7951
> URL: https://issues.apache.org/jira/browse/OFBIZ-7951
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Upcoming Branch
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>
> The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API
> in the JVM arguments. However, given that this has no effect on system
> performance, we should make all tasks secure by default (ofbiz, ofbizDebug,
> ofbizBackground) and remove the secure tasks. This has the benefit of
> reducing the number of tasks users need to be aware of.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420338#comment-15420338 ] Jacques Le Roux commented on OFBIZ-7910: Thanks Taher, this seems good to me and we will only need to use grunt-md2html to put (and later possibly update) the documentation in the wiki. If nobody disagree I'll commit in few days > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: ADD_LIB.patch, OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7723) Use grunt-md2html to integrate our README.MD from repo to Confluence
[ https://issues.apache.org/jira/browse/OFBIZ-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-7723: --- Description: See INFRA-12200 for details, this is about moving/updating Gradle documentation into the wiki (was: See INFRA-12200 for details) > Use grunt-md2html to integrate our README.MD from repo to Confluence > > > Key: OFBIZ-7723 > URL: https://issues.apache.org/jira/browse/OFBIZ-7723 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > Labels: documentation, gradle, wiki > Fix For: Upcoming Branch > > > See INFRA-12200 for details, this is about moving/updating Gradle > documentation into the wiki -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7723) Use grunt-md2html to integrate our README.MD from repo to Confluence
[ https://issues.apache.org/jira/browse/OFBIZ-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-7723: --- Labels: documentation gradle wiki (was: ) > Use grunt-md2html to integrate our README.MD from repo to Confluence > > > Key: OFBIZ-7723 > URL: https://issues.apache.org/jira/browse/OFBIZ-7723 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > Labels: documentation, gradle, wiki > Fix For: Upcoming Branch > > > See INFRA-12200 for details -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[ https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420331#comment-15420331 ] Jacques Le Roux commented on OFBIZ-7951: I thought a minute about hidding deserialize-trace.txt and is-deserialized.txt from svn (using svn:ignore). But it's maybe better to have them show to users. Because this is a sensible thing and those could be good reminders about it. Windows committers (apart me who now :D) can always use ToirtoiseSVN ignore-on-commit feature; others have to wait SVN-2858. BTW this also to encourage committers to vote for this issue ;) > remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build > script > - > > Key: OFBIZ-7951 > URL: https://issues.apache.org/jira/browse/OFBIZ-7951 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > > The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API > in the JVM arguments. However, given that this has no effect on system > performance, we should make all tasks secure by default (ofbiz, ofbizDebug, > ofbizBackground) and remove the secure tasks. This has the benefit of > reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taher Alkhateeb updated OFBIZ-7910: --- Attachment: ADD_LIB.patch Hello, I am attaching a patch that creates a custom libs folder in OFBiz top level directory where people can keep their jars and update the master script build.gradle accordingly. Take a look at it and see if suitable. > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: ADD_LIB.patch, OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[ https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taher Alkhateeb closed OFBIZ-7951. -- Resolution: Fixed Work is complete and all tests pass > remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build > script > - > > Key: OFBIZ-7951 > URL: https://issues.apache.org/jira/browse/OFBIZ-7951 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > > The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API > in the JVM arguments. However, given that this has no effect on system > performance, we should make all tasks secure by default (ofbiz, ofbizDebug, > ofbizBackground) and remove the secure tasks. This has the benefit of > reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
[ https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420250#comment-15420250 ] Taher Alkhateeb commented on OFBIZ-7951: Done and committed in r1756305. > remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build > script > - > > Key: OFBIZ-7951 > URL: https://issues.apache.org/jira/browse/OFBIZ-7951 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb > > The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API > in the JVM arguments. However, given that this has no effect on system > performance, we should make all tasks secure by default (ofbiz, ofbizDebug, > ofbizBackground) and remove the secure tasks. This has the benefit of > reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7952) CXF memory issue dump
[ https://issues.apache.org/jira/browse/OFBIZ-7952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ismail CHAKOUR closed OFBIZ-7952. - Resolution: Invalid > CXF memory issue dump > - > > Key: OFBIZ-7952 > URL: https://issues.apache.org/jira/browse/OFBIZ-7952 > Project: OFBiz > Issue Type: Bug > Components: framework >Reporter: ismail CHAKOUR > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7952) CXF memory issue dump
ismail CHAKOUR created OFBIZ-7952: - Summary: CXF memory issue dump Key: OFBIZ-7952 URL: https://issues.apache.org/jira/browse/OFBIZ-7952 Project: OFBiz Issue Type: Bug Components: framework Reporter: ismail CHAKOUR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419615#comment-15419615 ] Jacques Le Roux commented on OFBIZ-7910: Taher, I let you implement your idea OOTB, thanks! > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419613#comment-15419613 ] Jacques Le Roux commented on OFBIZ-7910: It seems the best way to me, no needs to dig down the folders tree! And as you said it's bq. cleaner, easier, integrated and detects conflicts early Better indeed to have only one version by lib, notably for security reasons! > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419589#comment-15419589 ] Jacques Le Roux commented on OFBIZ-7910: Thanks Wai, it's clear now :) > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419452#comment-15419452
]
Wai edited comment on OFBIZ-7910 at 8/12/16 8:49 PM:
-
In /ofbiz/build.gradle, I added Taher's suggestion in the 'dependencies' block
{code}
dependencies {
...
compile fileTree(dir: file("${rootDir}/lib"), include: '**/*.jar')
...
}
{code}
Then I added the 3rd party in-house jar into /ofbiz/lib.
Ran $ gradle cleanAll build
Now my hot-deploy component compiles ok.
was (Author: wt):
In /ofbiz/build.gradle, I added Taher's suggestion in the 'dependencies' block
{{monospaced}}
dependencies {
...
compile fileTree(dir: file("${rootDir}/lib"), include: '**/*.jar')
...
}
{{monospaced}}
Then I added the 3rd party in-house jar into /ofbiz/lib.
Ran $ gradle cleanAll build
Now my hot-deploy component compiles ok.
> Improve component template(s) to work with the Gradle solution
> --
>
> Key: OFBIZ-7910
> URL: https://issues.apache.org/jira/browse/OFBIZ-7910
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Trivial
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have
> the means to work with the Gradle build solution visavis dependency
> management.
> The reason for this is that no build.gradle template exists that need to be
> copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419452#comment-15419452
]
Wai edited comment on OFBIZ-7910 at 8/12/16 8:48 PM:
-
In /ofbiz/build.gradle, I added Taher's suggestion in the 'dependencies' block
{{monospaced}}
dependencies {
...
compile fileTree(dir: file("${rootDir}/lib"), include: '**/*.jar')
...
}
{{monospaced}}
Then I added the 3rd party in-house jar into /ofbiz/lib.
Ran $ gradle cleanAll build
Now my hot-deploy component compiles ok.
was (Author: wt):
In /ofbiz/build.gradle, I added Taher's suggestion in the 'dependencies' block
{{monospaced
dependencies {
...
compile fileTree(dir: file("${rootDir}/lib"), include: '**/*.jar')
...
}
}}
Then I added the 3rd party in-house jar into /ofbiz/lib.
Ran $ gradle cleanAll build
Now my hot-deploy component compiles ok.
> Improve component template(s) to work with the Gradle solution
> --
>
> Key: OFBIZ-7910
> URL: https://issues.apache.org/jira/browse/OFBIZ-7910
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Trivial
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have
> the means to work with the Gradle build solution visavis dependency
> management.
> The reason for this is that no build.gradle template exists that need to be
> copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419452#comment-15419452
]
Wai edited comment on OFBIZ-7910 at 8/12/16 8:48 PM:
-
In /ofbiz/build.gradle, I added Taher's suggestion in the 'dependencies' block
{{monospaced
dependencies {
...
compile fileTree(dir: file("${rootDir}/lib"), include: '**/*.jar')
...
}
}}
Then I added the 3rd party in-house jar into /ofbiz/lib.
Ran $ gradle cleanAll build
Now my hot-deploy component compiles ok.
was (Author: wt):
In /ofbiz/build.gradle, I added Taher's suggestion in the 'dependencies' block
dependencies {
...
compile fileTree(dir: file("${rootDir}/lib"), include: '**/*.jar')
...
}
Then I added the 3rd party in-house jar into /ofbiz/lib.
Ran $ gradle cleanAll build
Now my hot-deploy component compiles ok.
> Improve component template(s) to work with the Gradle solution
> --
>
> Key: OFBIZ-7910
> URL: https://issues.apache.org/jira/browse/OFBIZ-7910
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Trivial
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have
> the means to work with the Gradle build solution visavis dependency
> management.
> The reason for this is that no build.gradle template exists that need to be
> copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419452#comment-15419452
]
Wai commented on OFBIZ-7910:
In /ofbiz/build.gradle, I added Taher's suggestion in the 'dependencies' block
dependencies {
...
compile fileTree(dir: file("${rootDir}/lib"), include: '**/*.jar')
...
}
Then I added the 3rd party in-house jar into /ofbiz/lib.
Ran $ gradle cleanAll build
Now my hot-deploy component compiles ok.
> Improve component template(s) to work with the Gradle solution
> --
>
> Key: OFBIZ-7910
> URL: https://issues.apache.org/jira/browse/OFBIZ-7910
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Trivial
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have
> the means to work with the Gradle build solution visavis dependency
> management.
> The reason for this is that no build.gradle template exists that need to be
> copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419435#comment-15419435 ] Jacques Le Roux commented on OFBIZ-7910: Wai, could you please confirm which way you used? Because we all want a definitive solution... Thanks! > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419341#comment-15419341 ] Wai commented on OFBIZ-7910: Thanks, that worked. Wai > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419319#comment-15419319 ] Taher Alkhateeb commented on OFBIZ-7910: You are absolutely right and you guessed right, my answer is temporary. Right now I'm just trying to help Wai to make sure there are no bugs in the build system (I believe there are none as far as lib importing is concerned). Perhaps a permanent solution is to get rid of all /lib folders and just keep an empty one in root folder. Given that we do not really need the custom classloader and we can just share the libraries with all components (cleaner, easier, integrated and detects conflicts early). So if we do decide to adopt the permanent solution described above, we can use the code snippet I provided to Wai. No strong opinion, whatever you guys prefer. > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419307#comment-15419307 ] Pierre Smits commented on OFBIZ-7948: - Thanks, Wai. > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419303#comment-15419303 ] Jacques Le Roux commented on OFBIZ-7910: Taher, I was under the impression that after the jpim-0.1.jar removing we would get rid of /framework/base/lib/. Do you have other plans in mind? Is your answer only a temporay solution? > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419225#comment-15419225
]
Taher Alkhateeb commented on OFBIZ-7910:
Hi Wai, i'm not sure if you meant this literally or what, so let me try to be
very exact:
If you want to include your common libs in root folder /lib use the below code:
{code}
compile fileTree(dir: file("${rootDir}/lib"), include: '**/*.jar')
{code}
Alternatively (and more simply) just put your shared libs in
/framework/base/lib/
> Improve component template(s) to work with the Gradle solution
> --
>
> Key: OFBIZ-7910
> URL: https://issues.apache.org/jira/browse/OFBIZ-7910
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Trivial
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have
> the means to work with the Gradle build solution visavis dependency
> management.
> The reason for this is that no build.gradle template exists that need to be
> copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419060#comment-15419060
]
Wai commented on OFBIZ-7910:
I followed your suggestion by modifying /ofbiz/build.gradle and replace the
dependency to
compile files('$OFBIZ_HOME/lib') and placing myInHouse.jar into /ofbiz/lib
After running $ gradlew cleanAll build, a compilation error occurs with
mycomponent1 with symbol not found.
> Improve component template(s) to work with the Gradle solution
> --
>
> Key: OFBIZ-7910
> URL: https://issues.apache.org/jira/browse/OFBIZ-7910
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Trivial
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have
> the means to work with the Gradle build solution visavis dependency
> management.
> The reason for this is that no build.gradle template exists that need to be
> copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418996#comment-15418996 ] Taher Alkhateeb commented on OFBIZ-7910: Hi Wai, Any library you import is shared by all components under the new gradle build system. The problem in your modification in "Try1" is that the syntax is not right. Please take a look at the above code for proper importing of libs. If you import properly then your components would not complain. You just need to add $OFBIZ_HOME/lib to the compile set. > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418980#comment-15418980
]
Wai commented on OFBIZ-7910:
Hello Taher, Jacques
Here are my findings.
My source tree contains the following relevant details...
/ofbiz
/ofbiz/lib
/ofbiz/hot-deploy/mycomponent1
/ofbiz/hot-deploy/mycomponent1/lib
mycomponent1 references a class in myInHouse.jar
Try1:
I placed the myInHouse.jar in /ofbiz/lib
Modified /ofbiz/build.gradle and added the following to dependencies
compile files('lib')
Ran $gradlew cleanAll build
The compilation failed on mycomponent1.
-the failure is due to mycomponent1 referencing a class that is not found.
This class is in myInHouse.jar
Try2:
I placed the myInHouse.jar into /ofbiz/hot-deploy/mycomponent1/lib
Ran $gradlew cleanAll build
The compilation was sucessful.
Conclusion:
My findinds corroborates Taher's comment about searching in the local 'lib'
directory of each component to locate the custom jars.
I also noticed a deficiency with the build script. Consider a developer creates
multiple hot-deploy components. Each component references classes from the
same myInHouse.jar. This would require a copy of the same jar in each of the
components 'lib' directory. This is very inconvenient.
I suggest to modify the script so that each hot-deploy component can reference
one myInHouse.jar located in /ofbiz/lib.
I hope this helps.
Wai
> Improve component template(s) to work with the Gradle solution
> --
>
> Key: OFBIZ-7910
> URL: https://issues.apache.org/jira/browse/OFBIZ-7910
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Trivial
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have
> the means to work with the Gradle build solution visavis dependency
> management.
> The reason for this is that no build.gradle template exists that need to be
> copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-7951) remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
Taher Alkhateeb created OFBIZ-7951: -- Summary: remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script Key: OFBIZ-7951 URL: https://issues.apache.org/jira/browse/OFBIZ-7951 Project: OFBiz Issue Type: Improvement Affects Versions: Upcoming Branch Reporter: Taher Alkhateeb Assignee: Taher Alkhateeb The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API in the JVM arguments. However, given that this has no effect on system performance, we should make all tasks secure by default (ofbiz, ofbizDebug, ofbizBackground) and remove the secure tasks. This has the benefit of reducing the number of tasks users need to be aware of. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7950) Improve consistency of service createEmployee
[ https://issues.apache.org/jira/browse/OFBIZ-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Montalbano Florian updated OFBIZ-7950: -- Attachment: OFBIZ-7950_proposition.patch Here is a proposition to harmonize things : A Employee is at the very least just a Party with a Role of Employee and a RelationShip with a PartyGroup. That's why the only required field is the Internal Organization. Then, you can fill whatever fields you need. But if you fill the first name field, you have to provide at least the last name too. Same way for the address. What do you think of this ? Is this a good idea or should we go the other way arround with adding constraint to the service ? > Improve consistency of service createEmployee > - > > Key: OFBIZ-7950 > URL: https://issues.apache.org/jira/browse/OFBIZ-7950 > Project: OFBiz > Issue Type: Improvement > Components: humanres >Affects Versions: Trunk >Reporter: Montalbano Florian >Priority: Minor > Labels: consistency, create, employee, service > Attachments: OFBIZ-7950_proposition.patch > > > In the humanres component, we can create an employee through the form > https://localhost:8443/humanres/control/NewEmployee . > This form has required fields that are not the same requirement than the > service called when submitting the form. > The service called is createEmployee. > In the service, everything is declared optional but the > postalAddContactMechPurpTypeId (which is set in the form as an hidden field). > This means we could create an Employee without forcing a telephone number or > a primary address or even a first name. > But then, within the service, a check is done on the firstName and lastName > parameters and if missing, an error shows up. > We could harmonize things a little. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7950) Improve consistency of service createEmployee
Montalbano Florian created OFBIZ-7950: - Summary: Improve consistency of service createEmployee Key: OFBIZ-7950 URL: https://issues.apache.org/jira/browse/OFBIZ-7950 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: Trunk Reporter: Montalbano Florian Priority: Minor In the humanres component, we can create an employee through the form https://localhost:8443/humanres/control/NewEmployee . This form has required fields that are not the same requirement than the service called when submitting the form. The service called is createEmployee. In the service, everything is declared optional but the postalAddContactMechPurpTypeId (which is set in the form as an hidden field). This means we could create an Employee without forcing a telephone number or a primary address or even a first name. But then, within the service, a check is done on the firstName and lastName parameters and if missing, an error shows up. We could harmonize things a little. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418740#comment-15418740 ] Jacques Le Roux commented on OFBIZ-7948: Hi Wai, Could you please try Taher's solution at bottom of OFBIZ-7910? Thanks! > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418705#comment-15418705
]
Taher Alkhateeb commented on OFBIZ-7910:
I'm not sure if I got it right, but by default gradle will look in every
component for a /lib directory and add any of those jars to the classpath.
Specifically, this piece of code already does the job automatically as long as
you put those jars in /lib
{code}
getDirectoryInActiveComponentsIfExists('lib').each { libDir ->
compile fileTree(dir: libDir, include: '**/*.jar')
}
{code}
> Improve component template(s) to work with the Gradle solution
> --
>
> Key: OFBIZ-7910
> URL: https://issues.apache.org/jira/browse/OFBIZ-7910
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Trivial
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have
> the means to work with the Gradle build solution visavis dependency
> management.
> The reason for this is that no build.gradle template exists that need to be
> copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418693#comment-15418693 ] Jacques Le Roux commented on OFBIZ-7910: Hi Taher, So what would be your answer to Wai at OFBIZ-7948 ? > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418640#comment-15418640 ] Taher Alkhateeb commented on OFBIZ-7910: Hi Jacques, You can apply the java plugin directly to subprojects from the master build script. But why? We don't need the Java plugin in subprojects, that would just create an unnecessary build directory with artifacts that we will not use. > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418631#comment-15418631 ] Jacques Le Roux commented on OFBIZ-7910: Pierre from your last comment at OFBIZ-7948, and more as a reminder for our documentation, we should note that when using external libs in (hopefully soon) plugins, the local build.gradle file must also contain bq. apply plugin:'java' before the dependencies definition. > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Trivial > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418633#comment-15418633 ] Jacques Le Roux commented on OFBIZ-7948: This is somehow related with OFBIZ-7910 > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wai closed OFBIZ-7948. -- Resolution: Not A Problem > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417125#comment-15417125 ] Wai commented on OFBIZ-7948: That worked. Thanks. > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[
https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415759#comment-15415759
]
Pierre Smits edited comment on OFBIZ-7948 at 8/10/16 6:48 PM:
--
In order to have your component's build.gradle file compile the local external
libraries in the build process, please include
{code}
apply plugin:'java'
{code}
before the dependencies definition.
was (Author: pfm.smits):
In order to have your component's build.gradle file compile the local external
libraries in the build process, please include
{code]
apply plugin:'java'
{code}
before the dependencies definition.
> gradle does not recognize paths to 3rd party jars in hot-deploy components
> --
>
> Key: OFBIZ-7948
> URL: https://issues.apache.org/jira/browse/OFBIZ-7948
> Project: OFBiz
> Issue Type: Bug
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Wai
>
> I have a hot-deploy component. This component relies on 3rd party jars. I
> have added the paths to the 3rd party jars in the component's
> ofbiz-component.xml but the gradle build process complains about not being
> able to find symbols in those jars.
> This component used to build successfully with ant but now that ofbiz has
> switched to gradle, the build process fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[
https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415759#comment-15415759
]
Pierre Smits edited comment on OFBIZ-7948 at 8/10/16 6:48 PM:
--
In order to have your component's build.gradle file compile the local external
libraries in the build process, please include
{code]
apply plugin:'java'
{code}
before the dependencies definition.
was (Author: pfm.smits):
In order to have your component's build.gradle file compile the local external
libraries in the build process, please include
[code]
apply plugin:'java'
[code]
before the dependencies definition.
> gradle does not recognize paths to 3rd party jars in hot-deploy components
> --
>
> Key: OFBIZ-7948
> URL: https://issues.apache.org/jira/browse/OFBIZ-7948
> Project: OFBiz
> Issue Type: Bug
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Wai
>
> I have a hot-deploy component. This component relies on 3rd party jars. I
> have added the paths to the 3rd party jars in the component's
> ofbiz-component.xml but the gradle build process complains about not being
> able to find symbols in those jars.
> This component used to build successfully with ant but now that ofbiz has
> switched to gradle, the build process fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415759#comment-15415759 ] Pierre Smits commented on OFBIZ-7948: - In order to have your component's build.gradle file compile the local external libraries in the build process, please include [code] apply plugin:'java' [code] before the dependencies definition. > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7949) E-commerce : FTL formatting
Vaibhav Jain created OFBIZ-7949: --- Summary: E-commerce : FTL formatting Key: OFBIZ-7949 URL: https://issues.apache.org/jira/browse/OFBIZ-7949 Project: OFBiz Issue Type: Sub-task Components: specialpurpose/ecommerce Reporter: Vaibhav Jain Assignee: Vaibhav Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415356#comment-15415356 ] Wai commented on OFBIZ-7948: Following your instruction by placing the build.gradle into the hot-deploy component, I ran gradlew and received the following error. $ gradlew cleanAll FAILURE: Build failed with an exception. * Where: Build file '/home/me/workspace/ofbiz-trunk/hot-deploy/mycomponent/build.gradle' line: 3 * What went wrong: A problem occurred evaluating project ':hot-deploy:mycomponent'. > Could not find method compile() for arguments [file collection] on project > ':hot-deploy:mycomponent'. * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[
https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414991#comment-15414991
]
Pierre Smits commented on OFBIZ-7948:
-
If your hot-deploy component uses specific external libraries (e.g. when built
in house), you can include them in the build process. The way to do this is to
create a specific build.gradle file in your hot-deploy component with following
content:
{code}
dependencies {
//local file
compile files(/.jar)
}
{code},
where is the name of the folder within your hot-deploy component
where the external library resided (e.g. lib), and where
is the file name of the external library.
> gradle does not recognize paths to 3rd party jars in hot-deploy components
> --
>
> Key: OFBIZ-7948
> URL: https://issues.apache.org/jira/browse/OFBIZ-7948
> Project: OFBiz
> Issue Type: Bug
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Wai
>
> I have a hot-deploy component. This component relies on 3rd party jars. I
> have added the paths to the 3rd party jars in the component's
> ofbiz-component.xml but the gradle build process complains about not being
> able to find symbols in those jars.
> This component used to build successfully with ant but now that ofbiz has
> switched to gradle, the build process fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414551#comment-15414551 ] Wai edited comment on OFBIZ-7948 at 8/10/16 1:12 AM: - What if my component makes use of custom in-house jars. Where would one put these jars and how to configure gradle to look for them when compiling? Also how to configure ofbiz to look for these jars when it is run? was (Author: wt): What if my component makes use of custom in-house jars. Where would one put these jars and how to configure gradle to look for them? > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414551#comment-15414551 ] Wai commented on OFBIZ-7948: What if my component makes use of custom in-house jars. Where would one put these jars and how to configure gradle to look for them? > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414139#comment-15414139 ] Chris Howe commented on OFBIZ-7948: --- Because Gradle is caching the third party dependencies in the root of the application and not maintaining the jars for SVN/git, there is no need to keep the lib directory in your component. You should identify the dependency in the build.gradle file for your component and get rid of the lib directory all together. > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wai updated OFBIZ-7948: --- Summary: gradle does not recognize paths to 3rd party jars in hot-deploy components (was: ofbiz does not recognize paths of 3rd party jars in hot-deploy components) > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7948) ofbiz does not recognize paths of 3rd party jars in hot-deploy components
Wai created OFBIZ-7948: -- Summary: ofbiz does not recognize paths of 3rd party jars in hot-deploy components Key: OFBIZ-7948 URL: https://issues.apache.org/jira/browse/OFBIZ-7948 Project: OFBiz Issue Type: Bug Components: Gradle Affects Versions: Trunk Reporter: Wai I have a hot-deploy component. This component relies on 3rd party jars. I have added the paths to the 3rd party jars in the component's ofbiz-component.xml but the gradle build process complains about not being able to find symbols in those jars. This component used to build successfully with ant but now that ofbiz has switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7863) Ebay : FTL formatting
[ https://issues.apache.org/jira/browse/OFBIZ-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Jain updated OFBIZ-7863: Attachment: OFBIZ-7863.patch Thanks Pranay for reviewing the patch. Here is the updated patch > Ebay : FTL formatting > - > > Key: OFBIZ-7863 > URL: https://issues.apache.org/jira/browse/OFBIZ-7863 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/ebay >Reporter: Vaibhav Jain >Assignee: Vaibhav Jain > Attachments: OFBIZ-7863.patch, OFBIZ-7863.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7947) Create a Customer fails because password is missing
Montalbano Florian created OFBIZ-7947:
-
Summary: Create a Customer fails because password is missing
Key: OFBIZ-7947
URL: https://issues.apache.org/jira/browse/OFBIZ-7947
Project: OFBiz
Issue Type: Bug
Components: party
Affects Versions: Trunk
Reporter: Montalbano Florian
When creating a New Customer from the Party component, the following error
message is displayed :
{quote}
The Following Errors Occurred:
Password is Missing
Password or verify password missing.
{quote}
The problem is that there is no field to submit a password in the form. I have
an older revision where the required fields are displayed, so I'm guessing a
recent change is at cause here.
Step to reproduce :
- Access at the Customer creation form :
https://localhost:8443/partymgr/control/NewCustomer
- Try to create a Customer
- No field are related to the password requirement
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-5959) Add lifespan fields to PartyRole and dependency refactoring
[ https://issues.apache.org/jira/browse/OFBIZ-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15413013#comment-15413013 ] Pierre Smits commented on OFBIZ-5959: - new link: https://ofbiz-vm.apache.org:8443/partymgr/control/viewroles?partyId=admin > Add lifespan fields to PartyRole and dependency refactoring > --- > > Key: OFBIZ-5959 > URL: https://issues.apache.org/jira/browse/OFBIZ-5959 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits > Labels: role, roles > > Currently the assignments of roles to parties are boolean (there or not > there). > However, these role assignments also have a lifespan. This can be achieved by > adding fromDate and thruDate fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-5522) Introduce websocket usage
[ https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-5522: --- Comment: was deleted (was: We are all in dust world, so the clean power plan is useful for all.It is informative blog. powerplan is important for all. http://www.happydiwalismsmessages.in/ http://www.happydiwalismsmessages.in/2016/07/deepavali-greetings-messages-diwali-greetings.html http://www.happydiwalismsmessages.in/2015/10/happy-diwali-images-wallpaper-pictures-hd.html http://www.happydiwalismsmessages.in/2015/10/happy-diwali-2016-messages-sms-quotes-status.html) > Introduce websocket usage > - > > Key: OFBIZ-5522 > URL: https://issues.apache.org/jira/browse/OFBIZ-5522 > Project: OFBiz > Issue Type: Task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > > After a discussion with Ean, was suggested (draft here): > You need a service that lets you "subscribe" a widget to an entity and > then propagate change events to the widget as the entity is modified. > A generic mechanism like that could eventually expand to be a general > purpose "data bound widgets" system that mostly looks like the existing > system but magically reflects updates. > Could be used with/for > * The entity cache and webforms to automatically update views when data > changes. > * Replaces the current system notes > * Create a dashboard type pages (to be discussed futher) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
