[jira] [Commented] (OFBIZ-12166) Default ordering of webapps titles in main menu
[ https://issues.apache.org/jira/browse/OFBIZ-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284494#comment-17284494 ] ASF subversion and git services commented on OFBIZ-12166: - Commit e964d6172435db4be4870e09110576a68e33aafc in ofbiz-plugins's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=e964d61 ] Improved: Default ordering of webapps titles in main menu (OFBIZ-12166) This 1st step sorts the plugins. We need to discuss more... > Default ordering of webapps titles in main menu > --- > > Key: OFBIZ-12166 > URL: https://issues.apache.org/jira/browse/OFBIZ-12166 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > This follows https://markmail.org/message/ftgfpwztflty7klb, excerpt: > bq. [...] having more important apps in 1st places would be better [...] the > feature should be easily changed by custom projects [...] documentation for > that would be enough. > I propose this order: > 1. partymgr(because you need parties to do anything) > 2. catalog (because you need products to do anything) > 3. facility (because you need to store products to do anything) > 4. order (because it's there that things begin to "move") > 5. accounting (because it's there that things "end"; ar & ap should > disappear) > 6. content (because you need to associate contents to make things better) > 7. manufacturing (because OFBiz is also an ERP) > 8. sfa (because people are often looking for a CRM, BTW most them don't know > what SFA is) > 9. workeffort (this one could be above, but it's not obvious for most people) > 10. humanres (more important than below IMO) > 11. marketing (not sure about the place of this one) > 12. webtools (maybe higher?) > - (plugins start below) > 1. rest (could be named api soon) > 2. projectmgr > 3. webpos > 4. bi > 5. birt > 6. myportal > 7. assetmaint > 8. ismgr > 9. scrum > 10. solr > 11. ebay > 12. firstdata > 13. - (those are special, maybe above?) > 14. example > 15. exampleext > - (those plugins don't show atm but exist, maybe need more info > from backend menu?) > 1. ecommerce > 2. ecomseo > 3. multiflex > 4. cmssite > 5. ebaystore > 6. ldap > 7. lucene > 8. passport > 9. pricat > 10. msggateway -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12166) Default ordering of webapps titles in main menu
[ https://issues.apache.org/jira/browse/OFBIZ-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284493#comment-17284493 ] ASF subversion and git services commented on OFBIZ-12166: - Commit a2dac5482cc7aa4049dce59e6551b5702549659a in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=a2dac54 ] Improved: Default ordering of webapps titles in main menu (OFBIZ-12166) [...] having more important apps in 1st places would be better [...] the feature should be easily changed by custom projects [...] documentation for that would be enough. This 1st step sorts the applications and webtools. I believe webtools should not be secondary but that needs to be discussed with other options. > Default ordering of webapps titles in main menu > --- > > Key: OFBIZ-12166 > URL: https://issues.apache.org/jira/browse/OFBIZ-12166 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > This follows https://markmail.org/message/ftgfpwztflty7klb, excerpt: > bq. [...] having more important apps in 1st places would be better [...] the > feature should be easily changed by custom projects [...] documentation for > that would be enough. > I propose this order: > 1. partymgr(because you need parties to do anything) > 2. catalog (because you need products to do anything) > 3. facility (because you need to store products to do anything) > 4. order (because it's there that things begin to "move") > 5. accounting (because it's there that things "end"; ar & ap should > disappear) > 6. content (because you need to associate contents to make things better) > 7. manufacturing (because OFBiz is also an ERP) > 8. sfa (because people are often looking for a CRM, BTW most them don't know > what SFA is) > 9. workeffort (this one could be above, but it's not obvious for most people) > 10. humanres (more important than below IMO) > 11. marketing (not sure about the place of this one) > 12. webtools (maybe higher?) > - (plugins start below) > 1. rest (could be named api soon) > 2. projectmgr > 3. webpos > 4. bi > 5. birt > 6. myportal > 7. assetmaint > 8. ismgr > 9. scrum > 10. solr > 11. ebay > 12. firstdata > 13. - (those are special, maybe above?) > 14. example > 15. exampleext > - (those plugins don't show atm but exist, maybe need more info > from backend menu?) > 1. ecommerce > 2. ecomseo > 3. multiflex > 4. cmssite > 5. ebaystore > 6. ldap > 7. lucene > 8. passport > 9. pricat > 10. msggateway -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-12176) webapp position does not really work
[ https://issues.apache.org/jira/browse/OFBIZ-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-12176. --- Fix Version/s: Upcoming Branch Resolution: Fixed Too hard to backport to my taste... > webapp position does not really work > > > Key: OFBIZ-12176 > URL: https://issues.apache.org/jira/browse/OFBIZ-12176 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > The current implementation of webapp position uses String as key. You can't > really order on String, you need numbers. > This is needed by OFBIZ-12166 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12166) Default ordering of webapps titles in main menu
[ https://issues.apache.org/jira/browse/OFBIZ-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284472#comment-17284472 ] Jacques Le Roux commented on OFBIZ-12166: - Because I need numbers here a realistic usable version of the description # partymgr(because you need parties to do anything) # catalog (because you need products to do anything) # facility (because you need to store products to do anything) # order (because it's there that things begin to "move") # accounting (because it's there that things "end"; ar & ap should disappear) # content (because you need to associate contents to make things better) # manufacturing (because OFBiz is also an ERP) # sfa (because people are often looking for a CRM, BTW most them don't know what SFA is) # workeffort (this one could be above, but it's not obvious for most people) # humanres (more important than below IMO) # marketing (not sure about the place of this one) # webtools (maybe higher?) # rest (could be named api soon) # projectmgr # webpos # bi # birt # myportal # assetmaint # ismgr # scrum # solr # ebay # firstdata # example # exampleext > Default ordering of webapps titles in main menu > --- > > Key: OFBIZ-12166 > URL: https://issues.apache.org/jira/browse/OFBIZ-12166 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > This follows https://markmail.org/message/ftgfpwztflty7klb, excerpt: > bq. [...] having more important apps in 1st places would be better [...] the > feature should be easily changed by custom projects [...] documentation for > that would be enough. > I propose this order: > 1. partymgr(because you need parties to do anything) > 2. catalog (because you need products to do anything) > 3. facility (because you need to store products to do anything) > 4. order (because it's there that things begin to "move") > 5. accounting (because it's there that things "end"; ar & ap should > disappear) > 6. content (because you need to associate contents to make things better) > 7. manufacturing (because OFBiz is also an ERP) > 8. sfa (because people are often looking for a CRM, BTW most them don't know > what SFA is) > 9. workeffort (this one could be above, but it's not obvious for most people) > 10. humanres (more important than below IMO) > 11. marketing (not sure about the place of this one) > 12. webtools (maybe higher?) > - (plugins start below) > 1. rest (could be named api soon) > 2. projectmgr > 3. webpos > 4. bi > 5. birt > 6. myportal > 7. assetmaint > 8. ismgr > 9. scrum > 10. solr > 11. ebay > 12. firstdata > 13. - (those are special, maybe above?) > 14. example > 15. exampleext > - (those plugins don't show atm but exist, maybe need more info > from backend menu?) > 1. ecommerce > 2. ecomseo > 3. multiflex > 4. cmssite > 5. ebaystore > 6. ldap > 7. lucene > 8. passport > 9. pricat > 10. msggateway -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12166) Default ordering of webapps titles in main menu
[ https://issues.apache.org/jira/browse/OFBIZ-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284471#comment-17284471 ] ASF subversion and git services commented on OFBIZ-12166: - Commit 568ac8927bd74d83cd099a5d0fd59dd06a595b26 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=568ac89 ] Fixed: webapp position does not really work (OFBIZ-12176) The current implementation of webapp position uses String as key. You can't really order on String, you need numbers. This is needed by OFBIZ-12166 > Default ordering of webapps titles in main menu > --- > > Key: OFBIZ-12166 > URL: https://issues.apache.org/jira/browse/OFBIZ-12166 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > This follows https://markmail.org/message/ftgfpwztflty7klb, excerpt: > bq. [...] having more important apps in 1st places would be better [...] the > feature should be easily changed by custom projects [...] documentation for > that would be enough. > I propose this order: > 1. partymgr(because you need parties to do anything) > 2. catalog (because you need products to do anything) > 3. facility (because you need to store products to do anything) > 4. order (because it's there that things begin to "move") > 5. accounting (because it's there that things "end"; ar & ap should > disappear) > 6. content (because you need to associate contents to make things better) > 7. manufacturing (because OFBiz is also an ERP) > 8. sfa (because people are often looking for a CRM, BTW most them don't know > what SFA is) > 9. workeffort (this one could be above, but it's not obvious for most people) > 10. humanres (more important than below IMO) > 11. marketing (not sure about the place of this one) > 12. webtools (maybe higher?) > - (plugins start below) > 1. rest (could be named api soon) > 2. projectmgr > 3. webpos > 4. bi > 5. birt > 6. myportal > 7. assetmaint > 8. ismgr > 9. scrum > 10. solr > 11. ebay > 12. firstdata > 13. - (those are special, maybe above?) > 14. example > 15. exampleext > - (those plugins don't show atm but exist, maybe need more info > from backend menu?) > 1. ecommerce > 2. ecomseo > 3. multiflex > 4. cmssite > 5. ebaystore > 6. ldap > 7. lucene > 8. passport > 9. pricat > 10. msggateway -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12176) webapp position does not really work
[ https://issues.apache.org/jira/browse/OFBIZ-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284470#comment-17284470 ] ASF subversion and git services commented on OFBIZ-12176: - Commit 568ac8927bd74d83cd099a5d0fd59dd06a595b26 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=568ac89 ] Fixed: webapp position does not really work (OFBIZ-12176) The current implementation of webapp position uses String as key. You can't really order on String, you need numbers. This is needed by OFBIZ-12166 > webapp position does not really work > > > Key: OFBIZ-12176 > URL: https://issues.apache.org/jira/browse/OFBIZ-12176 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > > The current implementation of webapp position uses String as key. You can't > really order on String, you need numbers. > This is needed by OFBIZ-12166 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12176) webapp position does not really work
Jacques Le Roux created OFBIZ-12176: --- Summary: webapp position does not really work Key: OFBIZ-12176 URL: https://issues.apache.org/jira/browse/OFBIZ-12176 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux The current implementation of webapp position uses String as key. You can't really order on String, you need numbers. This is needed by OFBIZ-12166 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10351) Tree View of Call Graph for Services and Simple Methods
[ https://issues.apache.org/jira/browse/OFBIZ-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284440#comment-17284440 ] James Yong commented on OFBIZ-10351: Hi Michael, I haven't started on the suggestions from Jacques & Taher. For my use-case, I wanted the call graph to include services that are programmatically called from groovy, simple method or java codes during a request. Understand the call graph is only used during development and will be turned off in production. If there is performance concern, I will not continue with this JIRA issue then. > Tree View of Call Graph for Services and Simple Methods > --- > > Key: OFBIZ-10351 > URL: https://issues.apache.org/jira/browse/OFBIZ-10351 > Project: OFBiz > Issue Type: Improvement > Components: base >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10351.patch, OFBIZ-10351.patch, OFBIZ-10351.patch, > OFBIZ-10351.patch, OFBIZ-10351.patch > > > Option to log a tree view of services and simple methods, and events that are > called in a request. > Some discussion at > https://lists.apache.org/thread.html/079455a596056334265ecbd410b4de13b6e61e1449ac258af5e9679b@%3Cdev.ofbiz.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284399#comment-17284399 ] Michael Brohl edited comment on OFBIZ-12171 at 2/14/21, 3:52 PM: - I've also started with the migration for 17.12, which will be tougher because of the Gradle version used there. There is no metadataSources API to specify to pull a jar without a pom, which is used for the flute dependency. Does someone know how to correct a pom in maven central? This is the reason why metadataSources API was used for trunk and r18.12. Or does someone know a way to pull artefacts/jars from a repository without a valid pom in Gradle 3.2.1? Any help is appreciated, thanks! was (Author: mbrohl): I've also started with the migration for 17.12, which will be tougher because of the Gradle version used there. There is no metadataSources API to specify to pull a jar without a pom, which is used for the flute dependency. Does someone know how to correct a pom in maven central? This is the reason why metadateSources was used for trunk and r18.12. > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: Upcoming Branch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10351) Tree View of Call Graph for Services and Simple Methods
[ https://issues.apache.org/jira/browse/OFBIZ-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284428#comment-17284428 ] Michael Brohl commented on OFBIZ-10351: --- Hi James, are those newer patches considering the valid feedback from Taher? I feel a little uneasy to touch those core logic too, as this could also be a performance issue doing all the checks for logging. Considering the latest requirement to trace the service callstack (Danny Trunk), what about writing some functionality which inspect the code from outside, not during runtime. The code, eca, seca etc. could easily be parsed to show how services are used in the codebase, maybe also with a nice html output. This way we would have no runtime impact for a logic which, IMO, will not be used that much. > Tree View of Call Graph for Services and Simple Methods > --- > > Key: OFBIZ-10351 > URL: https://issues.apache.org/jira/browse/OFBIZ-10351 > Project: OFBiz > Issue Type: Improvement > Components: base >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10351.patch, OFBIZ-10351.patch, OFBIZ-10351.patch, > OFBIZ-10351.patch, OFBIZ-10351.patch > > > Option to log a tree view of services and simple methods, and events that are > called in a request. > Some discussion at > https://lists.apache.org/thread.html/079455a596056334265ecbd410b4de13b6e61e1449ac258af5e9679b@%3Cdev.ofbiz.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10351) Tree View of Call Graph for Services and Simple Methods
[ https://issues.apache.org/jira/browse/OFBIZ-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284420#comment-17284420 ] James Yong commented on OFBIZ-10351: Updated the patch to include async, SECA, EECA and MCA > Tree View of Call Graph for Services and Simple Methods > --- > > Key: OFBIZ-10351 > URL: https://issues.apache.org/jira/browse/OFBIZ-10351 > Project: OFBiz > Issue Type: Improvement > Components: base >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10351.patch, OFBIZ-10351.patch, OFBIZ-10351.patch, > OFBIZ-10351.patch, OFBIZ-10351.patch > > > Option to log a tree view of services and simple methods, and events that are > called in a request. > Some discussion at > https://lists.apache.org/thread.html/079455a596056334265ecbd410b4de13b6e61e1449ac258af5e9679b@%3Cdev.ofbiz.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10351) Tree View of Call Graph for Services and Simple Methods
[ https://issues.apache.org/jira/browse/OFBIZ-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Yong updated OFBIZ-10351: --- Attachment: OFBIZ-10351.patch > Tree View of Call Graph for Services and Simple Methods > --- > > Key: OFBIZ-10351 > URL: https://issues.apache.org/jira/browse/OFBIZ-10351 > Project: OFBiz > Issue Type: Improvement > Components: base >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10351.patch, OFBIZ-10351.patch, OFBIZ-10351.patch, > OFBIZ-10351.patch, OFBIZ-10351.patch > > > Option to log a tree view of services and simple methods, and events that are > called in a request. > Some discussion at > https://lists.apache.org/thread.html/079455a596056334265ecbd410b4de13b6e61e1449ac258af5e9679b@%3Cdev.ofbiz.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284399#comment-17284399 ] Michael Brohl commented on OFBIZ-12171: --- I've also started with the migration for 17.12, which will be tougher because of the Gradle version used there. There is no metadataSources API to specify to pull a jar without a pom, which is used for the flute dependency. Does someone know how to correct a pom in maven central? This is the reason why metadateSources was used for trunk and r18.12. > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: Upcoming Branch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284393#comment-17284393 ] Jacques Le Roux commented on OFBIZ-12171: - Since it's the same fix than in trunk, I trust it's OK: +1 for commit (we will see there if there is any issues anyway) > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: Upcoming Branch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [ofbiz-framework] sonarcloud[bot] commented on pull request #276: Improved: Switch from jCenter to mavenCentral to handle the jCenter shutdown (OFBIZ-12171)
sonarcloud[bot] commented on pull request #276: URL: https://github.com/apache/ofbiz-framework/pull/276#issuecomment-778756132 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-framework=276=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-framework=276=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-framework=276=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=276) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=276=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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [ofbiz-framework] sonarcloud[bot] removed a comment on pull request #276: Improved: Switch from jCenter to mavenCentral to handle the jCenter shutdown (OFBIZ-12171)
sonarcloud[bot] removed a comment on pull request #276: URL: https://github.com/apache/ofbiz-framework/pull/276#issuecomment-778697685 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-framework=276=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-framework=276=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_ofbiz-framework=276=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=276=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=276) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=276=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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown
[ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284382#comment-17284382 ] Michael Brohl commented on OFBIZ-12171: --- Sorry Jacques, I forgot to run the integrations tests, was late tonight... Should now be fixed, the tests pass on my local installation. > Handling the JCenter shutdown > - > > Key: OFBIZ-12171 > URL: https://issues.apache.org/jira/browse/OFBIZ-12171 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS >Affects Versions: Release Branch 18.12, Trunk, 17.12.05 >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Major > Labels: backport-needed > Fix For: Upcoming Branch > > > Citing Taher's message at [2]: > Hello Everyone, > > I received emails and checked resources [1] that seem to confirm JCenter from > JFrog is going down and that the last day of operation for the repository is > going to be May 1st 2021. > > This is a big deal as many running instances will crash unless updated, so > not only do future versions of OFBiz need to adapt, but also existing > installations. > > I'm not sure how to best handle this? Especially for production instances out > there on older versions of OFBiz. Maybe one solution is to host the existing > libraries in some temporary location or try to migrate them to MavenCentral > ... Whatever is the solution I think we should make a fast move. > > [1] > [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter] > > [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure] > [2] > [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
