Maven and Google Client API Services

dev
1

Lucee 7.0.2.106
Apache Tomcat/11.0.18
21.0.10 (Eclipse Adoptium) 64bit
Windows 11 (10.0) 64bit
IIS 10

I’m trying to access Google’s java API through Lucee. In the past I’ve done this by figuring out all the dependencies and then dumping the necessary files in the [lucee]\lib folder. I recently ran across Lucee’s ability to pull in java files via Maven, and decided to try that. For some reason, while I can get it to work for the client API, itself–pulling down and accessing all the necessary libraries, I can’t seem to get it to work for the services based on the API. Does anyone know why this works fine:

<cfcomponent … javaSettings=‘{“maven”:[“com.google.api-client:google-api-client:2.0.0”]}’

(Maven Central: com.google.api-client:google-api-client:2.0.0)

But this does not (i.e. doesn’t pull down any libraries, at all):

<cfcomponent … javaSettings=‘{“maven”:[“com.google.apis:google-api-services-sheets:v4-rev20260213-2.0.0”]}’>

( Maven Central: com.google.apis:google-api-services-sheets )

I’m not all that familiar with Maven, so, hopefully, I’m just missing something obvious. :crossed_fingers:t2:

Thanks!

1 Like
2

yup, it’s a bug, version parsing is to strict and also fails / skip silently

good report, thanks

https://luceeserver.atlassian.net/browse/LDEV-6250

2 Likes
3

fixed in the latest 6.2 and 7.0 snapshots

filed a follow up ticket to make the DX with invalid maven co-oridinates throw a better error message rather than just ending up null and throwing a slightly confusing component / class / variable not found. they are lazy evaluated on use, so it’s a bit more complicated to solve

https://luceeserver.atlassian.net/browse/LDEV-6251

1 Like