geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: build problem?
Date Thu, 17 Dec 2009 09:30:33 GMT
Looking at JasperListener I think we don't need it.  We can add a  
gbean to the jasper module to do the same thing.  Hopefully this will  
eliminate the dependency of tomcat on jasper.

thanks
david jencks

On Dec 15, 2009, at 5:28 AM, Ivan wrote:

> I worked around this by adding DynamicImport-Package:  
> org.apache.jasper.* to the catalina bundle. Could not see whether  
> they are other ways to solve it.
> While after that, I got other issues. Will continue to investigate it.
>
> 2009/12/15 Ivan <xhhsld@gmail.com>
> Finally, I could built the plugin folder (Jetty releated are  
> commented out, as I just wish to try Tomcat).
> When starting the welcome server, I got a class not found exception  
> in JasperListener class, it tries to load a class in jasper modules,  
> certainly it failed. I remembered that Jarek or someone else has  
> mentioned it in the past.
>
> 2009/12/15 David Jencks <david_jencks@yahoo.com>
>
> I finally got trunk to build for me....
> there were a few more tomcat6 refeences that I think were confusing  
> feilix and preventing it from figuring out which tomcat bundle to  
> wire to.
>
> Mark Thomas has fixed the jspc issue in tomcat trunk so I'll out  
> regenerating external/trunk/tomcat-parent-7.0.0.
>
> I'd be curious if anyone else can build trunk successfully.
>
> thanks
> david jencks
>
>
> On Dec 14, 2009, at 8:04 AM, David Jencks wrote:
>
> 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 <xhhsld@gmail.com> 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 <jgawor@gmail.com>
>
> I'm getting the same error.
>
> Jarek
>
> On Fri, Dec 11, 2009 at 2:09 PM, David Jencks <david_jencks@yahoo.com>
> 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
>
>
>
>
>
>
>
>
>
>
> -- 
> Ivan
>
>
>
> -- 
> Ivan


Mime
View raw message