Highlighted

maven-bundle-plugin not working as expected in AEM 6.5

nikunjj81682294

14-08-2019

<plugin>
      <groupId>org.apache.felix</groupId>
      <artifactId>maven-bundle-plugin</artifactId>
      <version></version>
      <extensions>true</extensions>
      <configuration>
        <instructions>
          <Bundle-SymbolicName>${bundle.symbolicName}</Bundle-SymbolicName>
          <Bundle-Version>${project.version}</Bundle-Version>
          <Bundle-Name>${bundle.name}</Bundle-Name>
          <Export-Package>${bundle.namespace}</Export-Package>
          <Bundle-Activator>Activator.class</Bundle-Activator>

         <Embed-Dependency>*;scope=!provided|test;groupId=!org.mybundle.test</Embed-Dependency>

          <Embed-Transitive>true</Embed-Transitive>
          <Import-Package>*;resolution:=optional</Import-Package>
        </instructions>
      </configuration>
    </plugin>

The above code works fine in AEM 6.2 when I try to embed an external jar file. It looks like the above plugin is not working as expected in AEM 6.5.

Can someone provide an answer on what needs to be done to embed an external jar file in AEM 6.5?

Thanks,

Nikunj Jariwala

Replies

Highlighted

nikunjj81682294

15-08-2019

JaideepBrar​, Thanks for responding.

The referenced links describe how to convert a regular jar into an OSGi jar. Although this option works it involves doing things manually as opposed to relying on maven to do the conversion.

The maven-bundle-plugin does the conversion for you. It looks like it has been replaced by bnd-maven-plugin.

Do u know if bnd-maven-plugin is capable of doing the conversion from regular jar to OSGI? or Are we going back to doing things manually where you have to convert the jar to OSGI jar instead of relying on Maven to do it for you?

Thanks,

Nikunj Jariwala