Filip Hanik - Dev Lists wrote:
oki doki, if we don't have any other feedback, I will make the following
adjustments
1. Use NSIS 2.0.0
Normally, the build structure is simpler with 6.0, and it seems there
won't be any such gotchas.
Rémy
oki doki, if we don't have any other feedback, I will make the following
adjustments
1. Use NSIS 2.0.0
2. Change the wording of LD_ASSUME_KERNEL in the release notes
and cut another build tomorrow
Filip
Remy Maucherat wrote:
William A. Rowe, Jr. wrote:
Jason Brittain wrote:
Then, later,
Dies Koper wrote:
Hello Filip,
In my application I used a pageContext.include which once threw a
JasperException (ServletException) while it was supposed to (according
to the spec) propagate the IOException as-is.
I noticed that setting the deployment init param in conf\web.xml to
false made
Filip Hanik - Dev Lists wrote:
I'm still running the tests, I had some funky results come up when I
turned off development, and I am re-running the tests to make sure it
wasn't me screwing it up
This is not really related, but where's the 5.5.18 build ?
Rémy
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
I'm still running the tests, I had some funky results come up when I
turned off development, and I am re-running the tests to make sure it
wasn't me screwing it up
This is not really related, but where's the 5.5.18 build ?
ok, development=false took care of the three errors, the TCK now runs
error free for the first run, any subsequent runs I get about 50 or so
errors.
If I delete the contents of the work directory, it again runs error
free, I'll do some investigations to see if its an actual issue
Filip
Remy
Filip Hanik - Dev Lists wrote:
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
I'm still running the tests, I had some funky results come up when I
turned off development, and I am re-running the tests to make sure it
wasn't me screwing it up
This is not really related, but where's the
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
I'm still running the tests, I had some funky results come up when
I turned off development, and I am re-running the tests to make
sure it wasn't me screwing it up
This is not really
Yoav Shapira wrote:
Hi,
Cool. The directory structure and signatures look good. We need to
update the release notes
(http://people.apache.org/~fhanik/v5.5.18-beta/RELEASE-NOTES) to
remove the LD_ASSUME_KERNEL section on Linux, as Bill (IIRC) pointed
out the day.
ok before I remove the
Hi Filip,
I can't give the correct recommendations, but explain the flag:
The flag tells the loader not to load the default thread library, but
instead another - usually older - one. Linux had incompatible changes in
it's thread implementation and since the distros bundle so much
software, they
Hi,
We need to clarify the message according to Bill's comments from a
thread on this list last week. The message is still correct for some
users, especially those using Tomcat 4.1, JDK 1.4, and certain Linux
kernels. We should make it clear the message does not apply to all
situations, should
Yoav Shapira wrote:
Hi,
We need to clarify the message according to Bill's comments from a
thread on this list last week. The message is still correct for some
users, especially those using Tomcat 4.1, JDK 1.4, and certain Linux
kernels.
It was for RH9 JDK1.4.0 and 1.3.1... Old stuff.
Look
Jean-frederic Clere wrote:
Yoav Shapira wrote:
Hi,
We need to clarify the message according to Bill's comments from a
thread on this list last week. The message is still correct for some
users, especially those using Tomcat 4.1, JDK 1.4, and certain Linux
kernels.
It was for RH9 JDK1.4.0
Hi guys.
On 8/29/06, Yoav Shapira [EMAIL PROTECTED] wrote:
Hi,
We need to clarify the message according to Bill's comments from a
thread on this list last week.
Clarifying it would be preferable.
The message is still correct for some
users, especially those using Tomcat 4.1, JDK 1.4, and
Jason Brittain wrote:
Then, later, I needed Java 1.5.x features, so I upgraded it to
Sun Java 1.5.0. At the time that I upgraded just the JDK, I
knew very well that I have LD_ASSUME_KERNEL set, but I
since I didn't upgrade the OS (same kernel libs) I left that
setting alone to see if it
William A. Rowe, Jr. wrote:
Jason Brittain wrote:
Then, later, I needed Java 1.5.x features, so I upgraded it to
Sun Java 1.5.0. At the time that I upgraded just the JDK, I
knew very well that I have LD_ASSUME_KERNEL set, but I
since I didn't upgrade the OS (same kernel libs) I left that
I have created a 5.5.18 distribution located at
http://people.apache.org/~fhanik/v5.5.18-beta/
I'm about to setup the TCK tests, servlet and JSP, to validate against
it. In the meantime feel free to play around with it.
Once we deem that it looks correct, we can setup a vote for it.
Filip
Hi,
Cool. The directory structure and signatures look good. We need to
update the release notes
(http://people.apache.org/~fhanik/v5.5.18-beta/RELEASE-NOTES) to
remove the LD_ASSUME_KERNEL section on Linux, as Bill (IIRC) pointed
out the day.
Yoav
On 8/28/06, Filip Hanik - Dev Lists [EMAIL
great, I will let the feedback gather up a little bit, (waiting for the
TCK tests to complete)
then make the adjustments
Filip
Yoav Shapira wrote:
Hi,
Cool. The directory structure and signatures look good. We need to
update the release notes
Looks like the TCK is expecting a IOException, and not a runtime jasper
exception when you have invalid TLD files is one of the errors.
---
Test FAILED. Exception thrown by forwardedresource, but was not an
instance of IOException
Type thrown:
Filip Hanik - Dev Lists wrote:
in hindsight I think its ok to let these slip
Probably. The first thing to check is if it's required somewhere in the
specification for that (and if it's required, well ... lol). The main
problem is that IOE is a checked exception, so there's a throws clause
Hello Filip,
In my application I used a pageContext.include which once threw a
JasperException (ServletException) while it was supposed to (according
to the spec) propagate the IOException as-is.
I noticed that setting the deployment init param in conf\web.xml to
false made it propagate the
22 matches
Mail list logo
