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 Rahul Akolkar <ra...@gmail.com> on 2008/05/27 23:36:42 UTC
Roadmap (was: JEXL engine)
On 5/27/08, Rony G. Flatscher (Apache) <ro...@apache.org> wrote:
<snip/>
>
> P.S.: Have been working on a local copy of BSF 2.4, but still need time to
> do all what needs to be done besides my current workload. But with your
> initiative and sebb's help things definitely move ...
>
Is the roadmap posted somewhere? What are the things you mention need
doing, and what are their priorities?
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
Re: Roadmap (was: JEXL engine)
Posted by "Rony G. Flatscher" <Ro...@wu-wien.ac.at>.
Hi sebb,
>> * incorporate the Jira-issues (e.g. suggestion to add the ability
>> for better debugging information for the Rhino-/Javascript-engine)
>> o here sebb's ideas would be incorporated by sebb, I hope
>>
>
> OK; let me know if I can help elsewhere too...
>
Thank you very much for your kind offer!
---rony
Re: Roadmap (was: JEXL engine)
Posted by sebb <se...@gmail.com>.
On 27/05/2008, Rony G. Flatscher <Ro...@wu-wien.ac.at> wrote:
>
>
> Rahul Akolkar wrote:
>
> > On 5/27/08, Rony G. Flatscher (Apache) <ro...@apache.org> wrote:
> > <snip/>
> >
> >
> > > P.S.: Have been working on a local copy of BSF 2.4, but still need time
> to
> > > do all what needs to be done besides my current workload. But with your
> > > initiative and sebb's help things definitely move ...
> > >
> > >
> > >
> >
> > Is the roadmap posted somewhere? What are the things you mention need
> > doing, and what are their priorities?
> >
> >
> No, no roadmap that I am aware of.
>
> Here are my ideas/plans for BSF 2.4:
>
> * incorporate the Jira-issues (e.g. suggestion to add the ability
> for better debugging information for the Rhino-/Javascript-engine)
> o here sebb's ideas would be incorporated by sebb, I hope
OK; let me know if I can help elsewhere too...
> * incorporate ant's BSF engine that imports the JSR-223 (a.k.a. Java
> 6/BSF 3.0) scripting engines
> o would like the default import to not replace BSF 2.4
> engines, but supply another method for that
> * add methods to the BSFManager to retrieve the registered BSF
> engines and the filetypes (extensions)
> * maybe creating a JSR-223 engine distributed with BSF 2.4 which
> would make all BSF 2.4 engines available (allowing BSF 2.4 engines
> to be employed by Java 6/BSF 3.0)
> o this would allow to deploy BSF 2.4 for Java6/BSF 3.0
> environments and interfacing with the BSF 2.4 engines using
> the JSR-223 defined interfaces
> o this might take a while though (it is a matter of having a
> few days available to get re-acquainted with JSR-223 before
> devising and implementing this)
>
> Regards
>
> ---rony
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
Re: Roadmap (was: JEXL engine)
Posted by "Rony G. Flatscher" <Ro...@wu-wien.ac.at>.
Rahul Akolkar wrote:
> On 5/27/08, Rony G. Flatscher (Apache) <ro...@apache.org> wrote:
> <snip/>
>
>> P.S.: Have been working on a local copy of BSF 2.4, but still need time to
>> do all what needs to be done besides my current workload. But with your
>> initiative and sebb's help things definitely move ...
>>
>>
>
> Is the roadmap posted somewhere? What are the things you mention need
> doing, and what are their priorities?
>
No, no roadmap that I am aware of.
Here are my ideas/plans for BSF 2.4:
* incorporate the Jira-issues (e.g. suggestion to add the ability
for better debugging information for the Rhino-/Javascript-engine)
o here sebb's ideas would be incorporated by sebb, I hope
* incorporate ant's BSF engine that imports the JSR-223 (a.k.a. Java
6/BSF 3.0) scripting engines
o would like the default import to not replace BSF 2.4
engines, but supply another method for that
* add methods to the BSFManager to retrieve the registered BSF
engines and the filetypes (extensions)
* maybe creating a JSR-223 engine distributed with BSF 2.4 which
would make all BSF 2.4 engines available (allowing BSF 2.4 engines
to be employed by Java 6/BSF 3.0)
o this would allow to deploy BSF 2.4 for Java6/BSF 3.0
environments and interfacing with the BSF 2.4 engines using
the JSR-223 defined interfaces
o this might take a while though (it is a matter of having a
few days available to get re-acquainted with JSR-223 before
devising and implementing this)
Regards
---rony