Lucee 5 - Extension via Maven (or similar)

If functionality like ORM is to be moved from the core to extensions then
there needs to be a way to declaratively build a Lucee app, as a WAR for
example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a maven
repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?

If functionality like ORM is to be moved from the core to extensions
then there needs to be a way to declaratively build a Lucee app, as a
WAR for example, and include the extensions that you’re cfml code is
going to require.

Agreed!

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

It’s ideal for me too-- I loves my dependencies. =)

Are there any plans to do something like this?

I’m happy to say that there are more than just plans. Micha is building
some stuff in, I’m building some stuff out (maven, and a few other repo
formats), and Ortus is working on ForgeBox, which is kind of an NPMish
deal. Color me stoked, and CFML being so hip it will have trouble
seeing over its pelvis.

-DenOn 4/20/15 2:48 AM, Chris Blackwell wrote:

Lucee extension are not compatible with war files, this is also something
completely different.
maybe an ear file would be more what you are looking for.
Anyway, that is what we support for Lucee 5, of course we are open to
discuss other possibilities for the future.

MichaOn Mon, Apr 20, 2015 at 1:38 PM, Chris Blackwell <@Chris_Blackwell> wrote:

Well not quite.
https://bitbucket.org/lucee/lucee/wiki/Lucee5_Extensions lists three
options for extension installation; Admin & Deploy Folder which require
post-startup actions, and a JVM Argument option, which i’m assuming prompts
lucee to go to the extension provider and download the required extension,
which doesn’t work if your lucee server is firewalled.

None of those options allow me to create a war that bundles the extension
without including the extension statically in WEB-INF/lucee/deploy

On Mon, 20 Apr 2015 at 12:22 Michael Offner <@Michael_Offner> wrote:

that is what is possible
https://bitbucket.org/lucee/lucee/wiki/Lucee5_Extensions

Micha

On Mon, Apr 20, 2015 at 12:57 PM, Chris Blackwell <@Chris_Blackwell> wrote:

And i’m not sure how that helps me once i have built the extension. I
don’t want to copy it to a location in my source code, or have to deploy it
seperately

i just want it as a dependency.
something like

<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>lucee-core</artifactId>
  <version>4.5.1.008</version>
<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>hibernate-orm</artifactId>
  <version>1.0.0</version>

Can that be done ?

On Mon, 20 Apr 2015 at 11:50 Chris Blackwell <@Chris_Blackwell> wrote:

unfortunately the build for the hibernate extension isn’t portable, as
it has dependencies on other code you have locally.

BUILD FAILED
/Users/chris/repos/lucee-hibernate-extension/build.xml:78:
/Users/mic/Projects/Railo/Source2/railo/railo-java/libs does not exist.

Isn’t this what maven solves… ?

On Mon, 20 Apr 2015 at 10:45 Michael Offner <@Michael_Offner> wrote:

No there are no plans to do this, because this is how it already works
:wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make "git clone https://bitbucket.org/lucee/hibernate-extension.git
    "
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be
copied to the extension provider or simply copied to
/deploy and Lucee then installs automatically.

All extension we do have a ant build script that allows to build them
without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the
modern (for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension
and you call for example “ant classic” to only get a old one.

Micha

On Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell> wrote:

If functionality like ORM is to be moved from the core to extensions
then there needs to be a way to declaratively build a Lucee app, as a WAR
for example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEBzYxXO2cjUM%2B4-e_4kCZ7VeOrD1mwejq7UYagF3L3bSAA%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEBzYxXO2cjUM%2B4-e_4kCZ7VeOrD1mwejq7UYagF3L3bSAA%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfTroJMt%3Db8bG8Nk1waDdXNpZnwckf87yJUUT-JaY%2BsUSZQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfTroJMt%3Db8bG8Nk1waDdXNpZnwckf87yJUUT-JaY%2BsUSZQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

And i’m not sure how that helps me once i have built the extension. I
don’t want to copy it to a location in my source code, or have to deploy it
seperately

i just want it as a dependency.
something like

<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>lucee-core</artifactId>
  <version>4.5.1.008</version>
<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>hibernate-orm</artifactId>
  <version>1.0.0</version>

Can that be done ?On Mon, 20 Apr 2015 at 11:50 Chris Blackwell <@Chris_Blackwell> wrote:

unfortunately the build for the hibernate extension isn’t portable, as it
has dependencies on other code you have locally.

BUILD FAILED
/Users/chris/repos/lucee-hibernate-extension/build.xml:78:
/Users/mic/Projects/Railo/Source2/railo/railo-java/libs does not exist.

Isn’t this what maven solves… ?

On Mon, 20 Apr 2015 at 10:45 Michael Offner <@Michael_Offner> wrote:

No there are no plans to do this, because this is how it already works :wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make “git clone https://bitbucket.org/lucee/hibernate-extension.git
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be
copied to the extension provider or simply copied to
/deploy and Lucee then installs automatically.

All extension we do have a ant build script that allows to build them
without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the modern
(for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension and
you call for example “ant classic” to only get a old one.

Micha

On Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell> wrote:

If functionality like ORM is to be moved from the core to extensions
then there needs to be a way to declaratively build a Lucee app, as a WAR
for example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

i will check …On Mon, Apr 20, 2015 at 12:50 PM, Chris Blackwell <@Chris_Blackwell> wrote:

unfortunately the build for the hibernate extension isn’t portable, as it
has dependencies on other code you have locally.

BUILD FAILED
/Users/chris/repos/lucee-hibernate-extension/build.xml:78:
/Users/mic/Projects/Railo/Source2/railo/railo-java/libs does not exist.

Isn’t this what maven solves… ?

On Mon, 20 Apr 2015 at 10:45 Michael Offner <@Michael_Offner> wrote:

No there are no plans to do this, because this is how it already works :wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make “git clone https://bitbucket.org/lucee/hibernate-extension.git
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be
copied to the extension provider or simply copied to
/deploy and Lucee then installs automatically.

All extension we do have a ant build script that allows to build them
without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the modern
(for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension and
you call for example “ant classic” to only get a old one.

Micha

On Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell> wrote:

If functionality like ORM is to be moved from the core to extensions
then there needs to be a way to declaratively build a Lucee app, as a WAR
for example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfToQ7ESS9SaN4DCko9U1Ef5yiWLW68h6A2VdYOv%3D8C3Ung%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfToQ7ESS9SaN4DCko9U1Ef5yiWLW68h6A2VdYOv%3D8C3Ung%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

so by moving features out of the core into extensions, WAR packaging
essentially gets broken? I’m sure this wasn’t your intention.

I don’t think an EAR file helps matters, Lucee should package perfectly
well as a WAR, and extensions should be able to be included in that war for
automatic deployment.

If .lex files in WEB-INF/lucee/deploy get automatically deployed when the
lucee starts, that’s half the battle right there. What about extending
that to find any .lex files on the classpath. That way they could just be
dropped in WEB-INF/lib by maven and they’ll get found.

The alternative is to use maven-dependency-plugin to copy the .lex files to
/WEB-INF/lucee/deploy in the package phase, but that requires a lot more
configuration than just declaring the dependencyOn Mon, 20 Apr 2015 13:07 Michael Offner <@Michael_Offner> wrote:

Lucee extension are not compatible with war files, this is also something
completely different.
maybe an ear file would be more what you are looking for.
Anyway, that is what we support for Lucee 5, of course we are open to
discuss other possibilities for the future.

Micha

On Mon, Apr 20, 2015 at 1:38 PM, Chris Blackwell <@Chris_Blackwell> wrote:

Well not quite.
https://bitbucket.org/lucee/lucee/wiki/Lucee5_Extensions lists three
options for extension installation; Admin & Deploy Folder which require
post-startup actions, and a JVM Argument option, which i’m assuming prompts
lucee to go to the extension provider and download the required extension,
which doesn’t work if your lucee server is firewalled.

None of those options allow me to create a war that bundles the extension
without including the extension statically in WEB-INF/lucee/deploy

On Mon, 20 Apr 2015 at 12:22 Michael Offner <@Michael_Offner> wrote:

that is what is possible
https://bitbucket.org/lucee/lucee/wiki/Lucee5_Extensions

Micha

On Mon, Apr 20, 2015 at 12:57 PM, Chris Blackwell <@Chris_Blackwell> wrote:

And i’m not sure how that helps me once i have built the extension. I
don’t want to copy it to a location in my source code, or have to deploy it
seperately

i just want it as a dependency.
something like

<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>lucee-core</artifactId>
  <version>4.5.1.008</version>
<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>hibernate-orm</artifactId>
  <version>1.0.0</version>

Can that be done ?

On Mon, 20 Apr 2015 at 11:50 Chris Blackwell <@Chris_Blackwell> wrote:

unfortunately the build for the hibernate extension isn’t portable, as
it has dependencies on other code you have locally.

BUILD FAILED
/Users/chris/repos/lucee-hibernate-extension/build.xml:78:
/Users/mic/Projects/Railo/Source2/railo/railo-java/libs does not exist.

Isn’t this what maven solves… ?

On Mon, 20 Apr 2015 at 10:45 Michael Offner <@Michael_Offner> wrote:

No there are no plans to do this, because this is how it already
works :wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make “git clone
    https://bitbucket.org/lucee/hibernate-extension.git
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be
copied to the extension provider or simply copied to
/deploy and Lucee then installs automatically.

All extension we do have a ant build script that allows to build them
without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the
modern (for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension
and you call for example “ant classic” to only get a old one.

Micha

On Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell> wrote:

If functionality like ORM is to be moved from the core to extensions
then there needs to be a way to declaratively build a Lucee app, as a WAR
for example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEBzYxXO2cjUM%2B4-e_4kCZ7VeOrD1mwejq7UYagF3L3bSAA%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEBzYxXO2cjUM%2B4-e_4kCZ7VeOrD1mwejq7UYagF3L3bSAA%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfTroJMt%3Db8bG8Nk1waDdXNpZnwckf87yJUUT-JaY%2BsUSZQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfTroJMt%3Db8bG8Nk1waDdXNpZnwckf87yJUUT-JaY%2BsUSZQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEBwTdtmaZsqFt4SK3xxt7RTx8_TwPaRZXUd582VrjRwS_A%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEBwTdtmaZsqFt4SK3xxt7RTx8_TwPaRZXUd582VrjRwS_A%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

No there are no plans to do this, because this is how it already works :wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make “git clone https://bitbucket.org/lucee/hibernate-extension.git
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be copied
to the extension provider or simply copied to /deploy and
Lucee then installs automatically.

All extension we do have a ant build script that allows to build them
without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the modern
(for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension and you
call for example “ant classic” to only get a old one.

MichaOn Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell> wrote:

If functionality like ORM is to be moved from the core to extensions then
there needs to be a way to declaratively build a Lucee app, as a WAR for
example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a maven
repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

sorry a push was missing, do a pull and try again …

MichaOn Mon, Apr 20, 2015 at 12:50 PM, Chris Blackwell <@Chris_Blackwell> wrote:

unfortunately the build for the hibernate extension isn’t portable, as it
has dependencies on other code you have locally.

BUILD FAILED
/Users/chris/repos/lucee-hibernate-extension/build.xml:78:
/Users/mic/Projects/Railo/Source2/railo/railo-java/libs does not exist.

Isn’t this what maven solves… ?

On Mon, 20 Apr 2015 at 10:45 Michael Offner <@Michael_Offner> wrote:

No there are no plans to do this, because this is how it already works :wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make “git clone https://bitbucket.org/lucee/hibernate-extension.git
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be
copied to the extension provider or simply copied to
/deploy and Lucee then installs automatically.

All extension we do have a ant build script that allows to build them
without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the modern
(for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension and
you call for example “ant classic” to only get a old one.

Micha

On Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell> wrote:

If functionality like ORM is to be moved from the core to extensions
then there needs to be a way to declaratively build a Lucee app, as a WAR
for example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfToQ7ESS9SaN4DCko9U1Ef5yiWLW68h6A2VdYOv%3D8C3Ung%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfToQ7ESS9SaN4DCko9U1Ef5yiWLW68h6A2VdYOv%3D8C3Ung%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

Well not quite.
https://bitbucket.org/lucee/lucee/wiki/Lucee5_Extensions lists three
options for extension installation; Admin & Deploy Folder which require
post-startup actions, and a JVM Argument option, which i’m assuming prompts
lucee to go to the extension provider and download the required extension,
which doesn’t work if your lucee server is firewalled.

None of those options allow me to create a war that bundles the extension
without including the extension statically in WEB-INF/lucee/deployOn Mon, 20 Apr 2015 at 12:22 Michael Offner <@Michael_Offner> wrote:

that is what is possible
https://bitbucket.org/lucee/lucee/wiki/Lucee5_Extensions

Micha

On Mon, Apr 20, 2015 at 12:57 PM, Chris Blackwell <@Chris_Blackwell> wrote:

And i’m not sure how that helps me once i have built the extension. I
don’t want to copy it to a location in my source code, or have to deploy it
seperately

i just want it as a dependency.
something like

<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>lucee-core</artifactId>
  <version>4.5.1.008</version>
<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>hibernate-orm</artifactId>
  <version>1.0.0</version>

Can that be done ?

On Mon, 20 Apr 2015 at 11:50 Chris Blackwell <@Chris_Blackwell> wrote:

unfortunately the build for the hibernate extension isn’t portable, as
it has dependencies on other code you have locally.

BUILD FAILED
/Users/chris/repos/lucee-hibernate-extension/build.xml:78:
/Users/mic/Projects/Railo/Source2/railo/railo-java/libs does not exist.

Isn’t this what maven solves… ?

On Mon, 20 Apr 2015 at 10:45 Michael Offner <@Michael_Offner> wrote:

No there are no plans to do this, because this is how it already works
:wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make “git clone https://bitbucket.org/lucee/hibernate-extension.git
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be
copied to the extension provider or simply copied to
/deploy and Lucee then installs automatically.

All extension we do have a ant build script that allows to build them
without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the modern
(for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension and
you call for example “ant classic” to only get a old one.

Micha

On Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell> wrote:

If functionality like ORM is to be moved from the core to extensions
then there needs to be a way to declaratively build a Lucee app, as a WAR
for example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEBzYxXO2cjUM%2B4-e_4kCZ7VeOrD1mwejq7UYagF3L3bSAA%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEBzYxXO2cjUM%2B4-e_4kCZ7VeOrD1mwejq7UYagF3L3bSAA%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

please see between the lines

Micha

so by moving features out of the core into extensions, WAR packaging
essentially gets broken? I’m sure this wasn’t your intention.

I don’t think an EAR file helps matters, Lucee should package perfectly
well as a WAR, and extensions should be able to be included in that war for
automatic deployment.

as you still can simply add the .lex file to WEB-INF/luceecontext/deploy/

If .lex files in WEB-INF/lucee/deploy get automatically deployed when the
lucee starts, that’s half the battle right there. What about extending
that to find any .lex files on the classpath. That way they could just be
dropped in WEB-INF/lib by maven and they’ll get found.

a .lex file is not a jar or a bundle, it is a lucee extension that maybe
contain one or more jar files

The alternative is to use maven-dependency-plugin to copy the .lex files
to /WEB-INF/lucee/deploy in the package phase, but that requires a lot more
configuration than just declaring the dependency

please raise a ticket to support this, so we can look into itOn Mon, Apr 20, 2015 at 2:54 PM, Chris Blackwell <@Chris_Blackwell> wrote:

On Mon, 20 Apr 2015 13:07 Michael Offner <@Michael_Offner> wrote:

Lucee extension are not compatible with war files, this is also something
completely different.
maybe an ear file would be more what you are looking for.
Anyway, that is what we support for Lucee 5, of course we are open to
discuss other possibilities for the future.

Micha

On Mon, Apr 20, 2015 at 1:38 PM, Chris Blackwell <@Chris_Blackwell> wrote:

Well not quite.
https://bitbucket.org/lucee/lucee/wiki/Lucee5_Extensions lists three
options for extension installation; Admin & Deploy Folder which require
post-startup actions, and a JVM Argument option, which i’m assuming prompts
lucee to go to the extension provider and download the required extension,
which doesn’t work if your lucee server is firewalled.

None of those options allow me to create a war that bundles the
extension without including the extension statically in WEB-INF/lucee/deploy

On Mon, 20 Apr 2015 at 12:22 Michael Offner <@Michael_Offner> wrote:

that is what is possible
https://bitbucket.org/lucee/lucee/wiki/Lucee5_Extensions

Micha

On Mon, Apr 20, 2015 at 12:57 PM, Chris Blackwell <@Chris_Blackwell> wrote:

And i’m not sure how that helps me once i have built the extension. I
don’t want to copy it to a location in my source code, or have to deploy it
seperately

i just want it as a dependency.
something like

<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>lucee-core</artifactId>
  <version>4.5.1.008</version>
<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>hibernate-orm</artifactId>
  <version>1.0.0</version>

Can that be done ?

On Mon, 20 Apr 2015 at 11:50 Chris Blackwell <@Chris_Blackwell> wrote:

unfortunately the build for the hibernate extension isn’t portable,
as it has dependencies on other code you have locally.

BUILD FAILED
/Users/chris/repos/lucee-hibernate-extension/build.xml:78:
/Users/mic/Projects/Railo/Source2/railo/railo-java/libs does not exist.

Isn’t this what maven solves… ?

On Mon, 20 Apr 2015 at 10:45 Michael Offner <@Michael_Offner> wrote:

No there are no plans to do this, because this is how it already
works :wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make “git clone
    https://bitbucket.org/lucee/hibernate-extension.git
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be
copied to the extension provider or simply copied to
/deploy and Lucee then installs automatically.

All extension we do have a ant build script that allows to build
them without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the
modern (for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension
and you call for example “ant classic” to only get a old one.

Micha

On Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell wrote:

If functionality like ORM is to be moved from the core to
extensions then there needs to be a way to declaratively build a Lucee app,
as a WAR for example, and include the extensions that you’re cfml code is
going to require.

It would be ideal (for me anyway :slight_smile: to see extensions published to
a maven repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEBzYxXO2cjUM%2B4-e_4kCZ7VeOrD1mwejq7UYagF3L3bSAA%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEBzYxXO2cjUM%2B4-e_4kCZ7VeOrD1mwejq7UYagF3L3bSAA%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfTroJMt%3Db8bG8Nk1waDdXNpZnwckf87yJUUT-JaY%2BsUSZQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfTroJMt%3Db8bG8Nk1waDdXNpZnwckf87yJUUT-JaY%2BsUSZQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEBwTdtmaZsqFt4SK3xxt7RTx8_TwPaRZXUd582VrjRwS_A%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEBwTdtmaZsqFt4SK3xxt7RTx8_TwPaRZXUd582VrjRwS_A%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfTohC5UiOKdBzUs85U1C%2Bx4m5yggKQVuexf29kquM138-Q%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfTohC5UiOKdBzUs85U1C%2Bx4m5yggKQVuexf29kquM138-Q%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

that is what is possible
https://bitbucket.org/lucee/lucee/wiki/Lucee5_Extensions

MichaOn Mon, Apr 20, 2015 at 12:57 PM, Chris Blackwell <@Chris_Blackwell> wrote:

And i’m not sure how that helps me once i have built the extension. I
don’t want to copy it to a location in my source code, or have to deploy it
seperately

i just want it as a dependency.
something like

<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>lucee-core</artifactId>
  <version>4.5.1.008</version>
<dependency>
  <groupId>org.lucee</groupId>
  <artifactId>hibernate-orm</artifactId>
  <version>1.0.0</version>

Can that be done ?

On Mon, 20 Apr 2015 at 11:50 Chris Blackwell <@Chris_Blackwell> wrote:

unfortunately the build for the hibernate extension isn’t portable, as it
has dependencies on other code you have locally.

BUILD FAILED
/Users/chris/repos/lucee-hibernate-extension/build.xml:78:
/Users/mic/Projects/Railo/Source2/railo/railo-java/libs does not exist.

Isn’t this what maven solves… ?

On Mon, 20 Apr 2015 at 10:45 Michael Offner <@Michael_Offner> wrote:

No there are no plans to do this, because this is how it already works
:wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make “git clone https://bitbucket.org/lucee/hibernate-extension.git
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be
copied to the extension provider or simply copied to
/deploy and Lucee then installs automatically.

All extension we do have a ant build script that allows to build them
without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the modern
(for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension and
you call for example “ant classic” to only get a old one.

Micha

On Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell> wrote:

If functionality like ORM is to be moved from the core to extensions
then there needs to be a way to declaratively build a Lucee app, as a WAR
for example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAB%3DtfTrDy4foVHR-u%3Dc_Z31Gf3YZ-uh%2B5w5_NdMpAP7uEpveig%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

unfortunately the build for the hibernate extension isn’t portable, as it
has dependencies on other code you have locally.

BUILD FAILED
/Users/chris/repos/lucee-hibernate-extension/build.xml:78:
/Users/mic/Projects/Railo/Source2/railo/railo-java/libs does not exist.

Isn’t this what maven solves… ?On Mon, 20 Apr 2015 at 10:45 Michael Offner <@Michael_Offner> wrote:

No there are no plans to do this, because this is how it already works :wink:
Not with Maven but with Ant.

Steps to build the hibernate extension

  1. make “git clone https://bitbucket.org/lucee/hibernate-extension.git
  2. got to the directory created and do “ant”

As result of this you get a .lex file (Lucee EXtension) that can be copied
to the extension provider or simply copied to /deploy and
Lucee then installs automatically.

All extension we do have a ant build script that allows to build them
without any environment relation necessary.
Some build script even build the classic (for Lucee 4.5) and the modern
(for Lucee 5.0) extension like this one
https://bitbucket.org/lucee/memcached/src

in that case you simply call “ant” to get a new and a old extension and
you call for example “ant classic” to only get a old one.

Micha

On Mon, Apr 20, 2015 at 10:48 AM, Chris Blackwell <@Chris_Blackwell> wrote:

If functionality like ORM is to be moved from the core to extensions then
there needs to be a way to declaratively build a Lucee app, as a WAR for
example, and include the extensions that you’re cfml code is going to
require.

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

Are there any plans to do something like this?


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/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3e09dc03-0854-4aa6-9b2e-f859b92b898d%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


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/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com
https://groups.google.com/d/msgid/lucee/CAG%2BEEByF1u_7BV_Jn9y%2BuAPSPqdawCq0U9bYPGRta5S9QjATzQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

Den, are there any plans to get cfmlprojects updated more frequently, its
currently @ 4.5.1.008 which is a few updates behind. And what about getting
some 5.x snapshot builds ?On Mon, 20 Apr 2015 at 10:15 denstar <@denstar> wrote:

On 4/20/15 2:48 AM, Chris Blackwell wrote:

If functionality like ORM is to be moved from the core to extensions
then there needs to be a way to declaratively build a Lucee app, as a
WAR for example, and include the extensions that you’re cfml code is
going to require.

Agreed!

It would be ideal (for me anyway :slight_smile: to see extensions published to a
maven repo, which can simply be added to a pom as a dependency.

It’s ideal for me too-- I loves my dependencies. =)

Are there any plans to do something like this?

I’m happy to say that there are more than just plans. Micha is building
some stuff in, I’m building some stuff out (maven, and a few other repo
formats), and Ortus is working on ForgeBox, which is kind of an NPMish
deal. Color me stoked, and CFML being so hip it will have trouble
seeing over its pelvis.

-Den


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/5534C3C4.5050109%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Yup, aiming for having it updating before the conferences next month.

We need to think about the snapshots-- I’ve got them squared away in the
build, but it doesn’t quite jive with bumping versions for preview/dev,
which are themselves snapshot-ish.

-DenOn 4/20/15 3:19 AM, Chris Blackwell wrote:

Den, are there any plans to get cfmlprojects updated more frequently,
its currently @ 4.5.1.008 which is a few updates behind. And what about
getting some 5.x snapshot builds ?

The current implementation is a big improvement about the old extension type
First of all, you can install them without user interaction. On one side
this is a limitation on the other side it opens a lot of possibilities.

One idea is also that you can add dependencies in your
application.cfc/server.cfc so that Lucee install this dependency if
necessary on the fly.
So if you have a orm app you have something like this in your
application.cfc.

this.extensions=[{id:“tgj575;fhhb”,version:“1.2.3.4”}];

There are a lot of ideas floating around atm, so I would prefer not to rush
to fast into it.
This will for sure be a topic we raise on the “Lucee tech board”. So best
raise a ticket about it with as many details as possible, so it get not
forget…

Before I forget, Lucee extension are late binding, so you cannot add them
as part of the build process of Lucee, so whatever we do, the extension
will always be physically separated.
That is important also for the license, if we had a early binding with the
core, the extension get infected with lgpl.

MichaAm Dienstag, 21. April 2015 schrieb denstar :

On 4/20/15 6:54 AM, Chris Blackwell wrote:

If .lex files in WEB-INF/lucee/deploy get automatically deployed when
the lucee starts, that’s half the battle right there. What about
extending that to find any .lex files on the classpath. That way they
could just be dropped in WEB-INF/lib by maven and they’ll get found.

Not a bad idea. I think the .lex would prevent unintentional loading.
Some deployers are kind of aggressive about zips though.

The alternative is to use maven-dependency-plugin to copy the .lex files
to /WEB-INF/lucee/deploy in the package phase, but that requires a lot
more configuration than just declaring the dependency

We could have the archtype/parent do it, to mitigate the configuration
aspect – we’ve already got a few doing similar stuff – but that’s not
as flexible as the straight dependency.

-Den


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 <javascript:;>.
To post to this group, send email to lucee@googlegroups.com <javascript:;>
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/5535F66B.9080400%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

If .lex files in WEB-INF/lucee/deploy get automatically deployed when
the lucee starts, that’s half the battle right there. What about
extending that to find any .lex files on the classpath. That way they
could just be dropped in WEB-INF/lib by maven and they’ll get found.

Not a bad idea. I think the .lex would prevent unintentional loading.
Some deployers are kind of aggressive about zips though.

The alternative is to use maven-dependency-plugin to copy the .lex files
to /WEB-INF/lucee/deploy in the package phase, but that requires a lot
more configuration than just declaring the dependency

We could have the archtype/parent do it, to mitigate the configuration
aspect – we’ve already got a few doing similar stuff – but that’s not
as flexible as the straight dependency.

-DenOn 4/20/15 6:54 AM, Chris Blackwell wrote:

I’ve created a ticket
https://bitbucket.org/lucee/lucee/issue/307/extensions-and-war-packagingOn Tuesday, 21 April 2015 12:29:08 UTC+1, Micha wrote:

The current implementation is a big improvement about the old extension
type
First of all, you can install them without user interaction. On one side
this is a limitation on the other side it opens a lot of possibilities.

One idea is also that you can add dependencies in your
application.cfc/server.cfc so that Lucee install this dependency if
necessary on the fly.
So if you have a orm app you have something like this in your
application.cfc.

this.extensions=[{id:“tgj575;fhhb”,version:“1.2.3.4”}];

There are a lot of ideas floating around atm, so I would prefer not to
rush to fast into it.
This will for sure be a topic we raise on the “Lucee tech board”. So best
raise a ticket about it with as many details as possible, so it get not
forget…

Before I forget, Lucee extension are late binding, so you cannot add them
as part of the build process of Lucee, so whatever we do, the extension
will always be physically separated.
That is important also for the license, if we had a early binding with the
core, the extension get infected with lgpl.

Micha

Am Dienstag, 21. April 2015 schrieb denstar :

On 4/20/15 6:54 AM, Chris Blackwell wrote:

If .lex files in WEB-INF/lucee/deploy get automatically deployed when
the lucee starts, that’s half the battle right there. What about
extending that to find any .lex files on the classpath. That way they
could just be dropped in WEB-INF/lib by maven and they’ll get found.

Not a bad idea. I think the .lex would prevent unintentional loading.
Some deployers are kind of aggressive about zips though.

The alternative is to use maven-dependency-plugin to copy the .lex files
to /WEB-INF/lucee/deploy in the package phase, but that requires a lot
more configuration than just declaring the dependency

We could have the archtype/parent do it, to mitigate the configuration
aspect – we’ve already got a few doing similar stuff – but that’s not
as flexible as the straight dependency.

-Den


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/5535F66B.9080400%40gmail.com.
For more options, visit https://groups.google.com/d/optout.