Hi While dealing with upgrading graphql-java I encountered a rather bizarre issue with bundles. The class ‘AbstractBundleRequestMojo` has a check on line 159 where it uses a JarFile.getManifest() but that only returns the MANIFEST.MF when it is the first entry in the JAR file.
That eventually loads to a problem that graphql-java is not installed during the deployment inside a Feature Model. That said when AEM is started and I have all these unresolved issues regarding graphql-java and installation of graphql-java through the OSGi Console does indeed install it. If Felix allows an OSGi bundle to be install with a MANIFEST.MF entry not being the first entry why is Sling then requiring it? Cheers - Andy
