cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: [GUMP] Build Failure - Cocoon
Date Fri, 28 Mar 2003 09:12:00 GMT
Christopher Oliver wrote:
> Stefano Mazzocchi wrote:
> 
> 
>>> compile-core:
>>>      [copy] Copying 41 files to 
>>> /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030327/classes
>>>      [copy] Copied 37 empty directories to 
>>> /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030327/classes
>>>     [javac] Compiling 1 source file to 
>>> /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030327/mocks
>>>     [javac] Compiling 515 source files to 
>>> /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030327/classes
>>>     [javac] 
>>> /home/rubys/jakarta/cocoon-2.1/src/java/org/apache/cocoon/components/flow/javascript/JavaScriptInterpreter.java:194:

>>> cannot resolve symbol
>>>     [javac] symbol  : method setOptimizationLevel (int)
>>>     [javac] location: class org.mozilla.javascript.tools.debugger.Main
>>>     [javac]             db.setOptimizationLevel(OPTIMIZATION_LEVEL);
>>>     [javac]               ^
>>
>>
>>
>> Chris,
>>
>> I think your latest rhino debugging modifications broke Gump. Can you 
>> please help me taking care of this? TIA.
>>
>> Stefano.
>>
> 
> Sure, I'd like to. But I don't understand how this error could be 
> generated unless Gump is using the non-continuations-enabled version of 
>  Rhino?

ah, that explains it.

> Can you configure Gump to build against the the version from 
> cocoondev.org? 

well, yes, even you could. all ASF committers have access to the 
jakarta-gump CVS module.

> Or what's the best approach?

I'm more and more concerned about the fact that we are, in fact, forking 
rhyno and calling it with the same name, this is a very bad practice, 
it's very close to steal visibility.

Am I the only one bothered by this?

Stefano.



Mime
View raw message