You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bsf-dev@jakarta.apache.org by Ulf Dittmer <ul...@ulfdittmer.com> on 2006/01/23 10:11:15 UTC

for release: Rhino 1.6 compatibility

Hello all-

Since there's talk about getting a release out, one thing to please make
sure is compatibility with the latest Rhino release (1.6R2 at the moment).
I don't know who maintains the JS engine -probably not the core BSF team,
I have no idea- but maybe whoever does is listening.
That's been bugging me (and others) ever since I started using BSF, that
2.2 works with a different Rhino than 2.3, and neither works with the
latest. (If the current CVS version already works with it, forget what I
said, and sorry for wasting your time.)

Cheers,
Ulf



---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org


Actual BSF version, interfacing to Java via strings only ... ( Re: Rhino 1.6 compatibility

Posted by "Rony G. Flatscher" <Ro...@wu-wien.ac.at>.
Hi Ulf,
> Thanks for the pointer to the nightly build. Indeed, it works like a 
> charm with the latest Rhino, and also compiles and runs with my Prolog 
> BSF engine. Great work!
Good to hear!

Will announce it in this group, should a new build of BSF come up in the 
context of the BSF4Rexx project.

BTW, you probably could use the class  
"org.rexxla.bsf.engines.Rexx.RexxAndJava", method "javaCallBSF" (call 
Java via BSF), cf. the docs in "docs_bsf4rexx.zip". This would allow you 
to interact with Java strictly with strings and still be able to 
interface with all kind and type of objects. There is also an easy way 
to create and interact with Java arrays, and much more. (Or with other 
words, there is nothing Rexx-specific there, so any non-Java based 
scripting engine could take advantage of the functionality of that class 
to ease full interfacing to Java.) The latest build of the entire 
package is at the moment at: 
<http://wi.wu-wien.ac.at/rgf/rexx/bsf4rexx/dist.20060124/>, it includes 
the aofrementioned docs.

Regards,

---rony

---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org


Re: Rhino 1.6 compatibility

Posted by Ulf Dittmer <ul...@ulfdittmer.com>.
Hi-

Thanks for the pointer to the nightly build. Indeed, it works like a 
charm with the latest Rhino, and also compiles and runs with my Prolog 
BSF engine. Great work!

Cheers,
Ulf


On 23.01.2006, at 10:25, Rony G. Flatscher wrote:

> AFAIC the SVN version of BSF *does* work with the latest Rhino!
>
> P.S.: You can get at an actual build of BSF, ...


---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org


Changing setup in Apache's world, how ? (Re: for release: Rhino 1.6 compatibility

Posted by "Rony G. Flatscher" <Ro...@wu-wien.ac.at>.
Hi Sanka,

>> That's the reason why I would think it to be important to have an
>> automated build-mechanism (at least triggered by check-ins into the SVN).
>>     
>
> +1 !!,
>
> We do that in most of ws-* projects at Apache where each commit
> triggers an automated build mechanisam which builds a new
> -SNAPSHOT-.jar from the fresh codebase.
>   
That sounds sound!
;)
> I dont see any reason why we couldn't or shouldn't do same with BSF.
>
> Does anyone have any idea on how to do this? I can start to work on
> that we someone can provide me some guidance.
>   
Unfortunately, I have no idea whatsoever, as I have never done that in 
Apache's world. Maybe someone who is in the know can give a hand, URLs 
or even help in the iChnitial setup?

Regards,

---rony


Re: for release: Rhino 1.6 compatibility

Posted by Sanka Samaranayake <ss...@gmail.com>.
Hi All,

On 1/23/06, Rony G. Flatscher <Ro...@wu-wien.ac.at> wrote:
> Hi Ulf,
>
> >Since there's talk about getting a release out, one thing to please make
> >sure is compatibility with the latest Rhino release (1.6R2 at the moment).
> >I don't know who maintains the JS engine -probably not the core BSF team,
> >I have no idea- but maybe whoever does is listening.
> >That's been bugging me (and others) ever since I started using BSF, that
> >2.2 works with a different Rhino than 2.3, and neither works with the
> >latest. (If the current CVS version already works with it, forget what I
> >said, and sorry for wasting your time.)
> >
> >
> AFAIC the SVN version of BSF *does* work with the latest Rhino!

yes, that is my understanding too.

>
> That's the reason why I would think it to be important to have an
> automated build-mechanism (at least triggered by check-ins into the SVN).

+1 !!,

We do that in most of ws-* projects at Apache where each commit
triggers an automated build mechanisam which builds a new
-SNAPSHOT-.jar from the fresh codebase.

I dont see any reason why we couldn't or shouldn't do same with BSF.

Does anyone have any idea on how to do this? I can start to work on
that we someone can provide me some guidance.

Best,
Sanka


>
> Regards,
>
> ---rony
>
> P.S.: You can get at an actual build of BSF, if you retrieve the
> installation package (in beta) of "BSF4Rexx", which allows employing
> ooRexx (http://www.ooRexx.org); look for the file
> "bsf-v204-20060117.jar" in "BSF4Rexx_install.zip". (This package
> supports Windows and Linux out of the box, also, it may be interesting
> to know that it uses the OpenOffice Java interfaces to script/automate
> OpenOffice via BSF; a set of samples is installed with the package.)
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org


Re: for release: Rhino 1.6 compatibility

Posted by "Rony G. Flatscher" <Ro...@wu-wien.ac.at>.
Hi Ulf,

>Since there's talk about getting a release out, one thing to please make
>sure is compatibility with the latest Rhino release (1.6R2 at the moment).
>I don't know who maintains the JS engine -probably not the core BSF team,
>I have no idea- but maybe whoever does is listening.
>That's been bugging me (and others) ever since I started using BSF, that
>2.2 works with a different Rhino than 2.3, and neither works with the
>latest. (If the current CVS version already works with it, forget what I
>said, and sorry for wasting your time.)
>  
>
AFAIC the SVN version of BSF *does* work with the latest Rhino!

That's the reason why I would think it to be important to have an 
automated build-mechanism (at least triggered by check-ins into the SVN).

Regards,

---rony

P.S.: You can get at an actual build of BSF, if you retrieve the 
installation package (in beta) of "BSF4Rexx", which allows employing 
ooRexx (http://www.ooRexx.org); look for the file 
"bsf-v204-20060117.jar" in "BSF4Rexx_install.zip". (This package 
supports Windows and Linux out of the box, also, it may be interesting 
to know that it uses the OpenOffice Java interfaces to script/automate 
OpenOffice via BSF; a set of samples is installed with the package.)




---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org