Mailing-List: contact bsf-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Bean Scripting Framework developers" <bsf-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of ssanka@gmail.com designates
 66.249.82.205 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=X852vLIc/oPFeTacWFETKHzArLzlrnGpcaFIM5VGUBUMO8WmEExlGM+NeISCg4G6rLPhGO8UuYdQXQXKAPJ649ujJqUTGCMuTmoUzgkQyS4sl3cQHvMS9949vJhsLUKp4/OAjx+68P8Jm9YuPfdTF6Mn8cj9Fxb/APjUkGydp4g=
Message-ID: <1e8c1ed40601230802j5ed1a6b1r6853066a37790cb@mail.gmail.com>
Date: Mon, 23 Jan 2006 22:02:20 +0600
From: Sanka Samaranayake <ssanka@gmail.com>
To: Bean Scripting Framework developers <bsf-dev@jakarta.apache.org>
Subject: Re: for release: Rhino 1.6 compatibility
In-Reply-To: <43D4A119.2070201@wu-wien.ac.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: 
 <1354.213.61.134.194.1138007475.squirrel@bobcattools.webappcabaret.net>
	 <43D4A119.2070201@wu-wien.ac.at>

Hi All,

On 1/23/06, Rony G. Flatscher <Rony.Flatscher@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