My installing/building/contributing to lucee 5 from source feedback

I know this is a beta release, but I wanted to check it out to see if it
will be ready for my app soon.

I assume I am to use these urls now if I send ideas/changes:
Jira: https://luceeserver.atlassian.net/secure/Dashboard.jspa

Lucee 5.0 master branch - https://github.com/lucee/Lucee
Lucee 4.x master branch - https://bitbucket.org/lucee/lucee - it seems the
develop branch is no longer used for lucee 5 development.
and this google group,
but there is also now a more technical debate forum? http://lang.lucee.org/

It seems that I can only build Lucee 5 from the develop branch on
bitbucket. The new github version doesn’t allow simply running ant,
because the build xml is missing or incomplete. I’m not sure how to get
access to a functional version of the latest work-in-progress code to
modify/test further, and I’m sure you’d rather get feedback on the newest
version of 5.0.

The lucee 5 ant build claims to finish successfully, but after patching the
server with the .loc file in the contexts directory, and restarting tomcat,
the railo admin appears to be missing or at a unknown new url. I’m
compiling with jdk 7 on windows.

This is the admin url I use now.
http://127.0.0.1:8888/lucee/admin/server.cfm

My large cfml app appears to work correctly on the stable release version
of Lucee 4.5, with the tomcat 8 installer off the official web site, but I
had to give the server several hundred mb more memory to start up my app
compared to Railo 4.2/tomcat 7.

My large cfml app doesn’t work on the beta release of Lucee 5 yet, and I
don’t know why because it shows a blank white screen instead of exceptions,
and nothing is logged in tomcat logs or railo web context logs.

I may have to walk through line by line writing echo(‘test’);abort in my
app to find what causes the empty response problem - and this would only be
to help you further develop or for me to fix my mistakes. It might be
related to the objectsave/objectload compatibility change, but I’m not sure
yet.

I also found that the documentation that says to put lucee.jar
and org-apache-felix-main-4-2-1.jar in tomcat/lib/ext/ is wrong. I had to
put those in tomcat/lib or it failed to start cfml with an error in tomcat
catalina.out that it couldn’t find the servlets for rest, cfml or lucee: .
I have no idea what the ext/ directory and classpaths documentation
steps are for. They seem irrelevant. I did the other steps to have the
other 5.0 jars in bundles dir correctly. So it appears the bitbucket wiki
is still accurate other then that.

I like the new admin colors/logo, and the attention to making the build
process easier (very nice that it doesn’t require a running copy of
lucee/railo anymore). I haven’t been able to utilize other new features
yet, but I plan on getting involved with the lucee language, because my
huge cfml app already works like your ideal version of CFML with the
various non-default scope rules and other compiler tweaks available in
Railo 4.2. I agree having a strict version of Adobe compatible CFML
separate from strict Lucee syntax language in order to force community to
adopt the 1 way to write modern cfml code and to not get confused about
what that syntax looks like. There are probably very few people who
actually use the syntax that isn’t ACF compatible.

Bruce,

Everything in terms of source is now on GitHub, please ignore the source on
BitBucket.

With regards to the Lucee 5 build process, this has been rewritten
completely using Maven and is still a “work in progress” so for now I would
not bother trying to get it to build. The latest build of Lucee 5 is
available here:

https://bitbucket.org/lucee/lucee/downloads/lucee-5.0.0.49.war
https://bitbucket.org/lucee/lucee/downloads/lucee-5.0.0.49-jars.zip

Also is your app using Coldbox? If so I think the empty response is a known
issue.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon - mso http://www.mso.net - Lucee
Association Member http://lucee.orgOn 8 August 2015 at 20:01, Bruce Kirkpatrick <@Bruce_Kirkpatrick> wrote:

I know this is a beta release, but I wanted to check it out to see if it
will be ready for my app soon.

I assume I am to use these urls now if I send ideas/changes:
Jira: https://luceeserver.atlassian.net/secure/Dashboard.jspa

Lucee 5.0 master branch - https://github.com/lucee/Lucee
Lucee 4.x master branch - https://bitbucket.org/lucee/lucee - it seems
the develop branch is no longer used for lucee 5 development.
and this google group,
but there is also now a more technical debate forum?
http://lang.lucee.org/

It seems that I can only build Lucee 5 from the develop branch on
bitbucket. The new github version doesn’t allow simply running ant,
because the build xml is missing or incomplete. I’m not sure how to get
access to a functional version of the latest work-in-progress code to
modify/test further, and I’m sure you’d rather get feedback on the newest
version of 5.0.

The lucee 5 ant build claims to finish successfully, but after patching
the server with the .loc file in the contexts directory, and restarting
tomcat, the railo admin appears to be missing or at a unknown new url. I’m
compiling with jdk 7 on windows.

This is the admin url I use now.
http://127.0.0.1:8888/lucee/admin/server.cfm

My large cfml app appears to work correctly on the stable release version
of Lucee 4.5, with the tomcat 8 installer off the official web site, but I
had to give the server several hundred mb more memory to start up my app
compared to Railo 4.2/tomcat 7.

My large cfml app doesn’t work on the beta release of Lucee 5 yet, and I
don’t know why because it shows a blank white screen instead of exceptions,
and nothing is logged in tomcat logs or railo web context logs.

I may have to walk through line by line writing echo(‘test’);abort in my
app to find what causes the empty response problem - and this would only be
to help you further develop or for me to fix my mistakes. It might be
related to the objectsave/objectload compatibility change, but I’m not sure
yet.

I also found that the documentation that says to put lucee.jar
and org-apache-felix-main-4-2-1.jar in tomcat/lib/ext/ is wrong. I had to
put those in tomcat/lib or it failed to start cfml with an error in tomcat
catalina.out that it couldn’t find the servlets for rest, cfml or lucee: .
I have no idea what the ext/ directory and classpaths documentation
steps are for. They seem irrelevant. I did the other steps to have the
other 5.0 jars in bundles dir correctly. So it appears the bitbucket wiki
is still accurate other then that.

I like the new admin colors/logo, and the attention to making the build
process easier (very nice that it doesn’t require a running copy of
lucee/railo anymore). I haven’t been able to utilize other new features
yet, but I plan on getting involved with the lucee language, because my
huge cfml app already works like your ideal version of CFML with the
various non-default scope rules and other compiler tweaks available in
Railo 4.2. I agree having a strict version of Adobe compatible CFML
separate from strict Lucee syntax language in order to force community to
adopt the 1 way to write modern cfml code and to not get confused about
what that syntax looks like. There are probably very few people who
actually use the syntax that isn’t ACF compatible.


See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/

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/fa258395-aa6e-4c06-960b-c5f2887b7bc7%40googlegroups.com
https://groups.google.com/d/msgid/lucee/fa258395-aa6e-4c06-960b-c5f2887b7bc7%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

Hi Bruce

Just a heads up. Lucee 4 master is now found
at https://github.com/lucee/Lucee4 :)On Saturday, 8 August 2015 20:01:19 UTC+1, Bruce Kirkpatrick wrote:

I know this is a beta release, but I wanted to check it out to see if it
will be ready for my app soon.

I assume I am to use these urls now if I send ideas/changes:
Jira: https://luceeserver.atlassian.net/secure/Dashboard.jspa

Lucee 5.0 master branch - https://github.com/lucee/Lucee
Lucee 4.x master branch - https://bitbucket.org/lucee/lucee - it seems
the develop branch is no longer used for lucee 5 development.
and this google group,
but there is also now a more technical debate forum?
http://lang.lucee.org/

It seems that I can only build Lucee 5 from the develop branch on
bitbucket. The new github version doesn’t allow simply running ant,
because the build xml is missing or incomplete. I’m not sure how to get
access to a functional version of the latest work-in-progress code to
modify/test further, and I’m sure you’d rather get feedback on the newest
version of 5.0.

The lucee 5 ant build claims to finish successfully, but after patching
the server with the .loc file in the contexts directory, and restarting
tomcat, the railo admin appears to be missing or at a unknown new url. I’m
compiling with jdk 7 on windows.

This is the admin url I use now.
http://127.0.0.1:8888/lucee/admin/server.cfm

My large cfml app appears to work correctly on the stable release version
of Lucee 4.5, with the tomcat 8 installer off the official web site, but I
had to give the server several hundred mb more memory to start up my app
compared to Railo 4.2/tomcat 7.

My large cfml app doesn’t work on the beta release of Lucee 5 yet, and I
don’t know why because it shows a blank white screen instead of exceptions,
and nothing is logged in tomcat logs or railo web context logs.

I may have to walk through line by line writing echo(‘test’);abort in my
app to find what causes the empty response problem - and this would only be
to help you further develop or for me to fix my mistakes. It might be
related to the objectsave/objectload compatibility change, but I’m not sure
yet.

I also found that the documentation that says to put lucee.jar
and org-apache-felix-main-4-2-1.jar in tomcat/lib/ext/ is wrong. I had to
put those in tomcat/lib or it failed to start cfml with an error in tomcat
catalina.out that it couldn’t find the servlets for rest, cfml or lucee: .
I have no idea what the ext/ directory and classpaths documentation
steps are for. They seem irrelevant. I did the other steps to have the
other 5.0 jars in bundles dir correctly. So it appears the bitbucket wiki
is still accurate other then that.

I like the new admin colors/logo, and the attention to making the build
process easier (very nice that it doesn’t require a running copy of
lucee/railo anymore). I haven’t been able to utilize other new features
yet, but I plan on getting involved with the lucee language, because my
huge cfml app already works like your ideal version of CFML with the
various non-default scope rules and other compiler tweaks available in
Railo 4.2. I agree having a strict version of Adobe compatible CFML
separate from strict Lucee syntax language in order to force community to
adopt the 1 way to write modern cfml code and to not get confused about
what that syntax looks like. There are probably very few people who
actually use the syntax that isn’t ACF compatible.

any updates on doco for how to build Lucee 5 from Source?On Sunday, August 9, 2015 at 3:29:42 AM UTC+8, Andrew Dixon wrote:

Bruce,

Everything in terms of source is now on GitHub, please ignore the source
on BitBucket.

With regards to the Lucee 5 build process, this has been rewritten
completely using Maven and is still a “work in progress” so for now I would
not bother trying to get it to build. The latest build of Lucee 5 is
available here:

https://bitbucket.org/lucee/lucee/downloads/lucee-5.0.0.49.war
https://bitbucket.org/lucee/lucee/downloads/lucee-5.0.0.49-jars.zip

Also is your app using Coldbox? If so I think the empty response is a
known issue.

Kind regards,

Andrew
about.me http://about.me/andrew_dixon - mso http://www.mso.net - Lucee
Association Member http://lucee.org

On 8 August 2015 at 20:01, Bruce Kirkpatrick <br...@farbeyondcode.com <javascript:>> wrote:

I know this is a beta release, but I wanted to check it out to see if it
will be ready for my app soon.

I assume I am to use these urls now if I send ideas/changes:
Jira: https://luceeserver.atlassian.net/secure/Dashboard.jspa

Lucee 5.0 master branch - https://github.com/lucee/Lucee
Lucee 4.x master branch - https://bitbucket.org/lucee/lucee - it seems
the develop branch is no longer used for lucee 5 development.
and this google group,
but there is also now a more technical debate forum?
http://lang.lucee.org/

It seems that I can only build Lucee 5 from the develop branch on
bitbucket. The new github version doesn’t allow simply running ant,
because the build xml is missing or incomplete. I’m not sure how to get
access to a functional version of the latest work-in-progress code to
modify/test further, and I’m sure you’d rather get feedback on the newest
version of 5.0.

The lucee 5 ant build claims to finish successfully, but after patching
the server with the .loc file in the contexts directory, and restarting
tomcat, the railo admin appears to be missing or at a unknown new url. I’m
compiling with jdk 7 on windows.

This is the admin url I use now.
http://127.0.0.1:8888/lucee/admin/server.cfm

My large cfml app appears to work correctly on the stable release version
of Lucee 4.5, with the tomcat 8 installer off the official web site, but I
had to give the server several hundred mb more memory to start up my app
compared to Railo 4.2/tomcat 7.

My large cfml app doesn’t work on the beta release of Lucee 5 yet, and I
don’t know why because it shows a blank white screen instead of exceptions,
and nothing is logged in tomcat logs or railo web context logs.

I may have to walk through line by line writing echo(‘test’);abort in my
app to find what causes the empty response problem - and this would only be
to help you further develop or for me to fix my mistakes. It might be
related to the objectsave/objectload compatibility change, but I’m not sure
yet.

I also found that the documentation that says to put lucee.jar
and org-apache-felix-main-4-2-1.jar in tomcat/lib/ext/ is wrong. I had to
put those in tomcat/lib or it failed to start cfml with an error in tomcat
catalina.out that it couldn’t find the servlets for rest, cfml or lucee: .
I have no idea what the ext/ directory and classpaths documentation
steps are for. They seem irrelevant. I did the other steps to have the
other 5.0 jars in bundles dir correctly. So it appears the bitbucket wiki
is still accurate other then that.

I like the new admin colors/logo, and the attention to making the build
process easier (very nice that it doesn’t require a running copy of
lucee/railo anymore). I haven’t been able to utilize other new features
yet, but I plan on getting involved with the lucee language, because my
huge cfml app already works like your ideal version of CFML with the
various non-default scope rules and other compiler tweaks available in
Railo 4.2. I agree having a strict version of Adobe compatible CFML
separate from strict Lucee syntax language in order to force community to
adopt the 1 way to write modern cfml code and to not get confused about
what that syntax looks like. There are probably very few people who
actually use the syntax that isn’t ACF compatible.


See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/

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 <javascript:>.
To post to this group, send email to lu...@googlegroups.com <javascript:>
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/fa258395-aa6e-4c06-960b-c5f2887b7bc7%40googlegroups.com
https://groups.google.com/d/msgid/lucee/fa258395-aa6e-4c06-960b-c5f2887b7bc7%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.