Build failure on Windows due to new jasper-deployer (and TLD files)

[Donald Woods]

Is anyone else seeing the following failure when building on Windows? I'm using trunk Rev522511 and verified the local repo contained the updated 6.0-G522103 jasper artifact (but noticed there were both 6.0.10 and 6.0-G522103 versions of the catalina file....)

[INFO]----------------------------------------------------------------------------
[INFO] Building Geronimo Configs :: JSP Examples Jetty
[INFO]    task-segment: [install]
[INFO]----------------------------------------------------------------------------
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] [car:prepare-plan]

[INFO] [car:package]

[INFO]------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]------------------------------------------------------------------------

[INFO] Generated: E:\g20\server\configs\jsp-examples-jetty\target\plan\plan.xml [INFO] Packaging module configuration: E:\g20\server\configs\jsp-examples-jetty\target\plan\plan.xml [INFO] Could not scan directory for TLD files: jar:file:/C:/Documents and Settings/drwoods/.m2/repository/commons-jexl/commons-jexl/1.1/commons-jexl-1.1.jar!/META-INF Illegal character in path at index 18: file:/C:/Documents and Settings/drwoods/.m2/repository/commons-jexl/commons-jexl/1.1/commons-jexl-1.1.jar

smime.p7s
Description: S/MIME Cryptographic Signature