Embed Third party dependency using bnd-maven-plugin

This post explains the use of bnd-maven-plugin to embed third party dependency 

bnd-maven-plugin

Two main instructions of bnd-maven-plugin that serves the purpose are detailed below. 

  • -conditionalpackage 
    • pick packages from respective library and copy them in the bundle. Any dependencies of those copied packages will also be copied if they match the selectors.
    • This means we need to explicitly list all the Java package names of desired dependency as part of this instruction (including its transitive dependencies)
    • More about conditionalpackage instruction from official docs - https://bnd.bndtools.org/instructions/conditionalpackage.html
  • -includeresource 
    • For including resource inline
      • -includeresource: @artifactId-version.jar!/*
    • For embedding as a jar with an entry in bundle class path
      • -includeresource: artifactId-version.jar;lib:=true
    • For several other possible combinations for including the resource, please check - https://bnd.bndtools.org/instructions/includeresource.html
With complete understanding on these two instructions from official docs + based on how we would like the dependency to be included, we can use any one of the instruction with its respective options accordingly. 

Sample plugin entry for the dependency jackson-dataformat-csv (Supports reading and writing CSV)
where ${jackson-dataformat-csv.version} in the instruction resolves to a maven property holding the artifact version (2.9.5) as defined in parent pom.xml.
  • conditionalpackage
  • includeresource inline
  • includeresource embed (as a jar with class path entry)

Other blog posts for embedding third party dependency using maven-bundle-plugin, 

Comments

  1. SamanalystFebruary 22, 2024 at 3:03 AM

    Description: Experience a realm of unmatched comfort and luxury with the best rooms in Nagercoil  at Hotel Vijayetha. Immerse yourself in a world where modern elegance meets warm hospitality, creating a haven for discerning travelers seeking the epitome of accommodation.

    Our best rooms are thoughtfully designed to provide a tranquil retreat for both business and leisure guests. From intimate singles to spacious suites, each room is adorned with tasteful decor, contemporary furnishings, and premium amenities to ensure a restful sanctuary.

    Indulge in a culinary journey at our on-site restaurant, offering exquisite flavors and culinary delights. The central location of Hotel Vijayetha provides easy access to local attractions, business centers, and transportation hubs, making it the ideal choice for those seeking convenience and style.

    Unwind in the plush surroundings, relish the warmth of attentive staff, and enjoy the convenience of modern amenities such as high-speed Wi-Fi and well-appointed bathrooms. Hotel Vijayetha's commitment to excellence guarantees that your stay in Nagercoil is marked by comfort, style, and an unparalleled level of service.

    Book the best rooms in Nagercoil at Hotel Vijayetha and elevate your travel experience to new heights. Whether you're on a business trip or exploring the city's cultural gems, our best rooms redefine the meaning of luxury and ensure a memorable stay..visit us on https://www.hotelvijayetha.com/our-rooms/.!!!

    ReplyDelete

Post a Comment

Popular posts from this blog

Embedding Third party dependency/OSGi bundle in AEM application hosted in AEMasCS

Image
This post illustrate the ways of embedding third party dependency in AEM maven project. Steps are mentioned considering the project structure to be followed for AEMasCS while the same can be followed for classic versions too.  Before we begin, I would like to explain the scenario of including a dependency in our AEM maven project.  When we would like to make use of an API that is not already available in our project, we look for that in maven-central repository and specify the dependency in main pom.xml and desired module's pom.xml file. (Lets say, AWS S3 Java SDK V2 dependency) Upon updating the project in the IDE, we would see our class files (making use of those APIs) are compiled/build successfully without any errors.  Now, in the context of AEM/OSGi environment, when the same package and hence the bundle is deployed to AEM instance, dependencies that we added new might not be resolved/available in the OSGi as a bundle. Something like the below This indicates that the added dep
Read more

OSGI Factory Configuration implementation

OSGI Factory configuration is used to have many instances of an OSGI config (represented/identified via an identifier) for the single OSGI service/PID. Most often used OOB Factory configurations for example: Logger Factory/writer configuration (for log statements) Service user Mapper service Amendment (for using service resource resolver in projects) Few sample real time use case for the need of OSGI factory config: For multi tenant projects, if we have generic service used across tenants with properties/attributes specific to tenant. For single tenant, generic service targeting all locales with properties/attributes specific to locale. (where generic service -> holds logic in the lines of calling third party service for retrieving/updating information.) Implementation: ( In terms of OSGI R6 annotations ): Create Object Class Definition(OCD) defining desired properties for the OSGI service. - OSGIFactoryConfigOCD.java OSGI Service/Factory service to retrieve
Read more

Creation of Template Types for Editable templates

Image
In this post, we will create templates types which is the base for creating editable templates. Before getting to the subject directly, have added an introduction about templates in general. Template is the base for creating pages. Starting AEM 6.2, we have categorisation for templates - Static and Editable templates. Static templates :  This has been available for several versions of AEM/CQ Created using "Create Template" option with base page component as resourceType (which is responsible for rendering the page structure).  Template ( base page component as resourceType ) -> Page This cannot be edited as such. Since it just holds a reference to base page component, any changes to the page (other than authorable components), would need a change in base page component which is ultimately a work of developer. (calls for a code change) Allowed components are configured using Design mode (list being saved to etc/designs/projectfolder/templatename/jcr:content)
Read more