[jira] [Comment Edited] (OFBIZ-12808) Eclipse build problems and proper dependency setup
[ https://issues.apache.org/jira/browse/OFBIZ-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715071#comment-17715071 ] Jacques Le Roux edited comment on OFBIZ-12808 at 4/21/23 4:32 PM: -- Thanks Michael, All compile, no import issues (AFAIK) and works here (UI). I'd just warn people using {{org.eclipse.jdt.core.compiler.ignoreUnnamedModuleForSplitPackage=enabled}} in {{.settings}} to remove it before applying the patches (or updating later); using gradlew eclipse is a solution. I'm not sure but it else seems to freeze Eclipse or makes it VERy, VEry, Very slow. was (Author: jacques.le.roux): Thanks Michael, All compile, no import issues (AFAIK) and works here (UI). I'd just warn people using {{org.eclipse.jdt.core.compiler.ignoreUnnamedModuleForSplitPackage=enabled}} in {{.settings}} to remove it before applying the patches (or updating later); using gralew eclipse is a solution. I'm not sure but it else seems to freeze Eclipse or makes it VERy, VEry, Very slow. > Eclipse build problems and proper dependency setup > -- > > Key: OFBIZ-12808 > URL: https://issues.apache.org/jira/browse/OFBIZ-12808 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Fix For: 22.01.01, Upcoming Branch > > > Due to improper dependency configurations and the JPMS (Java Plattform Module > System) which was introduced to Java since version 9, the Eclipse build and > running/debugging is not working with JDK 17 (trunk and release22.01). > The reason is that there are dependencies to libraries which are also shipped > with the JDK which causes a conflict leading to ignore those packages/classes > in the build. > We have a working solution for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12808) Eclipse build problems and proper dependency setup
[ https://issues.apache.org/jira/browse/OFBIZ-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715071#comment-17715071 ] Jacques Le Roux commented on OFBIZ-12808: - Thanks Michael, All compile, no import issues (AFAIK) and works here (UI). I'd just warn people using {{org.eclipse.jdt.core.compiler.ignoreUnnamedModuleForSplitPackage=enabled}} in {{.settings}} to remove it before applying the patches (or updating later); using gralew eclipse is a solution. I'm not sure but it else seems to freeze Eclipse or makes it VERy, VEry, Very slow. > Eclipse build problems and proper dependency setup > -- > > Key: OFBIZ-12808 > URL: https://issues.apache.org/jira/browse/OFBIZ-12808 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Fix For: 22.01.01, Upcoming Branch > > > Due to improper dependency configurations and the JPMS (Java Plattform Module > System) which was introduced to Java since version 9, the Eclipse build and > running/debugging is not working with JDK 17 (trunk and release22.01). > The reason is that there are dependencies to libraries which are also shipped > with the JDK which causes a conflict leading to ignore those packages/classes > in the build. > We have a working solution for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12810) BuildBot status Badge, use a link to BuildBot pages rather than to images
[ https://issues.apache.org/jira/browse/OFBIZ-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715067#comment-17715067 ] Jacques Le Roux commented on OFBIZ-12810: - Unfortunately not, as you can check. There are only badges for success, failure and errors builds IIRW. Moreover if you look at [ofbizTrunkFrameworkRat|https://ci2.apache.org/#/builders/51] you will see that it never fails. Same for other RAT builders: https://ci2.apache.org/#/builders/50 and https://ci2.apache.org/#/builders/52 (except initial config errors of mine) Once the builder is OK, only the information in the result page change, for instance: https://nightlies.apache.org/ofbiz/trunk/rat-output.html BTW could you please fix the missing, or not needed, ASL2 licences headers in trunk and 22.01? Remember that some files don't need a header, or it's the problem to put one there. You can then use https://github.com/apache/ofbiz-tools/blob/master/rat-excludes.txt > BuildBot status Badge, use a link to BuildBot pages rather than to images > - > > Key: OFBIZ-12810 > URL: https://issues.apache.org/jira/browse/OFBIZ-12810 > Project: OFBiz > Issue Type: Bug > Components: BuildBot >Affects Versions: 22.01.01 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 22.01.01 > > > At https://lists.apache.org/thread/8r81mbyg8291g0j2qlth3mttd3hosdg9 Daniel > rightly suggested to link from main README file to BuildBot pages rather than > to badges images that give no real information -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12808) Eclipse build problems and proper dependency setup
[ https://issues.apache.org/jira/browse/OFBIZ-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714999#comment-17714999 ] Daniel Watford commented on OFBIZ-12808: Hi [~mbrohl] , Would a non-eclipse user be able to recognise if they introduce the same sort of issue again, perhaps by adding new dependencies to plugins? Is it something the gradle could detect and use to deliberately fail a build? > Eclipse build problems and proper dependency setup > -- > > Key: OFBIZ-12808 > URL: https://issues.apache.org/jira/browse/OFBIZ-12808 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Fix For: 22.01.01, Upcoming Branch > > > Due to improper dependency configurations and the JPMS (Java Plattform Module > System) which was introduced to Java since version 9, the Eclipse build and > running/debugging is not working with JDK 17 (trunk and release22.01). > The reason is that there are dependencies to libraries which are also shipped > with the JDK which causes a conflict leading to ignore those packages/classes > in the build. > We have a working solution for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12808) Eclipse build problems and proper dependency setup
[ https://issues.apache.org/jira/browse/OFBIZ-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714986#comment-17714986 ] Michael Brohl commented on OFBIZ-12808: --- Fixes for framework / plugins for trunk and release22.01 are now in the pull requests. To test, the corresponding pr's for framework and plugins have to be checked out respectively. > Eclipse build problems and proper dependency setup > -- > > Key: OFBIZ-12808 > URL: https://issues.apache.org/jira/browse/OFBIZ-12808 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Fix For: 22.01.01, Upcoming Branch > > > Due to improper dependency configurations and the JPMS (Java Plattform Module > System) which was introduced to Java since version 9, the Eclipse build and > running/debugging is not working with JDK 17 (trunk and release22.01). > The reason is that there are dependencies to libraries which are also shipped > with the JDK which causes a conflict leading to ignore those packages/classes > in the build. > We have a working solution for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [ofbiz-plugins] sonarcloud[bot] commented on pull request #82: Fixed: Eclipse build problems and proper dependency setup (OFBIZ-12808)
sonarcloud[bot] commented on PR #82: URL: https://github.com/apache/ofbiz-plugins/pull/82#issuecomment-1517792722 Kudos, SonarCloud Quality Gate passed! [![Quality Gate passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/passed-16px.png 'Quality Gate passed')](https://sonarcloud.io/dashboard?id=apache_ofbiz-plugins=82) [![Bug](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/bug-16px.png 'Bug')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=82=false=BUG) [![A](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/RatingBadge/A-16px.png 'A')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=82=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=82=false=BUG) [![Vulnerability](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/vulnerability-16px.png 'Vulnerability')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=82=false=VULNERABILITY) [![A](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/RatingBadge/A-16px.png 'A')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=82=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=82=false=VULNERABILITY) [![Security Hotspot](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/security_hotspot-16px.png 'Security Hotspot')](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-plugins=82=false=SECURITY_HOTSPOT) [![A](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/RatingBadge/A-16px.png 'A')](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-plugins=82=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-plugins=82=false=SECURITY_HOTSPOT) [![Code Smell](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/code_smell-16px.png 'Code Smell')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=82=false=CODE_SMELL) [![A](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/RatingBadge/A-16px.png 'A')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=82=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=82=false=CODE_SMELL) [![No Coverage information](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/CoverageChart/NoCoverageInfo-16px.png 'No Coverage information')](https://sonarcloud.io/component_measures?id=apache_ofbiz-plugins=82) No Coverage information [![No Duplication information](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/Duplications/NoDuplicationInfo-16px.png 'No Duplication information')](https://sonarcloud.io/component_measures?id=apache_ofbiz-plugins=82=duplicated_lines_density=list) No Duplication information -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@ofbiz.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [ofbiz-plugins] mbrohl opened a new pull request, #82: Fixed: Eclipse build problems and proper dependency setup (OFBIZ-12808)
mbrohl opened a new pull request, #82: URL: https://github.com/apache/ofbiz-plugins/pull/82 Due to improper dependency configurations and the JPMS (Java Plattform Module System) which was introduced to Java since version 9, the Eclipse build and running/debugging is not working with JDK 17 (trunk and release22.01). The reason is that there are dependencies to libraries which are also shipped with the JDK which causes a conflict leading to ignore those packages/classes in the build. This commit fixes the problems for the trunk plugins. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@ofbiz.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [ofbiz-plugins] sonarcloud[bot] commented on pull request #81: Fixed: Eclipse build problems and proper dependency setup (OFBIZ-12808)
sonarcloud[bot] commented on PR #81: URL: https://github.com/apache/ofbiz-plugins/pull/81#issuecomment-1517764765 Kudos, SonarCloud Quality Gate passed! [![Quality Gate passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/passed-16px.png 'Quality Gate passed')](https://sonarcloud.io/dashboard?id=apache_ofbiz-plugins=81) [![Bug](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/bug-16px.png 'Bug')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=81=false=BUG) [![A](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/RatingBadge/A-16px.png 'A')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=81=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=81=false=BUG) [![Vulnerability](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/vulnerability-16px.png 'Vulnerability')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=81=false=VULNERABILITY) [![A](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/RatingBadge/A-16px.png 'A')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=81=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=81=false=VULNERABILITY) [![Security Hotspot](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/security_hotspot-16px.png 'Security Hotspot')](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-plugins=81=false=SECURITY_HOTSPOT) [![A](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/RatingBadge/A-16px.png 'A')](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-plugins=81=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-plugins=81=false=SECURITY_HOTSPOT) [![Code Smell](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/code_smell-16px.png 'Code Smell')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=81=false=CODE_SMELL) [![A](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/RatingBadge/A-16px.png 'A')](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=81=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_ofbiz-plugins=81=false=CODE_SMELL) [![No Coverage information](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/CoverageChart/NoCoverageInfo-16px.png 'No Coverage information')](https://sonarcloud.io/component_measures?id=apache_ofbiz-plugins=81) No Coverage information [![No Duplication information](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/Duplications/NoDuplicationInfo-16px.png 'No Duplication information')](https://sonarcloud.io/component_measures?id=apache_ofbiz-plugins=81=duplicated_lines_density=list) No Duplication information -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@ofbiz.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [ofbiz-plugins] mbrohl opened a new pull request, #81: Fixed: Eclipse build problems and proper dependency setup (OFBIZ-12808)
mbrohl opened a new pull request, #81: URL: https://github.com/apache/ofbiz-plugins/pull/81 Due to improper dependency configurations and the JPMS (Java Plattform Module System) which was introduced to Java since version 9, the Eclipse build and running/debugging is not working with JDK 17 (trunk and release22.01). The reason is that there are dependencies to libraries which are also shipped with the JDK which causes a conflict leading to ignore those packages/classes in the build. This commit fixes the problems for the release22.01 plugins. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@ofbiz.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12664: Assignee: (was: Mekika Leila) > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=9000] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12810) BuildBot status Badge, use a link to BuildBot pages rather than to images
[ https://issues.apache.org/jira/browse/OFBIZ-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-12810. --- Resolution: Fixed > BuildBot status Badge, use a link to BuildBot pages rather than to images > - > > Key: OFBIZ-12810 > URL: https://issues.apache.org/jira/browse/OFBIZ-12810 > Project: OFBiz > Issue Type: Bug > Components: BuildBot >Affects Versions: 22.01.01 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 22.01.01 > > > At https://lists.apache.org/thread/8r81mbyg8291g0j2qlth3mttd3hosdg9 Daniel > rightly suggested to link from main README file to BuildBot pages rather than > to badges images that give no real information -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12810) BuildBot status Badge, use a link to BuildBot pages rather than to images
[ https://issues.apache.org/jira/browse/OFBIZ-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714966#comment-17714966 ] Daniel Watford commented on OFBIZ-12810: Hi [~jleroux] , I think I may be misunderstanding your message - apologies if that is the case. I haven't found any documentation regarding the implementation of build status badges, but I would have expected every builder to have its own build status badge. Based on the URL in README.adoc, I would have thought individual badges would be accessible for the various OFBiz builds at: * [https://ci2.apache.org/badges/ofbizTrunkFramework.svg] * [https://ci2.apache.org/badges/ofbizTrunkFrameworkPlugins.svg|https://ci2.apache.org/badges/ofbizTrunkFramework.svg] * [https://ci2.apache.org/badges/ofbizTrunkFrameworkRat.svg|https://ci2.apache.org/badges/ofbizTrunkFramework.svg] * [https://ci2.apache.org/badges/ofbizBranch22Framework.svg|https://ci2.apache.org/badges/ofbizTrunkFramework.svg] * [https://ci2.apache.org/badges/ofbizBranch22FrameworkPlugins.svg|https://ci2.apache.org/badges/ofbizTrunkFramework.svg] * ... etc ... > BuildBot status Badge, use a link to BuildBot pages rather than to images > - > > Key: OFBIZ-12810 > URL: https://issues.apache.org/jira/browse/OFBIZ-12810 > Project: OFBiz > Issue Type: Bug > Components: BuildBot >Affects Versions: 22.01.01 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 22.01.01 > > > At https://lists.apache.org/thread/8r81mbyg8291g0j2qlth3mttd3hosdg9 Daniel > rightly suggested to link from main README file to BuildBot pages rather than > to badges images that give no real information -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12664: Assignee: Mekika Leila > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=9000] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12810) BuildBot status Badge, use a link to BuildBot pages rather than to images
[ https://issues.apache.org/jira/browse/OFBIZ-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714962#comment-17714962 ] Jacques Le Roux commented on OFBIZ-12810: - Mmm, I remember something now. There is no (easy?) mean to know if a RAT build has succeeded or not, but to get to the RAT page. I had a conversation about that at (and related) RAT-256 > BuildBot status Badge, use a link to BuildBot pages rather than to images > - > > Key: OFBIZ-12810 > URL: https://issues.apache.org/jira/browse/OFBIZ-12810 > Project: OFBiz > Issue Type: Bug > Components: BuildBot >Affects Versions: 22.01.01 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 22.01.01 > > > At https://lists.apache.org/thread/8r81mbyg8291g0j2qlth3mttd3hosdg9 Daniel > rightly suggested to link from main README file to BuildBot pages rather than > to badges images that give no real information -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-12810) BuildBot status Badge, use a link to BuildBot pages rather than to images
[ https://issues.apache.org/jira/browse/OFBIZ-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714958#comment-17714958 ] Jacques Le Roux edited comment on OFBIZ-12810 at 4/21/23 11:42 AM: --- Actually, as we can see for RAT and 22.01 branch the BB badges are all the same. Hence a new section I'll had for RAT just below the badges. But you are right, for the sake of consistence, I'll will change that. was (Author: jacques.le.roux): Actually, as we can see for RAT and 22.01 branch they are all the same. Hence a new section I'll had for RAT just below the badges. But you are right, for the sake of consistence, I'll will change that. > BuildBot status Badge, use a link to BuildBot pages rather than to images > - > > Key: OFBIZ-12810 > URL: https://issues.apache.org/jira/browse/OFBIZ-12810 > Project: OFBiz > Issue Type: Bug > Components: BuildBot >Affects Versions: 22.01.01 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 22.01.01 > > > At https://lists.apache.org/thread/8r81mbyg8291g0j2qlth3mttd3hosdg9 Daniel > rightly suggested to link from main README file to BuildBot pages rather than > to badges images that give no real information -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12810) BuildBot status Badge, use a link to BuildBot pages rather than to images
[ https://issues.apache.org/jira/browse/OFBIZ-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714958#comment-17714958 ] Jacques Le Roux commented on OFBIZ-12810: - Actually, as we can see for RAT and 22.01 branch they are all the same. Hence a new section I'll had for RAT just below the badges. But you are right, for the sake of consistence, I'll will change that. > BuildBot status Badge, use a link to BuildBot pages rather than to images > - > > Key: OFBIZ-12810 > URL: https://issues.apache.org/jira/browse/OFBIZ-12810 > Project: OFBiz > Issue Type: Bug > Components: BuildBot >Affects Versions: 22.01.01 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 22.01.01 > > > At https://lists.apache.org/thread/8r81mbyg8291g0j2qlth3mttd3hosdg9 Daniel > rightly suggested to link from main README file to BuildBot pages rather than > to badges images that give no real information -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12808) Eclipse build problems and proper dependency setup
[ https://issues.apache.org/jira/browse/OFBIZ-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714953#comment-17714953 ] Michael Brohl commented on OFBIZ-12808: --- Thanks Jacques. We are working on the dependency problems for plugins so the framework build configuration can possibly change in the course. > Eclipse build problems and proper dependency setup > -- > > Key: OFBIZ-12808 > URL: https://issues.apache.org/jira/browse/OFBIZ-12808 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Fix For: 22.01.01, Upcoming Branch > > > Due to improper dependency configurations and the JPMS (Java Plattform Module > System) which was introduced to Java since version 9, the Eclipse build and > running/debugging is not working with JDK 17 (trunk and release22.01). > The reason is that there are dependencies to libraries which are also shipped > with the JDK which causes a conflict leading to ignore those packages/classes > in the build. > We have a working solution for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (OFBIZ-12810) BuildBot status Badge, use a link to BuildBot pages rather than to images
[ https://issues.apache.org/jira/browse/OFBIZ-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Watford reopened OFBIZ-12810: Hi [~jleroux] , The SVG image for the badge refers to the ofbiz-framework build, but the link points to the framework+plugins build. These should match. > BuildBot status Badge, use a link to BuildBot pages rather than to images > - > > Key: OFBIZ-12810 > URL: https://issues.apache.org/jira/browse/OFBIZ-12810 > Project: OFBiz > Issue Type: Bug > Components: BuildBot >Affects Versions: 22.01.01 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 22.01.01 > > > At https://lists.apache.org/thread/8r81mbyg8291g0j2qlth3mttd3hosdg9 Daniel > rightly suggested to link from main README file to BuildBot pages rather than > to badges images that give no real information -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12810) BuildBot status Badge, use a link to BuildBot pages rather than to images
[ https://issues.apache.org/jira/browse/OFBIZ-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-12810. --- Resolution: Fixed > BuildBot status Badge, use a link to BuildBot pages rather than to images > - > > Key: OFBIZ-12810 > URL: https://issues.apache.org/jira/browse/OFBIZ-12810 > Project: OFBiz > Issue Type: Bug > Components: BuildBot >Affects Versions: 22.01.01 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 22.01.01 > > > At https://lists.apache.org/thread/8r81mbyg8291g0j2qlth3mttd3hosdg9 Daniel > rightly suggested to link from main README file to BuildBot pages rather than > to badges images that give no real information -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12808) Eclipse build problems and proper dependency setup
[ https://issues.apache.org/jira/browse/OFBIZ-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714872#comment-17714872 ] Jacques Le Roux commented on OFBIZ-12808: - +1 trunk works for me, a quick glance at 22.01 seems good. > Eclipse build problems and proper dependency setup > -- > > Key: OFBIZ-12808 > URL: https://issues.apache.org/jira/browse/OFBIZ-12808 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Fix For: 22.01.01, Upcoming Branch > > > Due to improper dependency configurations and the JPMS (Java Plattform Module > System) which was introduced to Java since version 9, the Eclipse build and > running/debugging is not working with JDK 17 (trunk and release22.01). > The reason is that there are dependencies to libraries which are also shipped > with the JDK which causes a conflict leading to ignore those packages/classes > in the build. > We have a working solution for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12810) BuildBot status Badge, use a link to BuildBot pages rather than to images
Jacques Le Roux created OFBIZ-12810: --- Summary: BuildBot status Badge, use a link to BuildBot pages rather than to images Key: OFBIZ-12810 URL: https://issues.apache.org/jira/browse/OFBIZ-12810 Project: OFBiz Issue Type: Bug Components: BuildBot Affects Versions: 22.01.01 Reporter: Jacques Le Roux Assignee: Jacques Le Roux Fix For: 22.01.01 At https://lists.apache.org/thread/8r81mbyg8291g0j2qlth3mttd3hosdg9 Daniel rightly suggested to link from main README file to BuildBot pages rather than to badges images that give no real information -- This message was sent by Atlassian Jira (v8.20.10#820010)