I am trying to update a 4.x extension to work in Lucee 5. The good news is
that if I manually move the requisite files into the correct folders,
everything works as it’s supposed to in Lucee 5.x… well, so far anyways.
I am having trouble getting the auto-deploy, convention-based method to
work. The documentation is virtually non-existent other than a blurb Micha
wrote here:
http://docs.lucee.org/guides/lucee-5/extensions.html
this snippet is about the only clue as to what to do:
“/applications - for cfm & cfc files that need to be installed in the
webroot /functions - for build-in functions to install /jars - for
libraries used by your extension”
So from here I gather that a “functions” (plural) folder in a .lex will map
to the “function” (singular) folder in the web context. Likewise for tags
to the tags folder. And indeed that does seem to work. However the rest is
a mystery.
I gather from the snippet above - and from the samples Micha has done
himself (e.g. MySQL, PDF, etc.) that any jars that I want to include go
into a “jars” folder. In 4.x these jars would get moved into the “lib”
folder in the web context… I don’t “see” that happening in 5.x but
perhaps they are being loaded nonetheless? I’ll need to check that…
The ones I am having trouble with are the files that need to go into
folders pther than function or tag, the components.org folder (I am dealing
with a web context, not the server context here, by the way). What is the
convention in the .lex file for that? I’ve trial and errored (with emphasis
on the “error” part!) several things but cannot seem to get it to work?
Anyways, would love to get this to work automatically so I could move the
cfspreadsheet extension that I mover from Railo to Lucee 4 to now go from
4.x to 5.x - as I said, the good news is that it does seem to work in 5.x
when manually copied over, just can’t get the new “easier and simplified”
install process to work.
Cheers,
Andrew
