remm2003/03/15 01:04:52
Modified:.build.xml
Log:
- Copy the declarations for manager and admin (now I know Costin doesn't
test anything ;-) ).
- Update release to include the embed distro.
Revision ChangesPath
1.113 +41 -1
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-03-15/jakarta-tomcat-5.html
Buildfile: build.xml
prepare-release:
[mkdir] Created dir:
mturk 2003/03/15 03:16:55
Modified:jk/native2/common jk_uriEnv.c
Log:
Fix missing function type.
Revision ChangesPath
1.45 +2 -2 jakarta-tomcat-connectors/jk/native2/common/jk_uriEnv.c
Index: jk_uriEnv.c
remm2003/03/15 03:37:05
Modified:coyote/src/java/org/apache/coyote/tomcat4 CoyoteAdapter.java
coyote/src/java/org/apache/coyote/tomcat5 CoyoteAdapter.java
Log:
- Return 400 for decoded URLs which don't start with '/'.
Revision ChangesPath
1.16 +9
remm2003/03/15 03:37:39
Modified:coyote/src/java/org/apache/coyote/tomcat4 Tag: coyote_10
CoyoteAdapter.java
coyote/src/java/org/apache/coyote/tomcat5 Tag: coyote_10
CoyoteAdapter.java
Log:
- Return 400 for decoded
mturk 2003/03/15 04:34:39
Modified:jk/native2/common jk_uriEnv.c
Log:
Make the regular expression uri maps finally working.
Revision ChangesPath
1.46 +17 -0 jakarta-tomcat-connectors/jk/native2/common/jk_uriEnv.c
Index: jk_uriEnv.c
[EMAIL PROTECTED] wrote:
costin 2003/03/14 14:42:43
Modified:.build.xml
Log:
Fix Filip's build.
It seems my clean workspace wasn't that clean after all.
This whole thing is unbelievable. I have no idea how we end up with this
mess.
The build is really complex,
Remy Maucherat wrote:
[EMAIL PROTECTED] wrote:
costin 2003/03/14 14:42:43
Modified:.build.xml
Log:
Fix Filip's build.
It seems my clean workspace wasn't that clean after all.
This whole thing is unbelievable. I have no idea how we end up with
this
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12069.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
All,
Using linux 2.4.16-10, with Apache/1.3.27 installed. Trying to get Tomcat
installed so my programmers can write jsp web pages.
I've installed j2sdk1.4.1_02 and jakarta-tomcat-4.1.18-LE-jdk14 (all
binaries, not source). I've even installed the tomcat 4.1.18 without the
LE-jdk14 (not sure
Costin Manolache wrote:
Remy Maucherat wrote:
The build is really complex, so it's normal to run into trouble when you
refactor it. Plus there are so many dependent components, doing ant
build is not enough to do a clean build ;-)
The purpose of the refactoring was to make it simpler ( or at
Hi,
I plan to tag 4.1.23 soon. The big question remaining is if we remove,
or not, the commons-fileupload related functionality.
Personally, I'm willing to ignore the issue.
Remy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
I'm not a commiter or any such, but:
I'd much sooner see a stable release as soon as possible that rolls in
all the improvements since 4.1.18, than wait to remove some extra baggage.
Remy Maucherat wrote:
Hi,
I plan to tag 4.1.23 soon. The big question remaining is if we remove,
or not, the
Remy Maucherat wrote:
Each component should support a dist.dir ( unlike servlet/jsp api build
files), should support a build target that only builds the .jar - and
should use the same patterns for finding the dependencies ( the other
components ).
No problem with me if you want to do that.
Not as major as the build breakage, I hope - but I think it is better to
do it as soon as possible.
Unless someone has good reasons not to do it, I'll start refactoring the
JMX registration. There are few things I would like to do:
- get rid of service=XXX in names. The JMX domain will
Costin Manolache wrote:
Not as major as the build breakage, I hope - but I think it is better to
do it as soon as possible.
Unless someone has good reasons not to do it, I'll start refactoring the
JMX registration. There are few things I would like to do:
- get rid of service=XXX in names. The JMX
I forgot one important thing:
The main problem with supporting both registrations is the deregistration -
who should unregister a component ?
If the components are started by JMX - then JMX is supposed to unregister
them.
If they are created automatically - then whoever created them is
Remy Maucherat wrote:
Hi,
I plan to tag 4.1.23 soon. The big question remaining is if we remove,
or not, the commons-fileupload related functionality.
Personally, I'm willing to ignore the issue.
I am ok with releasing 4.1.23 with commons-fileupload Beta 1 release.
If the decision is made
Remy Maucherat wrote:
- get rid of service=XXX in names. The JMX domain will correspond to
one tomcat instance - there is no reason to make things more complex. The
admin can just list all mbeans, search for *:type=Engine and get the
domain.
Ok, so that goes along with having only a one
Glenn Nielsen wrote:
Personally, I'm willing to ignore the issue.
Then I'll ignore the issue as well.
If the decision is made that we can not do a Tomcat release without
all dependent jar files being at a final stable release then I would
rather push to get commons to do a final stable
Glenn Nielsen wrote:
Remy Maucherat wrote:
If the decision is made that we can not do a Tomcat release without
all dependent jar files being at a final stable release then I would
rather push to get commons to do a final stable release of fileupload
than remove those features from the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18030.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
nacho 2003/03/15 16:56:34
Modified:jk/xdocs menu.jk2.idx
jk/xdocs/jk2 configtc.xml
Added: jk/xdocs/jk2 configtccom.xml
Log:
* Added all the remaning components and properties for jk2.properties cofngi file,
most of them not commentted..
* Converted the
It looks like the consensus is to release with the manager web app and
fileupload the way it currently is.
I will commit my manager changes after the release.
Glenn
Remy Maucherat wrote:
Glenn Nielsen wrote:
Remy Maucherat wrote:
If the decision is made that we can not do a Tomcat release
billbarker2003/03/15 17:43:47
Modified:coyote/src/java/org/apache/coyote/tomcat4 Tag: coyote_10
CoyoteAdapter.java
Log:
Was just reminded that I forgot to port the bad-cookie patch to this branch.
Revision ChangesPath
No revision
billbarker2003/03/15 17:56:27
Modified:coyote/src/java/org/apache/coyote/tomcat4 Tag: coyote_10
CoyoteAdapter.java
Log:
Small improvement on the bad-cookie case. Leave out the null cookies when bad ones
are detected.
Revision ChangesPath
No
billbarker2003/03/15 17:57:57
Modified:coyote/src/java/org/apache/coyote/tomcat4 CoyoteAdapter.java
Log:
Port patch.
Revision ChangesPath
1.17 +16 -11
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4/CoyoteAdapter.java
Index:
billbarker2003/03/15 17:58:59
Modified:coyote/src/java/org/apache/coyote/tomcat5 CoyoteAdapter.java
Log:
port patch.
Revision ChangesPath
1.16 +9 -4
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteAdapter.java
Index:
glenn 2003/03/15 18:59:44
Modified:jk/native CHANGES.txt
jk/native/apache-1.3 mod_jk.c
jk/native/apache-2.0 mod_jk.c
Log:
When a client aborted but Apache 2 tried to do a SSI include
of a JSP or servlet an error was being logged. Updated code
to
Glenn Nielsen wrote:
It looks like the consensus is to release with the manager web app and
fileupload the way it currently is.
I think you didn't leave much choice, and thus forced that consensus,
which is not something to be proud of.
Anyway, let's forget about that and move forward.
I will
remm2003/03/15 22:15:38
Modified:.RELEASE-NOTES-4.1.txt
Log:
- Status update.
Revision ChangesPath
1.66 +7 -1 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt
Index: RELEASE-NOTES-4.1.txt
costin 2003/03/15 23:05:44
Modified:coyote build.xml
Log:
Added a flag to disable javadoc.
I also inserted index=true - it seems that may speed up some things
in jdk1.4+ ( and it doesn't hurt otherwise )
Revision ChangesPath
1.23 +9 -6
32 matches
Mail list logo
