Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Sprint:Fall 2018 Sprint 3, Fall 2018 Sprint 4
Description
We are now using packages from htsjdk artifact in the IGB project. However, there is a problem. It is not an OSGi bundle. To handle this, we are now importing the htsjdk into the "shared-lib-wrapper" module of IGB project. The pom.xml file of this module uses the BND-tool maven plug-in to packages htsjdk along with many other completely unrelated artifacts into one large bundle, which then gets loaded into the OSGi run-time along with all the other bundles that make up the IGB application.
This is not ideal. Maintaining the "shared-lib-wrapper" module is made extra complicated by this approach. For example, if some of these libraries rely on different versions of the same artifact, the approach won't work.
To simplify our codebase, we should transform these 3rd-party jar artifacts into proper OSGi bundles.
To do this, let's "fork" the htsjdk library and modify/enhance their build process to create a proper OSGi bundle.
Following this, we should add it to our nexus maven repository (https://nexus.bioviz.org) so that the new htsjdk OSGi bundle is available to IGB developers.
Attachments
Issue Links
- relates to
-
IGBF-1457 Startup Error in Console (ERROR com.affymetrix.main.OSGiHandler)
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
IGBF-1417 Create new artifact with bigbed and bigwig parsing code from IGV codebase
-
- Closed
-
-
-
- Closed
-