Hi, just find that while stopping the server, there is some exceptions about
failing to unregister some Tomcat MBeans, I guess that there is still some
issues about MBean in Tomcat while I pull the codes. However, I did not
think that it is a blocking error. If no objection, I would pass the vote
forget my +1 :-)
2010/5/5 Joe Bohn joe.b...@earthlink.net
+1 (assuming the potential license issue mentioned below is not an issue)
I was able to build and run the new tomcat image.
The license issue pointed out last time is now resolved but there is one
other potential issue. I noticed
On May 4, 2010, at 1:56 PM, Joe Bohn wrote:
+1 (assuming the potential license issue mentioned below is not an issue)
I was able to build and run the new tomcat image.
The license issue pointed out last time is now resolved but there is one
other potential issue. I noticed a number
On Wed, May 5, 2010 at 7:45 PM, Kevan Miller kevan.mil...@gmail.com wrote:
On May 4, 2010, at 1:56 PM, Joe Bohn wrote:
+1 (assuming the potential license issue mentioned below is not an issue)
I was able to build and run the new tomcat image.
The license issue pointed out last time
I think that our four version numbers could help us, while Tomcat always has
three version number. In next iteration, we call our version 7.0.0.1, which
means more changes are merged from Tomcat 7 dev tree ..
2010/5/5 Vamsavardhana Reddy c1vams...@gmail.com
On Wed, May 5, 2010 at 7:45 PM,
IIRC I came up with the 4 digits and I was thinking exactly this, we can
release many ports of a given tomcat release this way. Having the same number
of digits as tomcat won't work. If they used 4 we'd be in trouble :-)
thanks
david jencks
On May 5, 2010, at 5:43 PM, Ivan wrote:
I think
Agree, We can just add a comment in its pom, which records the revision our
external tomcat based on.
-Rex
2010/5/6 Ivan xhh...@gmail.com
I think that our four version numbers could help us, while Tomcat always
has three version number. In next iteration, we call our version 7.0.0.1,
which
Everything built correctly and I don't see any obvious license or header
problems this time.
+1
On 5/4/2010 5:10 AM, Ivan wrote:
Please vote for Geronimo Customized Tomcat 7.0.0.0
Vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
+1 (assuming the potential license issue mentioned below is not an issue)
I was able to build and run the new tomcat image.
The license issue pointed out last time is now resolved but there is one
other potential issue. I noticed a number of files under jasper-el that
are generated using