Problems with maven dependencies in .CFConfig.json

dev support
1

I’m having problems adding maven dependencies to .CFConfig.json. Here’s what I was trying to add:

  "javasettings": {
    "maven": [
      "com.rabbitmq:amqp-client:5.25.0",
      "software.amazon.awssdk:cloudfront:2.20.0",
      "software.amazon.awssdk:secretsmanager:2.20.0",
      "software.amazon.awssdk:url-connection-client:2.20.0"
    ]
  }

I looked in the deploy.log file and didn’t see any issues. The only way I was able to find the issue was by slowly removing parts of my .CFConfig.json file and then trying to load the Lucee Administrator, which would not open when these dependencies were present.

What’s the best practice for adding these dependencies? Are there problems or limitations with this methodology that I should be aware of? How can I make this work, or am I forced to build fat jars that include the entire dependency graph for each one?

2

I ended up writing my own java bundle builder that pulls the entire dependency tree for a dependency and builds a shaded bundle jar for it. Not sure if this is the best way to go, but it seems to have solved my problem for the time being.