I fixed it in my copy of tomcat (external/trunk/tomcat-parent-7.0.0) and deployed a snapshot so I'm wondering why you are still seeing this.

On the other hand I am seeing some of the portlet projects pull in tomcat6 and hang during the car plugin phase on puglins/console/plugin- console-tomcat. I'm going to continue trying to update all the references from tomcat6 to tomcat7.

thanks
david jencks

On Dec 14, 2009, at 3:45 AM, Rick McGuire wrote:

Jarek Gawor wrote:
I see it when building plugins/activemq/activemq-portlets when the
jspc-maven-plugin kicks in.


It looks like this occurs on all of the portlet subprojects.

Rick

Jarek

On Fri, Dec 11, 2009 at 10:03 PM, Ivan <[email protected]> wrote:

Do you only get this error while using Tomcat 7 ? It seems that we get the
runtime resource issue again.

2009/12/12 Jarek Gawor <[email protected]>

I'm getting the same error.

Jarek

On Fri, Dec 11, 2009 at 2:09 PM, David Jencks <[email protected] >
wrote:

I'm seeing this kind of error in building console bits... anyone else
seeing
it or know how to fix it? Maybe I need to build something locally???
Haven't looked far yet.

[INFO] snapshot
org.apache.geronimo.ext.tomcat:jasper-el:7.0.0.0-SNAPSHOT:
checking for updates from ops4j.snapshots
[INFO] [jspc:compile {execution: default}]
Created dir:

/Users/david/projects/geronimo/server/trunk/plugins/console/ console-base-portlets/target/jsp-source
[INFO] Compiling JSP source files to

/Users/david/projects/geronimo/server/trunk/plugins/console/ console-base-portlets/target/jsp-source
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The absolute uri: http://java.sun.com/jsp/jstl/fmt cannot be
resolved
in either web.xml or the jar files deployed with this application
[INFO]
------------------------------------------------------------------------

thanks
david jencks



--
Ivan






Reply via email to