IGB uses GUI components from Jidesoft.

For many years, the IGB project has imported these components by including the following configuration in the parent POM:

    <properties>
...
       <jide.version>3.5.15</jide.version>
...
    </properties>
...
    <dependencyManagement>
...
            <dependency>
                <groupId>com.jidesoft</groupId>
                <artifactId>jide-ultimate</artifactId>
                <version>${jide.version}</version>
            </dependency>
...
    </dependencyManagement>

The jide-ultimate artifact is available from legacy maven repository 2, specified in the parent POM with:

    <repositories>
...
        <repository>
            <id>repo2</id>
            <url>https://maven.bioviz.org/repo2</url>
        </repository>
...
    </repositories>

Sai Supreeth Segu investigated obtaining jide-ultimate artifact from maven central. He could not find it there, but he did find some other artifacts that appear to contain packages from jide-ultimate.

For this task, review the packages he found. Compare them jide-ultimate. Answer the question:

• Which combination of packages contain all the packages used by jide-ultimate?

Next, use the IGB Docker image to test building IGB, or use your local environment after removing all artifacts from your local .m2 repository to avoid getting confused by local caching.
Recommended steps:

• Make a branch on your IGB fork
• Replace jide-ultimate artifact in the top level POM with the other artifacts.
• Modify shared-lib-wrapper code to import the packages from the other artifacts into our large OSGi bundle, as is currently being done with jide-ultimate
• Remove jide-ultimate artifact from the project
• Test the build on a totally clean environment, e.g., no jidesoft artifacts in the repository local to the build process; ensure it can built on bitbucket using bitbucket pipelines as usual
• Run the built application; check the log for OSGi-related errors, e.g., can't find a package

Tip: IGB contains a Felix Web Console you can use to check whether or not a bundle has been loaded and resolve properly. Errors occur when a bundles dependencies can't be resolved due the framework not being able to locate them. See IGB repository top-level README for how to access and use the Felix Web console.

Also, read: https://www.jidesoft.com/products/. Note that this documentation says that the first 14 artifacts are packaged with JIDE Ultimate Suite, which is probably the human-friendly name for the jide-ultimate.jar artifact. Do a global search of the IGB code base for all jidesoft imports and determine: Which classes and packages are being used? Use this information to identify the subset of artifacts we need for the IGB project.

JIDE Software products are focused on feature-rich Swing components to simplify the development of rich-client applications. We currently offer 15 component products - the JIDE Docking Framework, JIDE Action Framework, JIDE Components, JIDE Grids, JIDE Dialogs, JIDE Shortcut Editor, JIDE Pivot Grid, JIDE Data Grids, JIDE Code Editor, JIDE Feed Reader, JIDE Dashboard, JIDE Charts, JIDE Gantt Chart, and JIDE Diff - which cover almost every aspect of Swing development. All those products above are bundled into JIDE Ultimate Suite. We also have JIDE Professional Suite and JIDE Enterprise Suite which bundle the first two and the first five products respectively.

Also, note this message from Jidesoft:

As of April 2007, we decided to open source the JIDE Common Layer - the foundation of all JIDE other products. You can get the JIDE Common Layer release or access the github repository from github (it was formally hosted on java.net which is now discontinued). If you use maven for your project, all released versions of JIDE Common Layer are also available on the centeral maven repository through sonatype. If you are paid JIDE customers, the source code for JIDE Common Layer is always included in the release under src subfolder.

The above quote is from: https://www.jidesoft.com/products/oss.htm