Building Lucee with different Java Versions

The build process already works with Java 6 (default) and 7, i will now
look into the problems with Java 8.

Micha

Johnathan, you can start
here: https://bitbucket.org/lucee/lucee/wiki/Build%20from%20source

For me, with intellij, it was as simple as forking the repo, cloning it,
creating a project pointing to that folder (im using java 8), going to ant
build and properties to increase the ram it can use and then running the
full build.On Thursday, February 5, 2015 at 9:34:33 AM UTC-6, Jonathan Brookins wrote:

What steps are necessary for me to try playing with the Lucee code myself?
Although I’m not really a Java programmer I’ve been working with Scala and
using Intellij to do it. What do I need to do to get to the point where I
can modify and build the code?

Thanks!

I was able to successfully build with 8 today - but I am unable to get the
tests to work.

I set up the following mappings in the server admin:

/lucee-tests E:\home\java\lucee\lucee\tests Resource Always
/testcases E:\home\java\lucee\lucee\tests\testcases Resource Always

But when I try to browse to:

http://localhost:8888/lucee-tests/index.cfm I receive the following error:

Lucee 4.5.0.043 Error (expression)
Message invalid component definition, can’t find component
[testbox.system.testing.TestBox]
Stacktrace The Error Occurred in
E:\home\java\lucee\lucee\tests\index.cfm: line 57
55:
56: // Prepare TestBox
57: testbox = new testbox.system.testing.TestBox();
58:
59:

Java Stacktrace invalid component definition, can’t find component
[testbox.system.testing.TestBox]
at lucee.runtime.component.ComponentLoader.load(Unknown Source):-1
at lucee.runtime.component.ComponentLoader.loadComponent(Unknown
Source):-1
at lucee.runtime.PageContextImpl.loadComponent(Unknown Source):-1
at lucee.runtime.functions.other.CreateObject.doComponent(Unknown
Source):-1
at lucee.runtime.functions.other._CreateComponent.call(Unknown Source):-1
at index_cfm$cf.call(E:\home\java\lucee\lucee\tests\index.cfm:57):57
at lucee.runtime.PageContextImpl.doInclude(Unknown Source):-1
at lucee.runtime.PageContextImpl.doInclude(Unknown Source):-1
at lucee.runtime.listener.ModernAppListener._onRequest(Unknown Source):-1
at lucee.runtime.listener.MixedAppListener.onRequest(Unknown Source):-1
at lucee.runtime.PageContextImpl.execute(Unknown Source):-1
at lucee.runtime.PageContextImpl.execute(Unknown Source):-1
at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(Unknown Source):-1
at lucee.loader.servlet.CFMLServlet.service(Unknown Source):-1
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848):848
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686):686
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501):501
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137):137
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557):557
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231):231
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086):1086
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428):428
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193):193
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020):1020
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135):135
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255):255
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154):154
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116):116
at org.eclipse.jetty.server.Server.handle(Server.java:370):370
at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489):489
at
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949):949
at
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011):1011
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644):644
at
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235):235
at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82):82
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668):668
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52):52
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608):608
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543):543
at java.lang.Thread.run(Unknown Source):-1

Note the updated version number is from me bumping the version in info.ini.
And I am testing with the express jetty version (but the same thing
happened when I tried copying the jars into my existing tomcat
installation).

I think it may have something to do with testbox.ra not being loaded
properly, but I’m not certain how to fix it - I’ve never used the ra files
before (railo archive I suppose?).

I’m sure its something small i’m missing, any help would be appreciated.

I’ve tried a few things, even to the point of trying to provideOn Monday, February 2, 2015 at 4:37:58 AM UTC-6, Micha wrote:

The build process already works with Java 6 (default) and 7, i will now
look into the problems with Java 8.

Micha

What steps are necessary for me to try playing with the Lucee code myself?
Although I’m not really a Java programmer I’ve been working with Scala and
using Intellij to do it. What do I need to do to get to the point where I
can modify and build the code?

Thanks!

NP. A few of us in the ##coldfusion irc room on freenode have been playing
around with building and hacking on lucee, feel free to drop in there if
you have problems questions. No guarantees we will have answers though!

One thing I have questions about is if it is possible to interactively
debug lucee while it is evaluating CFML. I don’t expect that it is
possible, but I would be happy to be proven wrong!On Thursday, February 5, 2015 at 10:55:12 AM UTC-6, Jonathan Brookins wrote:

Thanks, Ryan! I’ll give it a shot when I get some free time.

On Thursday, February 5, 2015 at 10:40:46 AM UTC-5, Ryan Guill wrote:

Johnathan, you can start here:
https://bitbucket.org/lucee/lucee/wiki/Build%20from%20source

For me, with intellij, it was as simple as forking the repo, cloning it,
creating a project pointing to that folder (im using java 8), going to ant
build and properties to increase the ram it can use and then running the
full build.

On Thursday, February 5, 2015 at 9:34:33 AM UTC-6, Jonathan Brookins wrote:

What steps are necessary for me to try playing with the Lucee code
myself? Although I’m not really a Java programmer I’ve been working with
Scala and using Intellij to do it. What do I need to do to get to the
point where I can modify and build the code?

Thanks!

Please read my answers between the lines.

Micha

I started down the path of supplying my own version of testbox but it
seems the version included is a bit out of date, 1.1 vs 2.1, and some of
the packages in testbox have changed since (old:
testbox.system.testing.TestBox vs new: testbox.system.TestBox) which
affects quite a few files.

I will ask brad to jump in

I tried copying testbox.ra into the webroot, and also copying it and
renaming it to testbox.lar and it doesn’t seem to make a difference.

A .ra is build for the Railo environment, it will not work for inside
Lucee. Giving a dog a cats name does not make him catch mice.

What is the best way to create a component archive from testbox?

Inside the admin on the component page create a mapping for testbox, then
export the archive in that mapping.

I suppose I would need to go find a copy of version 1.1 to use?

Yeas as long the test case relay on that, but I will ask Luis and brad to
jump in on that …

I tried renaming the .ra file to .zip and opening it - there are some
.class files in there - but could I make an lar out of that?

No cat…Am Donnerstag, 5. Februar 2015 schrieb Ryan Guill :

On Wednesday, February 4, 2015 at 6:36:21 PM UTC-6, Micha wrote:

we should use a Lucee archive for testbox
(see: https://bitbucket.org/lucee/lucee/src/
5a0a12cf7e79b9419e3e3e78634c8058b82b292a/tests/Application.
cfc?at=master#cl-30)
but like you can see there, there is still a railo archive defined (.ra
instead of .lar)…

workaround: copy testbox into the webroot
solution: create a component archive from testbox and attach in the
aplication.cfc

Micha

On Thu, Feb 5, 2015 at 1:29 AM, Ryan Guill ryan...@gmail.com wrote:

I was able to successfully build with 8 today - but I am unable to get
the tests to work.

I set up the following mappings in the server admin:

/lucee-tests E:\home\java\lucee\lucee\tests Resource Always
/testcases E:\home\java\lucee\lucee\tests\testcases Resource Always

But when I try to browse to:

http://localhost:8888/lucee-tests/index.cfm I receive the following
error:

Lucee 4.5.0.043 Error (expression)
Message invalid component definition, can’t find component
[testbox.system.testing.TestBox]
Stacktrace The Error Occurred in
E:\home\java\lucee\lucee\tests\index.cfm: line 57
55:
56: // Prepare TestBox
57: testbox = new testbox.system.testing.TestBox();
58:
59:

Java Stacktrace invalid component definition, can’t find component
[testbox.system.testing.TestBox]
at lucee.runtime.component.ComponentLoader.load(Unknown Source):-1
at lucee.runtime.component.ComponentLoader.loadComponent(Unknown
Source):-1
at lucee.runtime.PageContextImpl.loadComponent(Unknown Source):-1
at lucee.runtime.functions.other.CreateObject.doComponent(Unknown
Source):-1
at lucee.runtime.functions.other._CreateComponent.call(Unknown
Source):-1
at index_cfm$cf.call(E:\home\java\lucee\lucee\tests\index.cfm:57):57
at lucee.runtime.PageContextImpl.doInclude(Unknown Source):-1
at lucee.runtime.PageContextImpl.doInclude(Unknown Source):-1
at lucee.runtime.listener.ModernAppListener._onRequest(Unknown
Source):-1
at lucee.runtime.listener.MixedAppListener.onRequest(Unknown
Source):-1
at lucee.runtime.PageContextImpl.execute(Unknown Source):-1
at lucee.runtime.PageContextImpl.execute(Unknown Source):-1
at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(Unknown Source):-1
at lucee.loader.servlet.CFMLServlet.service(Unknown Source):-1
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848):848
at org.eclipse.jetty.servlet.ServletHolder.handle(
ServletHolder.java:686):686
at org.eclipse.jetty.servlet.ServletHandler.doHandle(
ServletHandler.java:501):501
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
ScopedHandler.java:137):137
at org.eclipse.jetty.security.SecurityHandler.handle(
SecurityHandler.java:557):557
at org.eclipse.jetty.server.session.SessionHandler.
doHandle(SessionHandler.java:231):231
at org.eclipse.jetty.server.handler.ContextHandler.
doHandle(ContextHandler.java:1086):1086
at org.eclipse.jetty.servlet.ServletHandler.doScope(
ServletHandler.java:428):428
at org.eclipse.jetty.server.session.SessionHandler.
doScope(SessionHandler.java:193):193
at org.eclipse.jetty.server.handler.ContextHandler.
doScope(ContextHandler.java:1020):1020
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
ScopedHandler.java:135):135
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(
ContextHandlerCollection.java:255):255
at org.eclipse.jetty.server.handler.HandlerCollection.
handle(HandlerCollection.java:154):154
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
HandlerWrapper.java:116):116
at org.eclipse.jetty.server.Server.handle(Server.java:370):370
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(
AbstractHttpConnection.java:489):489
at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(
AbstractHttpConnection.java:949):949
at org.eclipse.jetty.server.AbstractHttpConnection$
RequestHandler.headerComplete(AbstractHttpConnection.java:1011):1011
at org.eclipse.jetty.http.HttpParser.parseNext(
HttpParser.java:644):644
at org.eclipse.jetty.http.HttpParser.parseAvailable(
HttpParser.java:235):235
at org.eclipse.jetty.server.AsyncHttpConnection.handle(
AsyncHttpConnection.java:82):82
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(
SelectChannelEndPoint.java:668):668
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(
SelectChannelEndPoint.java:52):52
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
QueuedThreadPool.java:608):608
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(
QueuedThreadPool.java:543):543
at java.lang.Thread.run(Unknown Source):-1

Note the updated version number is from me bumping the version in
info.ini. And I am testing with the express jetty version (but the same
thing happened when I tried copying the jars into my existing tomcat
installation).

I think it may have something to do with testbox.ra not being loaded
properly, but I’m not certain how to fix it - I’ve never used the ra files
before (railo archive I suppose?).

I’m sure its something small i’m missing, any help would be appreciated.

I’ve tried a few things, even to the point of trying to provide

On Monday, February 2, 2015 at 4:37:58 AM UTC-6, Micha wrote:

The build process already works with Java 6 (default) and 7, i will now
look into the problems with Java 8.

Micha


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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/lucee/87bdea64-23a5-4573-b333-9921430c1850%40googlegroups.com
https://groups.google.com/d/msgid/lucee/87bdea64-23a5-4573-b333-9921430c1850%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
<javascript:_e(%7B%7D,‘cvml’,‘lucee%2Bunsubscribe@googlegroups.com’);>.
To post to this group, send email to lucee@googlegroups.com
<javascript:_e(%7B%7D,‘cvml’,‘lucee@googlegroups.com’);>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/2608ab88-e695-419c-8fa6-73fb4d8c1100%40googlegroups.com
https://groups.google.com/d/msgid/lucee/2608ab88-e695-419c-8fa6-73fb4d8c1100%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

Thanks, Ryan! I’ll give it a shot when I get some free time.On Thursday, February 5, 2015 at 10:40:46 AM UTC-5, Ryan Guill wrote:

Johnathan, you can start here:
https://bitbucket.org/lucee/lucee/wiki/Build%20from%20source

For me, with intellij, it was as simple as forking the repo, cloning it,
creating a project pointing to that folder (im using java 8), going to ant
build and properties to increase the ram it can use and then running the
full build.

On Thursday, February 5, 2015 at 9:34:33 AM UTC-6, Jonathan Brookins wrote:

What steps are necessary for me to try playing with the Lucee code
myself? Although I’m not really a Java programmer I’ve been working with
Scala and using Intellij to do it. What do I need to do to get to the
point where I can modify and build the code?

Thanks!

we should use a Lucee archive for testbox
(see:
https://bitbucket.org/lucee/lucee/src/5a0a12cf7e79b9419e3e3e78634c8058b82b292a/tests/Application.cfc?at=master#cl-30
)
but like you can see there, there is still a railo archive defined (.ra
instead of .lar)…

workaround: copy testbox into the webroot
solution: create a component archive from testbox and attach in the
aplication.cfc

MichaOn Thu, Feb 5, 2015 at 1:29 AM, Ryan Guill <@Ryan_Guill> wrote:

I was able to successfully build with 8 today - but I am unable to get the
tests to work.

I set up the following mappings in the server admin:

/lucee-tests E:\home\java\lucee\lucee\tests Resource Always
/testcases E:\home\java\lucee\lucee\tests\testcases Resource Always

But when I try to browse to:

http://localhost:8888/lucee-tests/index.cfm I receive the following error:

Lucee 4.5.0.043 Error (expression)
Message invalid component definition, can’t find component
[testbox.system.testing.TestBox]
Stacktrace The Error Occurred in
E:\home\java\lucee\lucee\tests\index.cfm: line 57
55:
56: // Prepare TestBox
57: testbox = new testbox.system.testing.TestBox();
58:
59:

Java Stacktrace invalid component definition, can’t find component
[testbox.system.testing.TestBox]
at lucee.runtime.component.ComponentLoader.load(Unknown Source):-1
at lucee.runtime.component.ComponentLoader.loadComponent(Unknown
Source):-1
at lucee.runtime.PageContextImpl.loadComponent(Unknown Source):-1
at lucee.runtime.functions.other.CreateObject.doComponent(Unknown
Source):-1
at lucee.runtime.functions.other._CreateComponent.call(Unknown
Source):-1
at index_cfm$cf.call(E:\home\java\lucee\lucee\tests\index.cfm:57):57
at lucee.runtime.PageContextImpl.doInclude(Unknown Source):-1
at lucee.runtime.PageContextImpl.doInclude(Unknown Source):-1
at lucee.runtime.listener.ModernAppListener._onRequest(Unknown
Source):-1
at lucee.runtime.listener.MixedAppListener.onRequest(Unknown Source):-1
at lucee.runtime.PageContextImpl.execute(Unknown Source):-1
at lucee.runtime.PageContextImpl.execute(Unknown Source):-1
at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(Unknown Source):-1
at lucee.loader.servlet.CFMLServlet.service(Unknown Source):-1
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848):848
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686):686
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501):501
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137):137
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557):557
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231):231
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086):1086
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428):428
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193):193
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020):1020
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135):135
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255):255
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154):154
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116):116
at org.eclipse.jetty.server.Server.handle(Server.java:370):370
at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489):489
at
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949):949
at
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011):1011
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644):644
at
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235):235
at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82):82
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668):668
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52):52
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608):608
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543):543
at java.lang.Thread.run(Unknown Source):-1

Note the updated version number is from me bumping the version in
info.ini. And I am testing with the express jetty version (but the same
thing happened when I tried copying the jars into my existing tomcat
installation).

I think it may have something to do with testbox.ra not being loaded
properly, but I’m not certain how to fix it - I’ve never used the ra files
before (railo archive I suppose?).

I’m sure its something small i’m missing, any help would be appreciated.

I’ve tried a few things, even to the point of trying to provide

On Monday, February 2, 2015 at 4:37:58 AM UTC-6, Micha wrote:

The build process already works with Java 6 (default) and 7, i will now
look into the problems with Java 8.

Micha


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/87bdea64-23a5-4573-b333-9921430c1850%40googlegroups.com
https://groups.google.com/d/msgid/lucee/87bdea64-23a5-4573-b333-9921430c1850%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

Looking forward to it!On Thursday, February 5, 2015 at 6:42:05 PM UTC-6, Denny Valliant wrote:

On Thu, Feb 5, 2015 at 9:57 AM, Ryan Guill wrote:

One thing I have questions about is if it is possible to interactively
debug lucee while it is evaluating CFML. I don’t expect that it is
possible, but I would be happy to be proven wrong!

It’s totally possible, and is one of the things on the list for the new
build docs-- it’ll be Eclipse-centric, as that’s what I like, but the same
basic principles should apply to NB, for instance.

-Den

One thing I have questions about is if it is possible to interactively
debug lucee while it is evaluating CFML. I don’t expect that it is
possible, but I would be happy to be proven wrong!

It’s totally possible, and is one of the things on the list for the new
build docs-- it’ll be Eclipse-centric, as that’s what I like, but the same
basic principles should apply to NB, for instance.

-DenOn Thu, Feb 5, 2015 at 9:57 AM, Ryan Guill wrote: