Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-3337

Investigate replacing Jidesoft classes with similar classes

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      After removing Jidesoft from IGB project, find out if we can use other libraries that could replace it and create a new classes with the same name as Jidesoft components and extend classes from the new libraries .

        Attachments

          Issue Links

            Activity

            Hide
            karthik Karthik Raveendran added a comment -

            Note: Reference for migrating Felix annotations to OSGI v6 annotations https://medium.com/globant/declarative-services-from-felix-scr-to-osgi-4770509f1965

            Show
            karthik Karthik Raveendran added a comment - Note: Reference for migrating Felix annotations to OSGI v6 annotations https://medium.com/globant/declarative-services-from-felix-scr-to-osgi-4770509f1965
            Hide
            karthik Karthik Raveendran added a comment -

            To identify the issues in opening the application GUI, I want to run the project in the debug mode in Intellij. Although all the IGB bundles is running through terminal for Java 11, when I try to run the project in Intellij debug mode to identify the problem a Felix SCR Processing error is thrown. After disabling the processing, a google guava issue persists,

            java: cannot find symbol
              symbol:   method arbitrary()
              location: class com.google.common.collect.Ordering
            

            I am in the process of resolving this issue

            Show
            karthik Karthik Raveendran added a comment - To identify the issues in opening the application GUI, I want to run the project in the debug mode in Intellij. Although all the IGB bundles is running through terminal for Java 11, when I try to run the project in Intellij debug mode to identify the problem a Felix SCR Processing error is thrown. After disabling the processing, a google guava issue persists, java: cannot find symbol symbol: method arbitrary() location: class com.google.common.collect.Ordering I am in the process of resolving this issue
            Hide
            karthik Karthik Raveendran added a comment -
            Show
            karthik Karthik Raveendran added a comment - I saw this stackoverflow post. Checking to see if it is valid: https://stackoverflow.com/questions/32111613/why-doesnt-an-osgi-bundle-start-even-when-all-the-dependencies-are-resolved
            Hide
            nfreese Nowlan Freese added a comment - - edited

            While attempting to modify the IGB gui using the Netbeans GUI builder, we ran into an error regarding the ColorComboBox. I have attached pictures of the error and exceptions. I tested this on Java 8 Oracle JDK (jdk1.8.0_191.jdk) and Zulu (zulu8.62.0.19-ca-fx-jdk8.0.332-macosx_x64/zulu-8.jdk) on Netbeans 8.2 and 11.3 on IGB branches release-9.1.0 and master (as of May 19, 2023). All variations produced the same error.

            The error appears to be due to the Jidesoft ColorComboBox not being visible to the Netbeans GUI builder. Attempting to add the ColorComboBox to the Netbeans Palette from the Jidesoft jar does not appear to work.

            Updating Jide-Ultimate to version 3.7.14 did not make a difference.

            Opening the Jide-Ultimate jar as a file in netbeans did not make a difference.

            Netbeans Swing GUI Builder not working with java-module project and Maven

            Show
            nfreese Nowlan Freese added a comment - - edited While attempting to modify the IGB gui using the Netbeans GUI builder, we ran into an error regarding the ColorComboBox. I have attached pictures of the error and exceptions. I tested this on Java 8 Oracle JDK (jdk1.8.0_191.jdk) and Zulu (zulu8.62.0.19-ca-fx-jdk8.0.332-macosx_x64/zulu-8.jdk) on Netbeans 8.2 and 11.3 on IGB branches release-9.1.0 and master (as of May 19, 2023). All variations produced the same error. The error appears to be due to the Jidesoft ColorComboBox not being visible to the Netbeans GUI builder. Attempting to add the ColorComboBox to the Netbeans Palette from the Jidesoft jar does not appear to work. Updating Jide-Ultimate to version 3.7.14 did not make a difference. Opening the Jide-Ultimate jar as a file in netbeans did not make a difference. Netbeans Swing GUI Builder not working with java-module project and Maven
            Hide
            karthik Karthik Raveendran added a comment -

            The errors above was also resolved by removing felix jetty artifacts from main/pom.xml and keeping the dependency in the project pom.xml. See commit

            Show
            karthik Karthik Raveendran added a comment - The errors above was also resolved by removing felix jetty artifacts from main/pom.xml and keeping the dependency in the project pom.xml. See commit
            Hide
            karthik Karthik Raveendran added a comment - - edited

            Majority of the errors was an osgi.wiring.package issue with com.sun.java.swin.plaf.windows which is available in java.desktop. By adding com.sun.java.swing.plaf.windows;resolution:=optional in import package tag in igb pom.xml. See commit

            Errors left are "two dependency chains" issue:

            Unable to resolve resource org.apache.felix.http.jetty [org.apache.felix.http.jetty [66](R 66.0)] because it is exposed to package 'javax.servlet' from resources org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] and org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] via two dependency chains.
            Unable to resolve resource org.apache.felix.http.jetty [org.apache.felix.http.jetty [66](R 66.0)] because it is exposed to package 'javax.servlet' from resources org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] and org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] via two dependency chains.
            Unable to resolve resource org.apache.felix.http.jetty [org.apache.felix.http.jetty [66](R 66.0)] because it is exposed to package 'javax.servlet' from resources org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] and org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] via two dependency chains.
            Unable to resolve resource org.apache.felix.http.jetty [org.apache.felix.http.jetty [66](R 66.0)] because it is exposed to package 'javax.servlet.descriptor' from resources org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] and org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] via two dependency chains.
            Unable to resolve resource org.apache.felix.webconsole [org.apache.felix.webconsole [69](R 69.0)] because it is exposed to package 'javax.servlet' from resources org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] and org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] via two dependency chains.
            
            Show
            karthik Karthik Raveendran added a comment - - edited Majority of the errors was an osgi.wiring.package issue with com.sun.java.swin.plaf.windows which is available in java.desktop. By adding com.sun.java.swing.plaf.windows;resolution:=optional in import package tag in igb pom.xml. See commit Errors left are "two dependency chains" issue: Unable to resolve resource org.apache.felix.http.jetty [org.apache.felix.http.jetty [66](R 66.0)] because it is exposed to package 'javax.servlet' from resources org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] and org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] via two dependency chains. Unable to resolve resource org.apache.felix.http.jetty [org.apache.felix.http.jetty [66](R 66.0)] because it is exposed to package 'javax.servlet' from resources org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] and org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] via two dependency chains. Unable to resolve resource org.apache.felix.http.jetty [org.apache.felix.http.jetty [66](R 66.0)] because it is exposed to package 'javax.servlet' from resources org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] and org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] via two dependency chains. Unable to resolve resource org.apache.felix.http.jetty [org.apache.felix.http.jetty [66](R 66.0)] because it is exposed to package 'javax.servlet.descriptor' from resources org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] and org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] via two dependency chains. Unable to resolve resource org.apache.felix.webconsole [org.apache.felix.webconsole [69](R 69.0)] because it is exposed to package 'javax.servlet' from resources org.apache.felix.http.servlet-api [org.apache.felix.http.servlet-api [67](R 67.0)] and org.apache.felix.http.bundle [org.apache.felix.http.bundle [65](R 65.0)] via two dependency chains.

              People

              • Assignee:
                karthik Karthik Raveendran
                Reporter:
                karthik Karthik Raveendran
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: