[#APF-823] Upgrade maven-jetty-plugin to 6.1.5 and Cargo's Tomcat version to 6.0.14

AppFuse

Upgrade maven-jetty-plugin to 6.1.5 and Cargo's Tomcat version to 6.0.14

Created: 23/Jun/07 08:31 PM Updated: 01/Feb/08 08:49 AM

Component/s:

Application Servers, Installation

Affects Version/s:

2.0-M5

Fix Version/s:

2.0-RC1

Description

« Hide

Comment out el-api dependency for JSF:

http://raibledesigns.com/rd/entry/upgrading_to_tomcat_6

If someone wants to use Tomcat 5.5, they can add this back in. Add the commented out dependency to archetype's pom.xml's so users can easily change it.

Why do this upgrade? Because we eventually want to upgrade to JSF 1.2 and that will require we use these latest containers. Also, newer versions often have performance optimizations and speed improvements, so we want users to use the latest and greatest.

All

Comments

Change History

FishEye

Sort Order:

[ Permlink | « Hide ]

Matt Raible - 23/Jun/07 09:26 PM

Backed off upgrading Cargo's JBoss version to 4.2.0 GA since it doesn't seem compatible with Cargo. There's all kinds of exceptions send to the console when you try to use this version.

[ Permlink | « Hide ]

Matt Raible - 27/Aug/07 12:43 PM

Reopening to change issue from Jetty 6.1.4 to 6.1.5 and Tomcat from 6.0.13 to 6.0.14.

[ Permlink | « Hide ]

Porter Woodward - 01/Feb/08 08:49 AM

Something is broken with the version of Tomcat 6.0.14 in cargo.

When the Appfuse/Maven default build/test cycle is kicking off from the "quick start" - I get a zlib error when it attempts to unzip the Tomcat archive. Looking at it, I see that it's only 4MB in size. The Tomcat 6.0.14 from the Apache site is 6MB. It's possible that the download of cargo to my local repo was corrupted - but unlikely. I just copy in a local copy of a complete/correct zip of Tomcat 6.0.14 to the temp director and the build/test finishes w/o a problem.