Lucee 5 Extension creation

dev google-group-archive
1

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:

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

2

Thanks Jesse. However, I have tried that too. In that scenario, the files
are copied to:
C:\lucee-express-5.0.0.178-BETA\webapps\ROOT\WEB-INF\lucee\context\components\org.…

We need them in:
C:\lucee-express-5.0.0.178-BETA\webapps\ROOT\WEB-INF\lucee\components\org.…

I’ll keep trying different scenarios but it would be nice to have some sort
of guide for people who want to create extensions for Lucee.
AndrewOn Sunday, February 28, 2016 at 8:30:01 AM UTC-8, Jesse Shaffer wrote:

I believe those should go into context/components/org (for web extensions).

3

I believe those should go into context/components/org (for web extensions).

4

I wonder if the jars need to also be referenced in the MANIFEST.MF file. I noticed this in the MongoDB extension I’m working on. The MANIFEST.MF has the Require-Bundle property. Something to try maybe.

Manifest-Version: 1.0
Export-Package: org.lucee.mongodb
Bundle-ManifestVersion: 2
Require-Bundle: org.mongodb.mongo-java-driver;bundle-version=3.2.2> On Feb 27, 2016, at 8:51 PM, ADK <@ADK> wrote:

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:

Extensions in Lucee 5 :: Lucee Documentation

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

–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/c0e6266a-2039-4ae8-a54a-25ae2cf1660a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

5

Thank you both. I believe Jesse is correct on the jars directory. It is
mainly the “components” directory (with sub dir “org”, etc.) that I am
having an issue with. It would be nice if someone from LAS could weigh in
on the proper way to do this. Perhaps there isn’t one at the moment?

I will give Jesse’s suggestion a try, I am just a bit reluctant to spin my
wheels, hacking my way toward a workable solution if there’s a better
defined, best practice way of creating extensions.

Cheers for the help guys!On Monday, February 29, 2016 at 9:20:02 AM UTC-8, Jesse Shaffer wrote:

I wonder if the jars need to also be referenced in the MANIFEST.MF file. I

noticed this in the MongoDB extension I’m working on. The MANIFEST.MF has
the Require-Bundle property. Something to try maybe.

I don’t believe so… just put any needed jars in the “jars” sub
directory. If they are bundles they will be installed, if they are not
OSGi bundles, I don’t know if they are automatically converted to be
bundles or if they are just put in the lib directory. Micha would have to
answer that part.

One thing you might do is create a component mapping to a folder with your
org/whatever code (omit the components directory), then create a LAR from
that mapping. Then put that lar into the /archives subdirectory of the
extension, and it will automatically install.

As a side note, I’m working on a Maven plugin to build Lucee 5
archives/extensions. It is mostly working, still needs some improvement
and cleanup, and it’s not documented…yet (this is my first crack at
writing a maven plugin, so go easy on me if you see glaring problems).
GitHub - dajester2013/lucee-maven-plugin: A maven plugin to simplify Lucee project development. (switch to the
develop branch for the lucee extension portion).

6

Hi,

For my extensions, I am using ant build code created by Micha, which creates both the classic and modern extension.
Code can be found on Github: https://github.com/paulklinkenberg/lucee-loganalyzer-installer

The build-modern.xml file shows you the structure of the modern .lex extensions.

Kind regards,

Paul Klinkenberg------------

Op 2 mrt. 2016 om 01:45 heeft ADK <@ADK> het volgende geschreven:

Thank you both. I believe Jesse is correct on the jars directory. It is mainly the “components” directory (with sub dir “org”, etc.) that I am having an issue with. It would be nice if someone from LAS could weigh in on the proper way to do this. Perhaps there isn’t one at the moment?

I will give Jesse’s suggestion a try, I am just a bit reluctant to spin my wheels, hacking my way toward a workable solution if there’s a better defined, best practice way of creating extensions.

Cheers for the help guys!

On Monday, February 29, 2016 at 9:20:02 AM UTC-8, Jesse Shaffer wrote:

I wonder if the jars need to also be referenced in the MANIFEST.MF file. I noticed this in the MongoDB extension I’m working on. The MANIFEST.MF has the Require-Bundle property. Something to try maybe.

I don’t believe so… just put any needed jars in the “jars” sub directory. If they are bundles they will be installed, if they are not OSGi bundles, I don’t know if they are automatically converted to be bundles or if they are just put in the lib directory. Micha would have to answer that part.

One thing you might do is create a component mapping to a folder with your org/whatever code (omit the components directory), then create a LAR from that mapping. Then put that lar into the /archives subdirectory of the extension, and it will automatically install.

As a side note, I’m working on a Maven plugin to build Lucee 5 archives/extensions. It is mostly working, still needs some improvement and cleanup, and it’s not documented…yet (this is my first crack at writing a maven plugin, so go easy on me if you see glaring problems). GitHub - dajester2013/lucee-maven-plugin: A maven plugin to simplify Lucee project development. (switch to the develop branch for the lucee extension portion).

–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/1e42d60b-605a-4546-9eb2-7f1ae4dc4df2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

7

I fixed this bug now, again thanks for letting me know!
Bugfix + new release: the "modern type" extension did not contain the… · paulklinkenberg/lucee-loganalyzer@39c3aa8 · GitHub https://github.com/paulklinkenberg/lucee-loganalyzer/commit/39c3aa8fa4798d99b9e71ff14aa31956d7c377d0

Kind regards,

Paul KlinkenbergOp 2 mrt. 2016, om 16:55 heeft Paul Klinkenberg <@Paul_Klinkenberg> het volgende geschreven:

Well, now that sucks :-/ Thanks for the info, will check it.

Paul

Op 2 mrt. 2016, om 16:22 heeft Gert Franz <@Gert_Franz mailto:Gert_Franz> het volgende geschreven:

Just a FYI. Your modern extension is empty L when I build it with ant. It builds it but it only contains the manifest file and the logo…

Sincerely
Gert Franz
<image001.png>

RASIA GmbH
Spittelgasse 7
5103 Moeriken-Wildegg
Switzerland
Email: @Gert_Franz mailto:Gert_Franz
Skype: gert.franz
Phone Switzerland: +41 76 5680 231

Von: lucee@googlegroups.com mailto:lucee@googlegroups.com [mailto:lucee@googlegroups.com mailto:lucee@googlegroups.com] Im Auftrag von Paul Klinkenberg
Gesendet: Mittwoch, 2. März 2016 08:49
An: lucee@googlegroups.com mailto:lucee@googlegroups.com
Betreff: Re: [Lucee] Lucee 5 Extension creation

Hi,

For my extensions, I am using ant build code created by Micha, which creates both the classic and modern extension.
Code can be found on Github: GitHub - paulklinkenberg/lucee-loganalyzer-installer: A Lucee server extension to install the Log analyzer into all your web contexts https://github.com/paulklinkenberg/lucee-loganalyzer-installer

The build-modern.xml file shows you the structure of the modern .lex extensions.

Kind regards,

Paul Klinkenberg

Op 2 mrt. 2016 om 01:45 heeft ADK <@ADK mailto:ADK> het volgende geschreven:

Thank you both. I believe Jesse is correct on the jars directory. It is mainly the “components” directory (with sub dir “org”, etc.) that I am having an issue with. It would be nice if someone from LAS could weigh in on the proper way to do this. Perhaps there isn’t one at the moment?

I will give Jesse’s suggestion a try, I am just a bit reluctant to spin my wheels, hacking my way toward a workable solution if there’s a better defined, best practice way of creating extensions.

Cheers for the help guys!

On Monday, February 29, 2016 at 9:20:02 AM UTC-8, Jesse Shaffer wrote:

I wonder if the jars need to also be referenced in the MANIFEST.MF file. I noticed this in the MongoDB extension I’m working on. The MANIFEST.MF has the Require-Bundle property. Something to try maybe.

I don’t believe so… just put any needed jars in the “jars” sub directory. If they are bundles they will be installed, if they are not OSGi bundles, I don’t know if they are automatically converted to be bundles or if they are just put in the lib directory. Micha would have to answer that part.

One thing you might do is create a component mapping to a folder with your org/whatever code (omit the components directory), then create a LAR from that mapping. Then put that lar into the /archives subdirectory of the extension, and it will automatically install.

As a side note, I’m working on a Maven plugin to build Lucee 5 archives/extensions. It is mostly working, still needs some improvement and cleanup, and it’s not documented…yet (this is my first crack at writing a maven plugin, so go easy on me if you see glaring problems). GitHub - dajester2013/lucee-maven-plugin: A maven plugin to simplify Lucee project development. https://github.com/dajester2013/lucee-maven-plugin/ (switch to the develop branch for the lucee extension portion).

Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/1e42d60b-605a-4546-9eb2-7f1ae4dc4df2%40googlegroups.com https://groups.google.com/d/msgid/lucee/1e42d60b-605a-4546-9eb2-7f1ae4dc4df2%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.
–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/EA314C08-C569-438F-A714-9E69B135C7B3%40ongevraagdadvies.nl https://groups.google.com/d/msgid/lucee/EA314C08-C569-438F-A714-9E69B135C7B3%40ongevraagdadvies.nl?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/034501d17497%2451dc70a0%24f59551e0%24%40rasia.ch https://groups.google.com/d/msgid/lucee/034501d17497%2451dc70a0%24f59551e0%24%40rasia.ch?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/434B6496-9FCB-4867-9EA5-FBABCA0F7E4D%40ongevraagdadvies.nl https://groups.google.com/d/msgid/lucee/434B6496-9FCB-4867-9EA5-FBABCA0F7E4D%40ongevraagdadvies.nl?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

8

Well, now that sucks :-/ Thanks for the info, will check it.

PaulOp 2 mrt. 2016, om 16:22 heeft Gert Franz <@Gert_Franz> het volgende geschreven:

Just a FYI. Your modern extension is empty L when I build it with ant. It builds it but it only contains the manifest file and the logo…

Sincerely
Gert Franz
<image001.png>

RASIA GmbH
Spittelgasse 7
5103 Moeriken-Wildegg
Switzerland
Email: @Gert_Franz mailto:Gert_Franz
Skype: gert.franz
Phone Switzerland: +41 76 5680 231

Von: lucee@googlegroups.com [mailto:lucee@googlegroups.com] Im Auftrag von Paul Klinkenberg
Gesendet: Mittwoch, 2. März 2016 08:49
An: lucee@googlegroups.com
Betreff: Re: [Lucee] Lucee 5 Extension creation

Hi,

For my extensions, I am using ant build code created by Micha, which creates both the classic and modern extension.
Code can be found on Github: GitHub - paulklinkenberg/lucee-loganalyzer-installer: A Lucee server extension to install the Log analyzer into all your web contexts https://github.com/paulklinkenberg/lucee-loganalyzer-installer

The build-modern.xml file shows you the structure of the modern .lex extensions.

Kind regards,

Paul Klinkenberg

Op 2 mrt. 2016 om 01:45 heeft ADK <@ADK mailto:ADK> het volgende geschreven:

Thank you both. I believe Jesse is correct on the jars directory. It is mainly the “components” directory (with sub dir “org”, etc.) that I am having an issue with. It would be nice if someone from LAS could weigh in on the proper way to do this. Perhaps there isn’t one at the moment?

I will give Jesse’s suggestion a try, I am just a bit reluctant to spin my wheels, hacking my way toward a workable solution if there’s a better defined, best practice way of creating extensions.

Cheers for the help guys!

On Monday, February 29, 2016 at 9:20:02 AM UTC-8, Jesse Shaffer wrote:

I wonder if the jars need to also be referenced in the MANIFEST.MF file. I noticed this in the MongoDB extension I’m working on. The MANIFEST.MF has the Require-Bundle property. Something to try maybe.

I don’t believe so… just put any needed jars in the “jars” sub directory. If they are bundles they will be installed, if they are not OSGi bundles, I don’t know if they are automatically converted to be bundles or if they are just put in the lib directory. Micha would have to answer that part.

One thing you might do is create a component mapping to a folder with your org/whatever code (omit the components directory), then create a LAR from that mapping. Then put that lar into the /archives subdirectory of the extension, and it will automatically install.

As a side note, I’m working on a Maven plugin to build Lucee 5 archives/extensions. It is mostly working, still needs some improvement and cleanup, and it’s not documented…yet (this is my first crack at writing a maven plugin, so go easy on me if you see glaring problems). GitHub - dajester2013/lucee-maven-plugin: A maven plugin to simplify Lucee project development. https://github.com/dajester2013/lucee-maven-plugin/ (switch to the develop branch for the lucee extension portion).

Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/1e42d60b-605a-4546-9eb2-7f1ae4dc4df2%40googlegroups.com https://groups.google.com/d/msgid/lucee/1e42d60b-605a-4546-9eb2-7f1ae4dc4df2%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.
–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/EA314C08-C569-438F-A714-9E69B135C7B3%40ongevraagdadvies.nl https://groups.google.com/d/msgid/lucee/EA314C08-C569-438F-A714-9E69B135C7B3%40ongevraagdadvies.nl?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com mailto:lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/034501d17497%2451dc70a0%24f59551e0%24%40rasia.ch https://groups.google.com/d/msgid/lucee/034501d17497%2451dc70a0%24f59551e0%24%40rasia.ch?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

9

I think back porting the ant script into documentation might help.

Mark Drew

  • Sent by typing with my thumbs.> On 2 Mar 2016, at 07:48, Paul Klinkenberg <@Paul_Klinkenberg> wrote:

Hi,

For my extensions, I am using ant build code created by Micha, which creates both the classic and modern extension.
Code can be found on Github: GitHub - paulklinkenberg/lucee-loganalyzer-installer: A Lucee server extension to install the Log analyzer into all your web contexts

The build-modern.xml file shows you the structure of the modern .lex extensions.

Kind regards,

Paul Klinkenberg

Op 2 mrt. 2016 om 01:45 heeft ADK <@ADK> het volgende geschreven:

Thank you both. I believe Jesse is correct on the jars directory. It is mainly the “components” directory (with sub dir “org”, etc.) that I am having an issue with. It would be nice if someone from LAS could weigh in on the proper way to do this. Perhaps there isn’t one at the moment?

I will give Jesse’s suggestion a try, I am just a bit reluctant to spin my wheels, hacking my way toward a workable solution if there’s a better defined, best practice way of creating extensions.

Cheers for the help guys!

On Monday, February 29, 2016 at 9:20:02 AM UTC-8, Jesse Shaffer wrote:

I wonder if the jars need to also be referenced in the MANIFEST.MF file. I noticed this in the MongoDB extension I’m working on. The MANIFEST.MF has the Require-Bundle property. Something to try maybe.

I don’t believe so… just put any needed jars in the “jars” sub directory. If they are bundles they will be installed, if they are not OSGi bundles, I don’t know if they are automatically converted to be bundles or if they are just put in the lib directory. Micha would have to answer that part.

One thing you might do is create a component mapping to a folder with your org/whatever code (omit the components directory), then create a LAR from that mapping. Then put that lar into the /archives subdirectory of the extension, and it will automatically install.

As a side note, I’m working on a Maven plugin to build Lucee 5 archives/extensions. It is mostly working, still needs some improvement and cleanup, and it’s not documented…yet (this is my first crack at writing a maven plugin, so go easy on me if you see glaring problems). GitHub - dajester2013/lucee-maven-plugin: A maven plugin to simplify Lucee project development. (switch to the develop branch for the lucee extension portion).

–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/1e42d60b-605a-4546-9eb2-7f1ae4dc4df2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/EA314C08-C569-438F-A714-9E69B135C7B3%40ongevraagdadvies.nl.
For more options, visit https://groups.google.com/d/optout.

10

Just a FYI. Your modern extension is empty L when I build it with ant. It builds it but it only contains the manifest file and the logo…

Sincerely
Gert Franz

RASIA GmbH

Spittelgasse 7

5103 Moeriken-Wildegg

Switzerland

Email: mailto:Gert_Franz @Gert_Franz
Skype: gert.franz

Phone Switzerland: +41 76 5680 231Von: lucee@googlegroups.com [mailto:lucee@googlegroups.com] Im Auftrag von Paul Klinkenberg
Gesendet: Mittwoch, 2. März 2016 08:49
An: lucee@googlegroups.com
Betreff: Re: [Lucee] Lucee 5 Extension creation

Hi,

For my extensions, I am using ant build code created by Micha, which creates both the classic and modern extension.

Code can be found on Github: https://github.com/paulklinkenberg/lucee-loganalyzer-installer

The build-modern.xml file shows you the structure of the modern .lex extensions.

Kind regards,

Paul Klinkenberg

Op 2 mrt. 2016 om 01:45 heeft ADK <@ADK> het volgende geschreven:

Thank you both. I believe Jesse is correct on the jars directory. It is mainly the “components” directory (with sub dir “org”, etc.) that I am having an issue with. It would be nice if someone from LAS could weigh in on the proper way to do this. Perhaps there isn’t one at the moment?

I will give Jesse’s suggestion a try, I am just a bit reluctant to spin my wheels, hacking my way toward a workable solution if there’s a better defined, best practice way of creating extensions.

Cheers for the help guys!

On Monday, February 29, 2016 at 9:20:02 AM UTC-8, Jesse Shaffer wrote:

I wonder if the jars need to also be referenced in the MANIFEST.MF file. I noticed this in the MongoDB extension I’m working on. The MANIFEST.MF has the Require-Bundle property. Something to try maybe.

I don’t believe so… just put any needed jars in the “jars” sub directory. If they are bundles they will be installed, if they are not OSGi bundles, I don’t know if they are automatically converted to be bundles or if they are just put in the lib directory. Micha would have to answer that part.

One thing you might do is create a component mapping to a folder with your org/whatever code (omit the components directory), then create a LAR from that mapping. Then put that lar into the /archives subdirectory of the extension, and it will automatically install.

As a side note, I’m working on a Maven plugin to build Lucee 5 archives/extensions. It is mostly working, still needs some improvement and cleanup, and it’s not documented…yet (this is my first crack at writing a maven plugin, so go easy on me if you see glaring problems). GitHub - dajester2013/lucee-maven-plugin: A maven plugin to simplify Lucee project development. (switch to the develop branch for the lucee extension portion).

–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/1e42d60b-605a-4546-9eb2-7f1ae4dc4df2%40googlegroups.com https://groups.google.com/d/msgid/lucee/1e42d60b-605a-4546-9eb2-7f1ae4dc4df2%40googlegroups.com?utm_medium=email&utm_source=footer .
For more options, visit https://groups.google.com/d/optout.

–
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/EA314C08-C569-438F-A714-9E69B135C7B3%40ongevraagdadvies.nl https://groups.google.com/d/msgid/lucee/EA314C08-C569-438F-A714-9E69B135C7B3%40ongevraagdadvies.nl?utm_medium=email&utm_source=footer .
For more options, visit https://groups.google.com/d/optout.