RE: 4.1.7 / mod_jk 1.2.0 / mod_jk 2.0.0

[GOMEZ Henri]

>Henri: what about tagging the workspace for mod_jk1 with 1.2.0, 
>and use the same naming convention as in 4.1.x.

How did I take jk/native (only) as mod_jk_1_2_0 ?

cvs tag -r mod_jk_1_2_0 jk/native ?

>Nacho, Mladen: same thing for mod_jk2 - we should use the 'milestone'
>style, and mod_jk2.0.0 will be the first tagged milestone. There is
>no need for anything fancy - it's just an alpha release.
>
>I think we should try to synchronize a bit - and maybe tag jk1.2.0 
>and jk2.0.0 at the same time with 4.1.7.  
>
>
>Costin
>
>
>--
>To unsubscribe, e-mail:   
>
>For additional commands, e-mail: 
>
>
>

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: 4.1.7 / mod_jk 1.2.0 / mod_jk 2.0.0

[Remy Maucherat]

[EMAIL PROTECTED] wrote:
> Remy: I just fixed one serious bug in jk2/java ( the one reported by 
> David Oxley ). I think we need a 4.1.7 for that ( and possibly other
> bug fixes ). We are pretty close IMHO.
> 
> Henri: what about tagging the workspace for mod_jk1 with 1.2.0, 
> and use the same naming convention as in 4.1.x.
> 
> Nacho, Mladen: same thing for mod_jk2 - we should use the 'milestone'
> style, and mod_jk2.0.0 will be the first tagged milestone. There is
> no need for anything fancy - it's just an alpha release.
> 
> I think we should try to synchronize a bit - and maybe tag jk1.2.0 
> and jk2.0.0 at the same time with 4.1.7.  

Ok. I'll see if there are some other critical fixes that are needed to 
4.1.6. So far, I didn't get any report of serious problems (except DBCP 
issues; I'll update again to pick up the latest changes; Glenn, could 
you comment on that if you're around ?), so I'd say it looks good and 
I'll do the release (and I hope it will be beta worthy :-D).

We'll have to go do a cleanup of Bugzilla someday. Many bugs there are 
not relevant to 4.1.x, though. I'll try to update the version of those 
which are confirmed or in need of a review to be to a 4.1.x number.

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: 4.1.7 / mod_jk 1.2.0 / mod_jk 2.0.0

[Brian P. Millett]

On Tue, 2002-07-02 at 15:47, [EMAIL PROTECTED] wrote:
> Remy: I just fixed one serious bug in jk2/java ( the one reported by 
> David Oxley ). I think we need a 4.1.7 for that ( and possibly other
> bug fixes ). We are pretty close IMHO.
> 
> Henri: what about tagging the workspace for mod_jk1 with 1.2.0, 
> and use the same naming convention as in 4.1.x.
> 
> Nacho, Mladen: same thing for mod_jk2 - we should use the 'milestone'
> style, and mod_jk2.0.0 will be the first tagged milestone. There is
> no need for anything fancy - it's just an alpha release.
> 
> I think we should try to synchronize a bit - and maybe tag jk1.2.0 
> and jk2.0.0 at the same time with 4.1.7.  

For what it is worth, here are two patches (not pretty) to get the
tomcat 4.1.6-LE-jdk1.4 to compile with the struts-1.1-b1.  Don't know if
you want this for 4.1 final.

--- jakarta-tomcat-4.1.6-LE-jdk14-src/webapps/admin/build.xml~  Fri Jun
28 11:03:48 2002
+++ jakarta-tomcat-4.1.6-LE-jdk14-src/webapps/admin/build.xml   Sat Jun 29
17:27:13 2002
@@ -22,6 +22,7 @@
 
 
 
+
   
 
 
@@ -140,6 +141,7 @@
   
   
 
+
 
 
 


AND:
---
jakarta-tomcat-4.1.6-LE-jdk14-src/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/AttributeTag.java~
  Fri Jun 28 11:03:48 2002
+++
jakarta-tomcat-4.1.6-LE-jdk14-src/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/AttributeTag.java
   Sat Jun 29 17:07:50 2002
@@ -70,8 +70,7 @@
 import javax.servlet.jsp.JspWriter;
 import javax.servlet.jsp.PageContext;
 import javax.servlet.jsp.tagext.TagSupport;
-import org.apache.struts.util.PropertyUtils;
-
+import org.apache.commons.beanutils.PropertyUtils;
 
 /**
  * Custom tag that retrieves a JMX MBean attribute value, and writes it

 
-- 
Brian Millett
Enterprise Consulting Group   "Shifts in paradigms
(314) 205-9030   often cause nose bleeds."
[EMAIL PROTECTED]   Greg Glenn


--
To unsubscribe, e-mail:   
For additional commands, e-mail: