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 Wed, 16 Dec 2009 16:44:32 GMT
In case anyone else tries this.... to build jetty itself (not our  
integration) you need

mvn clean install -Pgeronimo-spec


I'll try to find out what's going on with this too.
thanks
david jencks

On Dec 16, 2009, at 5:39 AM, Rick McGuire wrote:

> David Jencks wrote:
>> I updated jetty with the api fixes and made our jetty8 build  
>> against the latest trunk.  Stuff seems to work for me....
>>
>> I've asked the jetty folks to push a new snapshot but I'm not sure  
>> if they have yet.
> The new snapshot has not been pushed yet, so I had to build jetty  
> myself.  When trying to do that, I'm still getting compilation  
> errors because the servlet-api version is prefers seems out of  
> date.  I'm not sure I understand what the situation is with their  
> servlet-api version.  However, I was able to build it successfully  
> using the latest geronimo servlet spec.
>
> Once I got a good jetty build, I was able to get a good complete  
> build.  Thank you so much for tracking this down!
>
> Rick
>
>>
>> thanks
>> david jencks
>>
>> On Dec 15, 2009, at 9:16 AM, David Jencks wrote:
>>
>>> I'll look into this.  Ivan identified some api errors in our  
>>> servlet 3 jar and it's possible that jetty has not picked up the  
>>> fixes (I'm not sure where jetty got their spec jar from).
>>>
>>> thanks
>>> david jencks
>>>
>>> On Dec 15, 2009, at 6:24 AM, Rick McGuire wrote:
>>>
>>>> David Jencks wrote:
>>>>> 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.
>>>> I'm able to get things to build until I get to jetty, then I'm  
>>>> stuck.  What version of jetty should we be using and where do we  
>>>> get it?  I've tried building it myself from
>>>>
>>>> http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/branches/jetty-8
>>>>
>>>> But I get compilation errors in jetty-continuation because of a  
>>>> serlet 3.0 api mismatch.  If I switch to using the Geronimo spec  
>>>> version, I get a different error.  The jetty trunk version  
>>>> appears to build 7.0.2 artifacts, not jetty-8, so I think this is  
>>>> the correct branch.  This is using a servlet 3.0 spec pulled from  
>>>> org.mortbay.jetty, but I haven't located the source for this  
>>>> package yet to try to build the latest version of that locally  
>>>> either.
>>>>
>>>> Rick
>>>>>
>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>


Mime
View raw message