This bug has been created mainly for tracking purposes of a problem our users might hit with org.kie:openshift-kie-springboot:7.33.0.Final-redhat-00002:jar artifact produced by SpringBoot: Nexus fails to deliver the file because it does not consider it to be a java-archive. A repackaged SpringBoot file is both application/java-archive and a application/x-sh. You can run it with java -jar artifact.jar and it is also possible to run it as a Linux service. 
The problem can be detected by observing the following message in Nexus log:
2020-03-09 19:19:02,234+0000 INFO [qtp572548223-344086] anonymous org.sonatype.nexus.proxy.maven.MavenFileTypeValidator - StorageFileItem pnc-indy-static:/org/kie/openshift-kie-springboot/7.33.0.Final-redhat-00002/openshift-kie-springboot-7.33.0.Final-redhat-00002.jar MIME-magic validation failed: expected MIME types: [application/java-archive], detected MIME types: [application/x-sh, text/plain, application/octet-stream]
2020-03-09 19:19:02,234+0000 INFO [qtp572548223-344086] anonymous org.sonatype.nexus.proxy.repository.validator.DefaultFileTypeValidatorHub - File item pnc-indy-static:/org/kie/openshift-kie-springboot/7.33.0.Final-redhat-00002/openshift-kie-springboot-7.33.0.Final-redhat-00002.jar evaluated as INVALID during file type validation (validator=maven)
2020-03-09 19:19:02,234+0000 INFO [qtp572548223-344086] anonymous org.sonatype.nexus.proxy.maven.maven2.M2Repository - Proxied item pnc-indy-static:/org/kie/openshift-kie-springboot/7.33.0.Final-redhat-00002/openshift-kie-springboot-7.33.0.Final-redhat-00002.jar evaluated as INVALID during content validation (validator=filetypevalidator, sourceUrl=<OMITTED>/org/kie/openshift-kie-springboot/7.33.0.Final-redhat-00002/openshift-kie-springboot-7.33.0.Final-redhat-00002.jar)
The above behaviour is expected and a possible workaround is to disable Nexus proxy content validation as mentioned in .
I do not see a way how to improve this situation in out product (provided we want to keep the current SpringBoot packaging), I suggest to close this issue as won't fix (unless any SpringBoot expert suggests otherwise) and keep it for documentation purposes.