To have offline working, we have to re-use internal web-inf/lib jars, however about 70 .jar's aren't mavenized, so we don't have metadata of those.
Not only metadata, but also the .pom file, without the original .pom file, it'll certainly won't match with maven central (ie. missing dependencies section).

So in the end the installed .jar will be narrowed to BC offline needs, and it might create incompatibilities if used differently. As .md5 and .sh1 files won't match, but also the functional aspect like third-party dependencies.

The potential proposed solution is to use the maven build (using an existing plugin or build a new plugin for this use case) that during the build of business central would collect not only the .jar's, but also the metadata content, and make it available somewhere to be re-used during runtime for the offline setup.

Here's the list of current dependencies that aren't exactly mavenized:
https://github.com/kiegroup/kie-wb-distributions/blob/master/kie-wb-webapp-common/src/main/resources/not-mavenized-artifacts.properties

Here's how we extract the .jars from web-inf:
https://github.com/kiegroup/appformer/blob/master/uberfire-m2repo-editor/uberfire-m2repo-editor-backend/src/main/java/org/guvnor/m2repo/backend/server/M2ServletContextListener.java

Here's how we fix not mavenized .jars:
https://github.com/kiegroup/appformer/blob/master/uberfire-m2repo-editor/uberfire-m2repo-editor-backend/src/main/java/org/guvnor/m2repo/backend/server/FixNotMavenizedArtifactInfo.java