Error in building with 3rd party standalone jar files | Unable to get bundle symbolic name from artifact

[digarg]

 

 Getting issue 

[ERROR] Failed to execute goal com.adobe.aem:aemanalyser-maven-plugin:1.5.8:project-analyse (aem-analyser) on project nxxxx

.all: A fatal error occurred while analysing the features, see error cause:: Unable to get bundle symbolic name from artifact com.captcha:botdetect-servlet:4.0.beta3.7 -> [Help 1]

Works fine for datalayer dependency. but failing for com.captcha jars with above issue. Followed below article .Please advise

https://techrevel.blog/2023/09/27/managing-third-party-dependencies-in-aem/comment-page-1/#respond

[Mahedi_Sabuj]

From Abode Documentation

---

It is assumed the 3rd party jar is an OSGi bundle

---

It seems the Jar is not OSGI compatible. You can try this approach using bnd-maven-plugin

https://myaemlearnings.blogspot.com/2021/12/embed-third-party-dependency-using-bnd.html

[arunpatidar]

Hi,
Please check the logs ?

If this is related to already working 3rd party jars then please check below:

we had the same kind of issue, where extraction of jar is failed due to java update, which failed due to extra data field check.

https://bell-sw.com/blog/invalid-cen-header-fixed-in-the-latest-jdk-11-and-17-updates/ 

[EstebanBustamante]

@digarg Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community