Re: svn commit: r1816617 - in /tomcat/trunk: java/org/apache/catalina/ java/org/apache/catalina/core/ java/org/apache/catalina/mapper/ java/org/apache/catalina/startup/ java/org/apache/tomcat/util/des
On Wed, Dec 6, 2017 at 8:35 PM, Mark Thomas wrote: > On 06/12/17 16:25, Rémy Maucherat wrote: > > On Wed, Nov 29, 2017 at 1:12 PM, Mark Thomas wrote: > > > >> On 29/11/17 09:46, r...@apache.org wrote: > >>> Author: remm > >>> Date: Wed Nov 29 09:46:00 2017 > >>> New Revision: 1816617 > >>> > >>> URL: http://svn.apache.org/viewvc?rev=1816617&view=rev > >>> Log: > >>> Add a bare bones default-context-path impl (best effort really, it's a > >> bad feature). Also fix for some mapping paths, excluded pending some > >> clarifications. > >> > >> I agree that default-context-path is a bad feature. > >> > > > > I still don't see any good way to do this. The Tomcat deployer is > > exclusively based on the file name (which isn't bad since you can change > it > > - in the context of Tomcat, as you say inside an EAR it's different). > From > > that the conditions to keep everything in place make the feature unusable > > as far as I am concerned. > > Just thinking aloud... > > Could we get the deployer to attempt a rename (if there are no naming > conflicts) based on the default-context-path as the very first action > and then follow the normal automatic deployment rules? > To be honest, I thought about it, but it seemed quite horrible and didn't seem like an acceptable solution to me. Maybe it is then ? Rémy > > Mark > > P.S. I'm quite happy to ignore this feature and declare Tomcat spec > compliant on the grounds the container specific configuration is always > present. > >
Re: svn commit: r1816617 - in /tomcat/trunk: java/org/apache/catalina/ java/org/apache/catalina/core/ java/org/apache/catalina/mapper/ java/org/apache/catalina/startup/ java/org/apache/tomcat/util/des
On 07/12/17 09:03, Rémy Maucherat wrote: > On Wed, Dec 6, 2017 at 8:35 PM, Mark Thomas wrote: > >> On 06/12/17 16:25, Rémy Maucherat wrote: >>> On Wed, Nov 29, 2017 at 1:12 PM, Mark Thomas wrote: >>> On 29/11/17 09:46, r...@apache.org wrote: > Author: remm > Date: Wed Nov 29 09:46:00 2017 > New Revision: 1816617 > > URL: http://svn.apache.org/viewvc?rev=1816617&view=rev > Log: > Add a bare bones default-context-path impl (best effort really, it's a bad feature). Also fix for some mapping paths, excluded pending some clarifications. I agree that default-context-path is a bad feature. >>> >>> I still don't see any good way to do this. The Tomcat deployer is >>> exclusively based on the file name (which isn't bad since you can change >> it >>> - in the context of Tomcat, as you say inside an EAR it's different). >> From >>> that the conditions to keep everything in place make the feature unusable >>> as far as I am concerned. >> >> Just thinking aloud... >> >> Could we get the deployer to attempt a rename (if there are no naming >> conflicts) based on the default-context-path as the very first action >> and then follow the normal automatic deployment rules? >> > > To be honest, I thought about it, but it seemed quite horrible and didn't > seem like an acceptable solution to me. Maybe it is then ? I hadn't thought much about the implementation detail. The more I think about it the worse it looks. My preference at this point remains not to implement this feature. If there is demand for it, and an elegant implementation can be found, then I could live with it. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 35959] mod_jk not independant of UseCanonicalName
https://bz.apache.org/bugzilla/show_bug.cgi?id=35959 Mark Thomas changed: What|Removed |Added Resolution|--- |WONTFIX Status|REOPENED|RESOLVED --- Comment #11 from Mark Thomas --- I understand the use case. Using the canonical name on the Tomcat side is going to trigger the same set of issues (e.g. broken cookies) as it triggers on the httpd side. The subset of users for which this is not a concern is going to be very small. It should be possible to configure Tomcat's virtual hosts to align with httpd's. Since this issue was raised Tomcat added limited support for wildcards (see bug 18500). Depending on the exact requirements, it is likely that other httpd configuration options (mod_headers, mod_rewrite, etc.) can be used to achieve the desired results. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1816617 - in /tomcat/trunk: java/org/apache/catalina/ java/org/apache/catalina/core/ java/org/apache/catalina/mapper/ java/org/apache/catalina/startup/ java/org/apache/tomcat/util/des
On Thu, Dec 7, 2017 at 10:51 AM, Mark Thomas wrote: > On 07/12/17 09:03, Rémy Maucherat wrote: > > On Wed, Dec 6, 2017 at 8:35 PM, Mark Thomas wrote: > > > >> On 06/12/17 16:25, Rémy Maucherat wrote: > >>> On Wed, Nov 29, 2017 at 1:12 PM, Mark Thomas wrote: > >>> > On 29/11/17 09:46, r...@apache.org wrote: > > Author: remm > > Date: Wed Nov 29 09:46:00 2017 > > New Revision: 1816617 > > > > URL: http://svn.apache.org/viewvc?rev=1816617&view=rev > > Log: > > Add a bare bones default-context-path impl (best effort really, it's > a > bad feature). Also fix for some mapping paths, excluded pending some > clarifications. > > I agree that default-context-path is a bad feature. > > >>> > >>> I still don't see any good way to do this. The Tomcat deployer is > >>> exclusively based on the file name (which isn't bad since you can > change > >> it > >>> - in the context of Tomcat, as you say inside an EAR it's different). > >> From > >>> that the conditions to keep everything in place make the feature > unusable > >>> as far as I am concerned. > >> > >> Just thinking aloud... > >> > >> Could we get the deployer to attempt a rename (if there are no naming > >> conflicts) based on the default-context-path as the very first action > >> and then follow the normal automatic deployment rules? > >> > > > > To be honest, I thought about it, but it seemed quite horrible and didn't > > seem like an acceptable solution to me. Maybe it is then ? > > I hadn't thought much about the implementation detail. The more I think > about it the worse it looks. > > My preference at this point remains not to implement this feature. If > there is demand for it, and an elegant implementation can be found, then > I could live with it. > > We could have another folder, like webapps, where we could say we deploy "enterprise" archives (like if we support some amount of EAR one day, after all it can be used to package multiple wars together), as a way to disguise the predeploy/copy step. Ok, it's horrible too :) Another option is to generate a context file (I'm pretty sure it will have some challenges) while making the original webapp unavailable or something, so the war gets treated as an external one. Rémy
svn commit: r1817351 - /tomcat/jk/trunk/native/apache-2.0/mod_jk.mak
Author: markt
Date: Thu Dec 7 11:13:52 2017
New Revision: 1817351
URL: http://svn.apache.org/viewvc?rev=1817351&view=rev
Log:
Add the Visual Studio 6 (no, that isn't a typo) exported make file so mod_jk
can be built from the command line for Windows without Visual Studio 6.
Added:
tomcat/jk/trunk/native/apache-2.0/mod_jk.mak
Added: tomcat/jk/trunk/native/apache-2.0/mod_jk.mak
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/native/apache-2.0/mod_jk.mak?rev=1817351&view=auto
==
--- tomcat/jk/trunk/native/apache-2.0/mod_jk.mak (added)
+++ tomcat/jk/trunk/native/apache-2.0/mod_jk.mak Thu Dec 7 11:13:52 2017
@@ -0,0 +1,666 @@
+# Microsoft Developer Studio Generated NMAKE File, Based on mod_jk.dsp
+!IF "$(CFG)" == ""
+CFG=mod_jk - Win32 Release httpd 2.
+!MESSAGE No configuration specified. Defaulting to mod_jk - Win32 Release
httpd 2.0.
+!ENDIF
+
+!IF "$(CFG)" != "mod_jk - Win32 Release httpd 2.0" && "$(CFG)" != "mod_jk -
Win32 Debug httpd 2.0" && "$(CFG)" != "mod_jk - Win32 Release httpd 2.2" &&
"$(CFG)" != "mod_jk - Win32 Debug httpd 2.2"
+!MESSAGE Invalid configuration "$(CFG)" specified.
+!MESSAGE You can specify a configuration when running NMAKE
+!MESSAGE by defining the macro CFG on the command line. For example:
+!MESSAGE
+!MESSAGE NMAKE /f "mod_jk.mak" CFG="mod_jk - Win32 Release httpd 2.0"
+!MESSAGE
+!MESSAGE Possible choices for configuration are:
+!MESSAGE
+!MESSAGE "mod_jk - Win32 Release httpd 2.0" (based on "Win32 (x86)
Dynamic-Link Library")
+!MESSAGE "mod_jk - Win32 Debug httpd 2.0" (based on "Win32 (x86) Dynamic-Link
Library")
+!MESSAGE "mod_jk - Win32 Release httpd 2.2" (based on "Win32 (x86)
Dynamic-Link Library")
+!MESSAGE "mod_jk - Win32 Debug httpd 2.2" (based on "Win32 (x86) Dynamic-Link
Library")
+!MESSAGE
+!ERROR An invalid configuration is specified.
+!ENDIF
+
+!IF "$(OS)" == "Windows_NT"
+NULL=
+!ELSE
+NULL=nul
+!ENDIF
+
+!IF "$(CFG)" == "mod_jk - Win32 Release httpd 2.0"
+
+OUTDIR=.\Release
+INTDIR=.\Release
+# Begin Custom Macros
+OutDir=.\Release
+# End Custom Macros
+
+ALL : "$(OUTDIR)\mod_jk.so"
+
+
+CLEAN :
+ -@erase "$(INTDIR)\jk_ajp12_worker.obj"
+ -@erase "$(INTDIR)\jk_ajp13.obj"
+ -@erase "$(INTDIR)\jk_ajp13_worker.obj"
+ -@erase "$(INTDIR)\jk_ajp14.obj"
+ -@erase "$(INTDIR)\jk_ajp14_worker.obj"
+ -@erase "$(INTDIR)\jk_ajp_common.obj"
+ -@erase "$(INTDIR)\jk_connect.obj"
+ -@erase "$(INTDIR)\jk_context.obj"
+ -@erase "$(INTDIR)\jk_lb_worker.obj"
+ -@erase "$(INTDIR)\jk_map.obj"
+ -@erase "$(INTDIR)\jk_md5.obj"
+ -@erase "$(INTDIR)\jk_msg_buff.obj"
+ -@erase "$(INTDIR)\jk_pool.obj"
+ -@erase "$(INTDIR)\jk_shm.obj"
+ -@erase "$(INTDIR)\jk_sockbuf.obj"
+ -@erase "$(INTDIR)\jk_status.obj"
+ -@erase "$(INTDIR)\jk_uri_worker_map.obj"
+ -@erase "$(INTDIR)\jk_url.obj"
+ -@erase "$(INTDIR)\jk_util.obj"
+ -@erase "$(INTDIR)\jk_worker.obj"
+ -@erase "$(INTDIR)\mod_jk.obj"
+ -@erase "$(INTDIR)\mod_jk.res"
+ -@erase "$(INTDIR)\mod_jk_src.idb"
+ -@erase "$(INTDIR)\mod_jk_src.pdb"
+ -@erase "$(OUTDIR)\mod_jk.exp"
+ -@erase "$(OUTDIR)\mod_jk.lib"
+ -@erase "$(OUTDIR)\mod_jk.pdb"
+ -@erase "$(OUTDIR)\mod_jk.so"
+
+"$(OUTDIR)" :
+if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"
+
+CPP=cl.exe
+CPP_PROJ=/nologo /MD /W3 /Zi /O2 /Oy- /I "..\common" /I
"$(APACHE2_HOME)\include" /I "$(APACHE2_HOME)\srclib\apr\include" /I
"$(APACHE2_HOME)\srclib\apr-util\include" /D "NDEBUG" /D "WIN32" /D "_WINDOWS"
/D "HAVE_APR" /Fo"$(INTDIR)\\" /Fd"$(INTDIR)\mod_jk_src" /FD /c
+
+.c{$(INTDIR)}.obj::
+ $(CPP) @<<
+ $(CPP_PROJ) $<
+<<
+
+.cpp{$(INTDIR)}.obj::
+ $(CPP) @<<
+ $(CPP_PROJ) $<
+<<
+
+.cxx{$(INTDIR)}.obj::
+ $(CPP) @<<
+ $(CPP_PROJ) $<
+<<
+
+.c{$(INTDIR)}.sbr::
+ $(CPP) @<<
+ $(CPP_PROJ) $<
+<<
+
+.cpp{$(INTDIR)}.sbr::
+ $(CPP) @<<
+ $(CPP_PROJ) $<
+<<
+
+.cxx{$(INTDIR)}.sbr::
+ $(CPP) @<<
+ $(CPP_PROJ) $<
+<<
+
+MTL=midl.exe
+MTL_PROJ=/nologo /D "NDEBUG" /mktyplib203 /win32
+RSC=rc.exe
+RSC_PROJ=/l 0x409 /fo"$(INTDIR)\mod_jk.res" /i "..\common" /d "NDEBUG"
+BSC32=bscmake.exe
+BSC32_FLAGS=/nologo /o"$(OUTDIR)\mod_jk.bsc"
+BSC32_SBRS= \
+
+LINK32=link.exe
+LINK32_FLAGS=libhttpd.lib libapr.lib libaprutil.lib kernel32.lib user32.lib
advapi32.lib ws2_32.lib mswsock.lib /nologo /base:"0x6A6B"
/subsystem:windows /dll /incremental:no /pdb:"$(OUTDIR)\mod_jk.pdb" /debug
/machine:I386 /out:"$(OUTDIR)\mod_jk.so" /implib:"$(OUTDIR)\mod_jk.lib"
/libpath:"$(APACHE2_HOME)\Release"
/libpath:"$(APACHE2_HOME)\srclib\apr\Release"
/libpath:"$(APACHE2_HOME)\srclib\apr-util\Release"
/libpath:"$(APACHE2_HOME)\lib" /opt:ref
+LINK32_OBJS= \
+ "$(INTDIR)\jk_ajp12_worker.obj" \
+ "$(INTDIR)\jk_ajp13.obj" \
+ "$(INTDIR)\jk_ajp13_worker.obj" \
+ "$(INTDIR)\jk_ajp14.obj" \
+
[Bug 43303] Versioning under Windows not reported by many connector components
https://bz.apache.org/bugzilla/show_bug.cgi?id=43303 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #8 from Mark Thomas --- Most of the libraries referenced in the original report have been removed from the svn repo. I've checked the remaining libraries and they all include version info once built. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1817365 - in /tomcat/jk/trunk: native/apache-2.0/mod_jk.mak xdocs/miscellaneous/changelog.xml
Author: markt Date: Thu Dec 7 12:43:52 2017 New Revision: 1817365 URL: http://svn.apache.org/viewvc?rev=1817365&view=rev Log: Drop httpd 2.0 support, add httpd 2.4 (untested) Make httpd 2.4 the default Modified: tomcat/jk/trunk/native/apache-2.0/mod_jk.mak tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml Modified: tomcat/jk/trunk/native/apache-2.0/mod_jk.mak URL: http://svn.apache.org/viewvc/tomcat/jk/trunk/native/apache-2.0/mod_jk.mak?rev=1817365&r1=1817364&r2=1817365&view=diff == --- tomcat/jk/trunk/native/apache-2.0/mod_jk.mak (original) +++ tomcat/jk/trunk/native/apache-2.0/mod_jk.mak Thu Dec 7 12:43:52 2017 @@ -1,22 +1,22 @@ # Microsoft Developer Studio Generated NMAKE File, Based on mod_jk.dsp !IF "$(CFG)" == "" -CFG=mod_jk - Win32 Release httpd 2. -!MESSAGE No configuration specified. Defaulting to mod_jk - Win32 Release httpd 2.0. +CFG=mod_jk - Win32 Release httpd 2.4 +!MESSAGE No configuration specified. Defaulting to mod_jk - Win32 Release httpd 2.4 !ENDIF -!IF "$(CFG)" != "mod_jk - Win32 Release httpd 2.0" && "$(CFG)" != "mod_jk - Win32 Debug httpd 2.0" && "$(CFG)" != "mod_jk - Win32 Release httpd 2.2" && "$(CFG)" != "mod_jk - Win32 Debug httpd 2.2" +!IF "$(CFG)" != "mod_jk - Win32 Release httpd 2.2" && "$(CFG)" != "mod_jk - Win32 Debug httpd 2.2" && "$(CFG)" != "mod_jk - Win32 Release httpd 2.4" && "$(CFG)" != "mod_jk - Win32 Debug httpd 2.4" !MESSAGE Invalid configuration "$(CFG)" specified. !MESSAGE You can specify a configuration when running NMAKE !MESSAGE by defining the macro CFG on the command line. For example: !MESSAGE -!MESSAGE NMAKE /f "mod_jk.mak" CFG="mod_jk - Win32 Release httpd 2.0" +!MESSAGE NMAKE /f "mod_jk.mak" CFG="mod_jk - Win32 Release httpd 2.4" !MESSAGE !MESSAGE Possible choices for configuration are: !MESSAGE -!MESSAGE "mod_jk - Win32 Release httpd 2.0" (based on "Win32 (x86) Dynamic-Link Library") -!MESSAGE "mod_jk - Win32 Debug httpd 2.0" (based on "Win32 (x86) Dynamic-Link Library") !MESSAGE "mod_jk - Win32 Release httpd 2.2" (based on "Win32 (x86) Dynamic-Link Library") !MESSAGE "mod_jk - Win32 Debug httpd 2.2" (based on "Win32 (x86) Dynamic-Link Library") +!MESSAGE "mod_jk - Win32 Release httpd 2.4" (based on "Win32 (x86) Dynamic-Link Library") +!MESSAGE "mod_jk - Win32 Debug httpd 2.4" (based on "Win32 (x86) Dynamic-Link Library") !MESSAGE !ERROR An invalid configuration is specified. !ENDIF @@ -27,12 +27,12 @@ NULL= NULL=nul !ENDIF -!IF "$(CFG)" == "mod_jk - Win32 Release httpd 2.0" +!IF "$(CFG)" == "mod_jk - Win32 Release httpd 2.2" -OUTDIR=.\Release -INTDIR=.\Release +OUTDIR=.\Release22 +INTDIR=.\Release22 # Begin Custom Macros -OutDir=.\Release +OutDir=.\Release22 # End Custom Macros ALL : "$(OUTDIR)\mod_jk.so" @@ -143,12 +143,12 @@ LINK32_OBJS= \ $(LINK32_FLAGS) $(LINK32_OBJS) << -!ELSEIF "$(CFG)" == "mod_jk - Win32 Debug httpd 2.0" +!ELSEIF "$(CFG)" == "mod_jk - Win32 Debug httpd 2.2" -OUTDIR=.\Debug -INTDIR=.\Debug +OUTDIR=.\Debug22 +INTDIR=.\Debug22 # Begin Custom Macros -OutDir=.\Debug +OutDir=.\Debug22 # End Custom Macros ALL : "$(OUTDIR)\mod_jk.so" @@ -259,12 +259,12 @@ LINK32_OBJS= \ $(LINK32_FLAGS) $(LINK32_OBJS) << -!ELSEIF "$(CFG)" == "mod_jk - Win32 Release httpd 2.2" +!ELSEIF "$(CFG)" == "mod_jk - Win32 Release httpd 2.4" -OUTDIR=.\Release22 -INTDIR=.\Release22 +OUTDIR=.\Release24 +INTDIR=.\Release24 # Begin Custom Macros -OutDir=.\Release22 +OutDir=.\Release24 # End Custom Macros ALL : "$(OUTDIR)\mod_jk.so" @@ -375,12 +375,12 @@ LINK32_OBJS= \ $(LINK32_FLAGS) $(LINK32_OBJS) << -!ELSEIF "$(CFG)" == "mod_jk - Win32 Debug httpd 2.2" +!ELSEIF "$(CFG)" == "mod_jk - Win32 Debug httpd 2.4" -OUTDIR=.\Debug22 -INTDIR=.\Debug22 +OUTDIR=.\Debug24 +INTDIR=.\Debug24 # Begin Custom Macros -OutDir=.\Debug22 +OutDir=.\Debug24 # End Custom Macros ALL : "$(OUTDIR)\mod_jk.so" @@ -503,7 +503,7 @@ LINK32_OBJS= \ !ENDIF -!IF "$(CFG)" == "mod_jk - Win32 Release httpd 2.0" || "$(CFG)" == "mod_jk - Win32 Debug httpd 2.0" || "$(CFG)" == "mod_jk - Win32 Release httpd 2.2" || "$(CFG)" == "mod_jk - Win32 Debug httpd 2.2" +!IF "$(CFG)" == "mod_jk - Win32 Release httpd 2.2" || "$(CFG)" == "mod_jk - Win32 Debug httpd 2.2" || "$(CFG)" == "mod_jk - Win32 Release httpd 2.4" || "$(CFG)" == "mod_jk - Win32 Debug httpd 2.4" SOURCE=..\common\jk_ajp12_worker.c "$(INTDIR)\jk_ajp12_worker.obj" : $(SOURCE) "$(INTDIR)" @@ -631,28 +631,28 @@ SOURCE=.\mod_jk.c SOURCE=..\common\jk.rc -!IF "$(CFG)" == "mod_jk - Win32 Release httpd 2.0" +!IF "$(CFG)" == "mod_jk - Win32 Release httpd 2.2" "$(INTDIR)\mod_jk.res" : $(SOURCE) "$(INTDIR)" $(RSC) /l 0x409 /fo"$(INTDIR)\mod_jk.res" /i "..\common" /i "\mod_jk\jk-1.2.x\native\common" /d "NDEBUG" $(SOURCE) -!ELSEIF "$(CFG)" == "mod_jk - Win32 Debug httpd 2.0" +!ELSEIF "$(CFG)" == "mod_jk - Win32 Debug httpd 2.2" "$(INTDIR)\mod_j
svn commit: r1817367 - in /tomcat/jk/trunk: native/apache-2.0/mod_jk.mak xdocs/miscellaneous/changelog.xml
Author: markt Date: Thu Dec 7 12:46:51 2017 New Revision: 1817367 URL: http://svn.apache.org/viewvc?rev=1817367&view=rev Log: Open eyes. Find makefile.vc Removed: tomcat/jk/trunk/native/apache-2.0/mod_jk.mak Modified: tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml Modified: tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml URL: http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml?rev=1817367&r1=1817366&r2=1817367&view=diff == --- tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml (original) +++ tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml Thu Dec 7 12:46:51 2017 @@ -59,14 +59,6 @@ Update the ISAPI redirector installation documentation to reflect the currently supported versions of Windows. (markt) - -Add a make file to enable building mod_jk for Windows from the command -line. (markt) - - -Remove httpd 2.0 support and add httpd 2.4 support to the mod_jk Windows -build. (markt) - - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1817368 - /tomcat/jk/trunk/native/apache-2.0/mod_jk.dsp
Author: markt Date: Thu Dec 7 12:47:08 2017 New Revision: 1817368 URL: http://svn.apache.org/viewvc?rev=1817368&view=rev Log: Drop out of date VS 6 project file. Removed: tomcat/jk/trunk/native/apache-2.0/mod_jk.dsp - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 45313] mod_jk 1.2.26 & apache 2.2.9 static compiled on solaris not able to connect
https://bz.apache.org/bugzilla/show_bug.cgi?id=45313 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Mark Thomas --- Looks to be a compiler issue on Solaris. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Incorrect version number listed for Tomcat 6.0.x
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I'm not sure if anyone actually cares, but the archive page for Tomcat 6 says that the latest stable version is 6.0.45 when it appears to be 6.0.53. https://archive.apache.org/dist/tomcat/tomcat-6/ I have no idea how to change that. Thanks, - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlopXUQdHGNocmlzQGNo cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFjsyhAAhgN1QL8K/QOtYZZk J+P4Is/pSN4VheZKS8cufAGZhuLx8BXi3FPP41Ht3ZrbyFUgj5fWg3KxrK+z5mbR WKBVIiXNd8syG//X+Wm1Y1KOaJdovHZ6pcRvvEh5JzSBFCtzPkH/cdqHHbUwtc71 gQRyF4jf8UtAfuGPCfO3x1cb+uM6Xbr+isA/dQICxC4PbTBrYEfkL3rk0fHubfOA Txu5E8Ghb8Mpk9bY1H+7nCXnkmRhldQ8/Q93bU91qvk+L59iVeKHJya8K6UiX7le BTLTA2s0AUHadWJfF9U5rdCz6Fniply3phY4cAL8G+x3Tk6ScJnluTw031TJi4yw ICKGS61YAfwWPFff/OsXaILm37u4UItbsPj4FC3iIJ8TWsdOsP9PvjgvXcbouc1A 71z0ZdyZQPusJzQ5NS8Xk7xLeDUTYqMlA4+2mmGmVy/WVGOmcTsjVDSiN/ghvIjs gNF6G2Md+V1yGg3bEStpBbOzG/vmuNo2YoaZ6xQdfUUioVgjtV9xVyauxX+lRjmi A3ZcgXuYz/WLYIO25OD6SalPnjq16c7SVlCdGEbwk//4hAgeX29WeC2GdmwDGPcy HKrfP6G/fixdI4udiKYwiHg/2wrAD61au7fCWyA9PGfFsWYMWm8GcgFkU8vfxLvG dZRgk8u12d3d0brfpLkq2HG5Boc= =08pJ -END PGP SIGNATURE- - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Incorrect version number listed for Tomcat 6.0.x
On 07/12/17 15:24, Christopher Schultz wrote: > All, > > I'm not sure if anyone actually cares, but the archive page for Tomcat > 6 says that the latest stable version is 6.0.45 when it appears to be > 6.0.53. > > https://archive.apache.org/dist/tomcat/tomcat-6/ If we had updated the README as part of the final 6.0.x release, it would have been copied over. We could recreate the 6.0.x release area, add the corrected file, wait for it to sync and then remove the 6.0.x release area. Or someone in Infra could just edit it directly on archive.a.o The latter option seemed simpler. Done. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 8.0.48
Hi, We need more votes here Thanks, Violeta On Thu, 30 Nov 2017 at 9:19, Violeta Georgieva wrote: > The proposed Apache Tomcat 8.0.48 release is now available for voting. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.0.48/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1162/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/TOMCAT_8_0_48/ > > The proposed 8.0.48 release is: > [ ] Broken - do not release > [ ] Stable - go ahead and release as 8.0.48 > > Regards, > Violeta >
Re: [VOTE] Release Apache Tomcat 7.0.83
Hi, We need more votes here Thanks, Violeta On Thu, 30 Nov 2017 at 11:37, Violeta Georgieva wrote: > The proposed Apache Tomcat 7.0.83 release is now available for voting. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.83/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1163/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_83/ > > The proposed 7.0.83 release is: > [ ] Broken - do not release > [ ] Stable - go ahead and release as 7.0.83 Stable > > Regards, > Violeta >
Re: [VOTE] Release Apache Tomcat 8.0.48
On Thu, Nov 30, 2017 at 12:19 PM, Violeta Georgieva wrote: > The proposed Apache Tomcat 8.0.48 release is now available for voting. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.0.48/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1162/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/TOMCAT_8_0_48/ > > The proposed 8.0.48 release is: > [ ] Broken - do not release > [x] Stable - go ahead and release as 8.0.48 +1 > Regards, > Violeta - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.83
On Thu, Nov 30, 2017 at 2:37 PM, Violeta Georgieva wrote: > The proposed Apache Tomcat 7.0.83 release is now available for voting. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.83/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1163/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_83/ > > The proposed 7.0.83 release is: > [ ] Broken - do not release > [x] Stable - go ahead and release as 7.0.83 Stable +1 > Regards, > Violeta - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
