Good stuff Zac/Micha! Just tried it out with a simple library hosted on Maven and it worked perfectly.
But I can’t see where the jar has been downloaded to. The /mvn/
directory you mention doesn’t exist in my case. Nothing in the deploy log either, or in the Bundles list in the admin UI.
Where can I find it? (This is a standard 6.2.1.122 Tomcat install on Windows).
1 Like
Ummm, in single mode?
Try this maybe? Make a typo in the maven artifact
Yes, single mode.
Can’t see anything in the catalina log about Maven, even if I run from the command line.
I’ve searched the lucee install folder for the name of the jar but found nothing.
Wait, do you have a .m2 cache?
With those logs settings, look in application.log?
One it’s installed it might no longer log as it’s simply found and used
Catalina.log is only for servlet related stuff
My bad the path was wrong, it’s just lucee-server\mvn\
not under the context
Actually I wasn’t seeing that directory either, but I think I’ve worked out why.
I already had an older version of the jar in my Lucee Admin > Bundles list (installed using osgiLoader).
When I uninstalled the existing jar and then ran my code, the specified jar was indeed downloaded to lucee-server\mvn\
.
I think this might be a bug because, while I would expect Lucee not to download the jar from MVN if it finds a copy already installed locally, that should only be the case if the local version is the same.
I had specified a newer version so Lucee should have downloaded it.