Parsing JSPs into java source code via tomcatJasper task in gradle tomcat plugin

The following are excerpts from my build.gradle and other various files.

apply plugin: 'com.bmuschko.tomcat'
buildscript {
    repositories {

    dependencies {
        classpath 'com.bmuschko:gradle-tomcat-plugin:2.2.2'

repositories {

dependencies {

    def tomcatVersion = '6.0.43'
    tomcat "org.apache.tomcat:catalina:${tomcatVersion}",

task copyJSPs(type: Copy) {
    //mkdir(dir: "build/jsps/WEB-INF/")
    from("${properties_common_dir}/WEB-INF/web.xml") {
    from(fileTree(dir: "${source_dir}", include: ["**.jsp*", "**/SA_menu.html", "**/SA_main.html"], excludes: ["**/admin/*.jsp", "**/pl/**/jsp/*.jsp", "**/Kalotay.jsp"]).files) {
    from(fileTree("${source_dir}").files) {
        include "**/agreement.html"
        include "**/consensus.html"
        include "**/footer.html"
        include "**/dynamicDisplayTable.txt"
        include "**/brokerDisclaimer.html"
        include "**/traderDisclaimer.html"


tomcat {
    jasper {
        errorOnUseBeanInvalidClassAttribute = false
        validateXml = false
        outputDir = file("${jspbuild_dir}")
        webXmlFragment = file("${jspbuild_dir}/WEB-INF/generated_web.xml")
        uriroot = file("${jspbuild_dir}")
        poolingEnabled = false

When trying to run the the following commands:

:gradle copyJSPs
:gradle tomcatJasper

I get a number of errors. My JSPs are copied just fine and dandy, however when I get to running tomcatJasper I get an exception and error. Seen here:

FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':tomcatJasper'.
> org.apache.jasper.JasperException: file:/usr/local/tmc/twa_web/build/jsps/Header.jsp(10,0) The value for the useBean class attribute com.muni.web.beans.MessageBean is invalid.

That error does not occur if I parse the JSPs with an ant task. I can not figure out why this is occuring, especially because I have the property

errorOnUseBeanInvalidClassAttribute = false

Has anyone ever come into a similar error? Is it a bug in TomCat6? Thanks for your help!