You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Alex O'Ree <al...@apache.org> on 2023/01/31 22:20:29 UTC
Commons bsf
Is the bsf library still supported? Looks like the website hasn't been
published since 2011.
Re: Commons bsf
Posted by aisen faith marrero <fa...@gmail.com>.
Thank you for your application for the role of senior data.
On Wed, Feb 1, 2023 at 1:43 PM robertlazarski <ro...@gmail.com>
wrote:
> On Wed, Feb 1, 2023 at 3:32 AM robertlazarski <ro...@gmail.com>
> wrote:
>
> >
> >
> > A couple years ago after using J2V8 - they only support Android now - we
> > moved to the Javet project that is Apache licensed.
> >
> > On a scale of 1/10 I give it a 10. They do an impressive release about
> > once a month lately and most importantly they ship with the latest V8
> which
> > is important for us.
> >
> > If you need something else besides JS though I have no idea.
> >
>
> I forgot about GraalVM but the performance wasn't much better than Rhino
> but it is a small improvement.
>
> For us, Javet is by far the best one out there.
>
ad J2V8 (Re: Commons bsf
Posted by "Rony G. Flatscher" <Ro...@wu.ac.at>.
On 01.02.2023 14:42, robertlazarski wrote:
> On Wed, Feb 1, 2023 at 3:32 AM robertlazarski <ro...@gmail.com>
> wrote:
>
>> A couple years ago after using J2V8 - they only support Android now - we
>> moved to the Javet project that is Apache licensed.
>>
>> On a scale of 1/10 I give it a 10. They do an impressive release about
>> once a month lately and most importantly they ship with the latest V8 which
>> is important for us.
>>
>> If you need something else besides JS though I have no idea.
>>
> I forgot about GraalVM but the performance wasn't much better than Rhino
> but it is a small improvement.
>
> For us, Javet is by far the best one out there.
It seems that Google's J2V8 according to [1] does not support JSR-223/BSF, which is unfortunate as
it breaks/ignores the Java scripting framework (BSF 3 would have allowed them to employ it in the
Harmony days already).
Your complaints seem to be about the speed of different JavaScript implementations in Java, if I
read that correctly, and that you have experienced that Google's JavaScript implementation is the
fastest and the preferred one for you.
---rony
[1] J2V8: <https://eclipsesource.com/blogs/tutorials/getting-started-with-j2v8/>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: ad J2V8 (Re: Commons bsf
Posted by "Rony G. Flatscher (Apache)" <ro...@apache.org>.
On 02.02.2023 17:02, robertlazarski wrote:
> On Thu, Feb 2, 2023 at 5:23 AM Rony G. Flatscher (Apache) <ro...@apache.org>
> wrote:
>
>> On 01.02.2023 14:42, robertlazarski wrote:
>>> On Wed, Feb 1, 2023 at 3:32 AM robertlazarski <ro...@gmail.com>
>>> wrote:
>>>
>>>> A couple years ago after using J2V8 - they only support Android now - we
>>>> moved to the Javet project that is Apache licensed.
>>>>
>>>> On a scale of 1/10 I give it a 10. They do an impressive release about
>>>> once a month lately and most importantly they ship with the latest V8
>> which
>>>> is important for us.
>>>>
>>>> If you need something else besides JS though I have no idea.
>>>>
>>> I forgot about GraalVM but the performance wasn't much better than Rhino
>>> but it is a small improvement.
>>>
>>> For us, Javet is by far the best one out there.
>> It seems that Google's J2V8 according to [1] does not support JSR-223/BSF,
>> which is unfortunate as
>> it breaks/ignores the Java scripting framework (BSF 3 would have allowed
>> them to employ it in the
>> Harmony days already).
>>
>> Your complaints seem to be about the speed of different JavaScript
>> implementations in Java, if I
>> read that correctly, and that you have experienced that Google's
>> JavaScript implementation is the
>> fastest and the preferred one for you.
>>
>> ---rony
>>
>> [1] J2V8: <
>> https://eclipsesource.com/blogs/tutorials/getting-started-with-j2v8/>
>>
>>
>>
> The terminology here is confusing however it is important to get it right.
>
> For the record, I am an Apache committer (PMC chair of Axis web services
> and no relation here) and am speaking in terms of the state of JSR-223.
>
> Speaking broadly here as not a contributor, but someone who built and
> studied the source of these projects below.
>
> V8 is the JavaScript engine that Google supports for Chrome. It is written
> in C. It has no relation to JSR-223 besides some Java people want to run it
> via JNI.
Java people usually use Java, JSR-223 is the package javax.script which should be used by scripting
engines. It would allow to exploit V8 from any Java application that employs javax.script for
executing scripts.
> V8 progresses very rapidly in performance so old jars are not a good fit.
Not sure what you mean when referring to "old jars". java.lang.Object is probably older than many
"old jars", yet, it is of vital importance and up-to-date, despite being old. So age is not
necessarily an indicator for obsolescence.
> J2V8 is a one man project with no relation to Google. At one point the
> individual provided OS specific jars with C libs and JNI code but a while
> back dropped all support except Android.
If javax.script/JSR-223 is not available on Android - not even in the OpenJDK deployments - then
this may make sense (having a non-standard, individual interface), however it impedes the Java
infrastructure in the scripting application area. In such a case BSF 3 may be helpful in bringing
javax.script to the Android table, allowing Java apps to exploit any scripting engine that is made
available to Android via this standard Java scripting framework. (Will eventually know more as I
might be able to explore these very waters on Android sometimes in the near future.)
> Javet is a one man project as well, who like my day job also needed to move
> on from J2V8.
Having briefly looked at
<https://sjtucaocao.medium.com/javet-java-and-javascript-interop-245c28210f32> what is described
there (allowing Java objects to be shared with the V8 JavaScript engine) is what the
javax.script/JSR-223 framework has been defining in a standardized way, cf. e.g. ScriptContext and
Bindings in <https://docs.oracle.com/javase/8/docs/api/javax/script/package-summary.html>. This way
a Java programmer can register whatever Java objects they want to share with the scripting engine
that evals the Java supplied script code.
---
To get an idea what javax.script (BSF3) allows for in the context of web applications (having
learned your PMC role in Apache Axis) you could take a look at
<https://sourceforge.net/projects/bsf4oorexx/files/Sandbox/rgf/taglibs/ga/> where JSPs programmed
with scripting languages becomes possible. There was a ApacheCon Tomcat presentation about it, the
slides can be found at
<https://sourceforge.net/projects/bsf4oorexx/files/Sandbox/rgf/taglibs/ga/AC21-Flatscher-EnablingScriptingLanguagesInJsps-v05.pdf>.
Demonstration examples were created in the scripting languages ooRexx (using BSF and implementing in
addition JSR-223), Nashorn JavaScript, Jython, PHP (caucho's Resin) and Groovy. Any scripting
language that has an implementation of javax.script.Engine (very simple to create if one extends
javax.script.AbstractEngine) could be used in addition out of the box.
There are also non-Web-related applications for which javax.script/JSR-223 script engines get
exploited for scripting and macros, as it makes it very easy for Java programmers to allow for
running scripts and macros against any Java application (adding scriptability to any Java
application). Another example may be Apache OpenOffice which supplies Java APIs. Thanks to the Java
APIs ooRexx (open object Rexx originally written by IBM in C++, open-sourced 2005 by
https://www.rexxla.org) can be used as a macro language and it can be used to write programs that
control AOO/LO via Java (both realized via the ooRexx-Java bridge BSF4ooRexx850) in a platform
independent manner (exploiting Java's "write once, run everywhere").
Notabene, if a scripting language implements javax.script/JSR-223 [Abstract]Engine it is a
no-brainer for acquainted Java developers to employ any such script engine easily for evaluating
scripts and even let them interact with supplied Java objects. Therefore I had assumed that V8
implements javax.script/JSR-223 making it immediately available as a Java scripting engine to any
Java application on any platform.
---rony
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: ad J2V8 (Re: Commons bsf
Posted by robertlazarski <ro...@gmail.com>.
On Thu, Feb 2, 2023 at 5:23 AM Rony G. Flatscher (Apache) <ro...@apache.org>
wrote:
> On 01.02.2023 14:42, robertlazarski wrote:
> > On Wed, Feb 1, 2023 at 3:32 AM robertlazarski <ro...@gmail.com>
> > wrote:
> >
> >> A couple years ago after using J2V8 - they only support Android now - we
> >> moved to the Javet project that is Apache licensed.
> >>
> >> On a scale of 1/10 I give it a 10. They do an impressive release about
> >> once a month lately and most importantly they ship with the latest V8
> which
> >> is important for us.
> >>
> >> If you need something else besides JS though I have no idea.
> >>
> > I forgot about GraalVM but the performance wasn't much better than Rhino
> > but it is a small improvement.
> >
> > For us, Javet is by far the best one out there.
>
> It seems that Google's J2V8 according to [1] does not support JSR-223/BSF,
> which is unfortunate as
> it breaks/ignores the Java scripting framework (BSF 3 would have allowed
> them to employ it in the
> Harmony days already).
>
> Your complaints seem to be about the speed of different JavaScript
> implementations in Java, if I
> read that correctly, and that you have experienced that Google's
> JavaScript implementation is the
> fastest and the preferred one for you.
>
> ---rony
>
> [1] J2V8: <
> https://eclipsesource.com/blogs/tutorials/getting-started-with-j2v8/>
>
>
>
The terminology here is confusing however it is important to get it right.
For the record, I am an Apache committer (PMC chair of Axis web services
and no relation here) and am speaking in terms of the state of JSR-223.
Speaking broadly here as not a contributor, but someone who built and
studied the source of these projects below.
V8 is the JavaScript engine that Google supports for Chrome. It is written
in C. It has no relation to JSR-223 besides some Java people want to run it
via JNI.
V8 progresses very rapidly in performance so old jars are not a good fit.
J2V8 is a one man project with no relation to Google. At one point the
individual provided OS specific jars with C libs and JNI code but a while
back dropped all support except Android.
Javet is a one man project as well, who like my day job also needed to move
on from J2V8.
ad J2V8 (Re: Commons bsf
Posted by "Rony G. Flatscher (Apache)" <ro...@apache.org>.
On 01.02.2023 14:42, robertlazarski wrote:
> On Wed, Feb 1, 2023 at 3:32 AM robertlazarski <ro...@gmail.com>
> wrote:
>
>> A couple years ago after using J2V8 - they only support Android now - we
>> moved to the Javet project that is Apache licensed.
>>
>> On a scale of 1/10 I give it a 10. They do an impressive release about
>> once a month lately and most importantly they ship with the latest V8 which
>> is important for us.
>>
>> If you need something else besides JS though I have no idea.
>>
> I forgot about GraalVM but the performance wasn't much better than Rhino
> but it is a small improvement.
>
> For us, Javet is by far the best one out there.
It seems that Google's J2V8 according to [1] does not support JSR-223/BSF, which is unfortunate as
it breaks/ignores the Java scripting framework (BSF 3 would have allowed them to employ it in the
Harmony days already).
Your complaints seem to be about the speed of different JavaScript implementations in Java, if I
read that correctly, and that you have experienced that Google's JavaScript implementation is the
fastest and the preferred one for you.
---rony
[1] J2V8: <https://eclipsesource.com/blogs/tutorials/getting-started-with-j2v8/>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: Commons bsf
Posted by robertlazarski <ro...@gmail.com>.
On Wed, Feb 1, 2023 at 3:32 AM robertlazarski <ro...@gmail.com>
wrote:
>
>
> A couple years ago after using J2V8 - they only support Android now - we
> moved to the Javet project that is Apache licensed.
>
> On a scale of 1/10 I give it a 10. They do an impressive release about
> once a month lately and most importantly they ship with the latest V8 which
> is important for us.
>
> If you need something else besides JS though I have no idea.
>
I forgot about GraalVM but the performance wasn't much better than Rhino
but it is a small improvement.
For us, Javet is by far the best one out there.
Re: Commons bsf
Posted by aisen faith marrero <fa...@gmail.com>.
Hey
On Wed, Feb 1, 2023 at 1:32 PM robertlazarski <ro...@gmail.com>
wrote:
> On Wed, Feb 1, 2023 at 2:27 AM Rony G. Flatscher (Apache) <rony@apache.org
> >
> wrote:
>
> > On 01.02.2023 09:49, sebb wrote:
> > > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree <al...@apache.org> wrote:
> > >> No problem. There was some activity on github.
> > > Please note: That does not mean the component is being developed.
> > > Dependabot runs on most components, and that generates traffic.
> > > Also there may need to be changes to asf.yaml which affect all
> > > components on github.
> > > Etc. This is no indication that the component is being actively
> > > maintained, as such changes need very little (if any) knowledge of the
> > > component.
> >
> > Well, I have been interesting in keeping BSF up and going.
> >
> > >> I ran the owasp dependency
> > >> check thing against it and found a few issues, attempted to update
> some
> > of
> > >> the dependencies (jython) and hit a bit of a snag. I'm not entirely
> sure
> > >> where to go from here. I'm not sure if anyone else has attempted this
> or
> > >> not.
> > > Note that the component has a separate 3.x version, which is based on
> > > JSR-223 - see https://commons.apache.org/proper/commons-bsf/
> > >
> > > I’m not entirely sure that either are still needed.
> >
> > BSF 3.0, the open-source implementation JSR-223 (package javax.script)
> may
> > not be needed anymore
> > with OpenJDK containing it.
> >
> >
> My 2 cents as someone who spent the last decade at my day job on a JSR-223
> implementation for running JavaScript in a Java Class ...
>
> The OpenJDK implementation, Rhino, has performance that is awful. That may
> be fine for smaller scripts. The performance however is a show stopper for
> us as the scripts are enormous.
>
> A couple years ago after using J2V8 - they only support Android now - we
> moved to the Javet project that is Apache licensed.
>
> On a scale of 1/10 I give it a 10. They do an impressive release about once
> a month lately and most importantly they ship with the latest V8 which is
> important for us.
>
> If you need something else besides JS though I have no idea.
>
Re: Commons bsf
Posted by robertlazarski <ro...@gmail.com>.
On Wed, Feb 1, 2023 at 2:27 AM Rony G. Flatscher (Apache) <ro...@apache.org>
wrote:
> On 01.02.2023 09:49, sebb wrote:
> > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree <al...@apache.org> wrote:
> >> No problem. There was some activity on github.
> > Please note: That does not mean the component is being developed.
> > Dependabot runs on most components, and that generates traffic.
> > Also there may need to be changes to asf.yaml which affect all
> > components on github.
> > Etc. This is no indication that the component is being actively
> > maintained, as such changes need very little (if any) knowledge of the
> > component.
>
> Well, I have been interesting in keeping BSF up and going.
>
> >> I ran the owasp dependency
> >> check thing against it and found a few issues, attempted to update some
> of
> >> the dependencies (jython) and hit a bit of a snag. I'm not entirely sure
> >> where to go from here. I'm not sure if anyone else has attempted this or
> >> not.
> > Note that the component has a separate 3.x version, which is based on
> > JSR-223 - see https://commons.apache.org/proper/commons-bsf/
> >
> > I’m not entirely sure that either are still needed.
>
> BSF 3.0, the open-source implementation JSR-223 (package javax.script) may
> not be needed anymore
> with OpenJDK containing it.
>
>
My 2 cents as someone who spent the last decade at my day job on a JSR-223
implementation for running JavaScript in a Java Class ...
The OpenJDK implementation, Rhino, has performance that is awful. That may
be fine for smaller scripts. The performance however is a show stopper for
us as the scripts are enormous.
A couple years ago after using J2V8 - they only support Android now - we
moved to the Javet project that is Apache licensed.
On a scale of 1/10 I give it a 10. They do an impressive release about once
a month lately and most importantly they ship with the latest V8 which is
important for us.
If you need something else besides JS though I have no idea.
Re: Commons bsf
Posted by aisen faith marrero <fa...@gmail.com>.
Watch our YouTube videos about Innovation.
On Wed, Feb 1, 2023 at 12:27 PM Rony G. Flatscher (Apache) <ro...@apache.org>
wrote:
> On 01.02.2023 09:49, sebb wrote:
> > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree <al...@apache.org> wrote:
> >> No problem. There was some activity on github.
> > Please note: That does not mean the component is being developed.
> > Dependabot runs on most components, and that generates traffic.
> > Also there may need to be changes to asf.yaml which affect all
> > components on github.
> > Etc. This is no indication that the component is being actively
> > maintained, as such changes need very little (if any) knowledge of the
> > component.
>
> Well, I have been interesting in keeping BSF up and going.
>
> >> I ran the owasp dependency
> >> check thing against it and found a few issues, attempted to update some
> of
> >> the dependencies (jython) and hit a bit of a snag. I'm not entirely sure
> >> where to go from here. I'm not sure if anyone else has attempted this or
> >> not.
> > Note that the component has a separate 3.x version, which is based on
> > JSR-223 - see https://commons.apache.org/proper/commons-bsf/
> >
> > I’m not entirely sure that either are still needed.
>
> BSF 3.0, the open-source implementation JSR-223 (package javax.script) may
> not be needed anymore
> with OpenJDK containing it.
>
> >> On Tue, Jan 31, 2023 at 6:34 PM Gary Gregory <ga...@gmail.com>
> wrote:
> >>
> >>> This is an open source project, so support is as best as us volunteers
> see
> >>> fit or have itches to scratch ;-)
> >>>
> >>> In this case the lack of activity might show that the original authors
> >>> could have abandoned the component. Let's see how else pipes in.
> At least one project (BSF4ooRexx, e.g. <
> https://sourceforge.net/projects/bsf4oorexx/files/beta/>)
> has been actively using it.
> >>> On Tue, Jan 31, 2023, 17:21 Alex O'Ree <al...@apache.org> wrote:
> >>>
> >>>> Is the bsf library still supported? Looks like the website hasn't been
> >>>> published since 2011.
>
> This is mostly a question of free time on one's hands. E.g. for the
> BSF4ooRexx project I have a few
> little changes applied to BSF which I have always been meaning to
> incorporate.
>
> Alex, your initiative w.r.t. jython and the website are highly welcome!
>
> ---rony
>
> P.S.: Will try to assess the differences between the official BSF and the
> one in BSF4ooRexx in the
> next weeks (time permitting) and then adding the few enhancements with
> JIRA tickets for tracking.
> One thing that will take me some time is re-orienting myself to
> <https://github.com/apache/commons-bsf> and learn about becoming able to
> commit there (not sure
> where I would have to register/report my github id such that it can be
> associated with my ASF id).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>
Ad git-related information (Re: Commons bsf
Posted by "Rony G. Flatscher (Apache)" <ro...@apache.org>.
Bonjour Gilles,
On 01.02.2023 13:53, Gilles Sadowski wrote:
> Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
> <ro...@apache.org> a écrit :
>> [...]
>> One thing that will take me some time is re-orienting myself to
>> <https://github.com/apache/commons-bsf> and learn about becoming able to commit there
> Why "there", when you can commit directly here (at ASF "Commons")?
>
>> (not sure
>> where I would have to register/report my github id such that it can be associated with my ASF id).
> https://whimsy.apache.org/roster/committer/__self__
thank you very much!
Also to get up and running with Apache git:
* Apache git primer: https://infra.apache.org/git-primer.html
* Apache git repositories: https://gitbox.apache.org/repos/asf
* Apache self-service platform: https://selfserve.apache.org/
Best regards
---rony
Re: Commons bsf
Posted by aisen faith marrero <fa...@gmail.com>.
Hi there! Welcome to CM-Team. We’ll get back to you as soon as possible
On Wed, Feb 1, 2023 at 1:34 PM Gilles Sadowski <gi...@gmail.com> wrote:
> Le mer. 1 févr. 2023 à 14:21, Alex O'Ree <al...@apache.org> a écrit :
> >
> > I'm not sure I have commit permissions to that repo. It would be rather
> > rude of me to just commit to a project I've never supported before. IMO
>
> Actually, I was replying to Rony Flatscher, who had asked (AFAICT from
> the email message) and who is a member of the "Commons" PMC.
>
> Any ASF committer can obtain write access to "Commons" repositories;
> just ask Gary (PMC Chair).
>
> Regards,
> Gilles
>
> >
> > On Wed, Feb 1, 2023, 7:58 AM Gilles Sadowski <gi...@gmail.com>
> wrote:
> >
> > > Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
> > > <ro...@apache.org> a écrit :
> > > >
> > > > [...]
> > > > One thing that will take me some time is re-orienting myself to
> > > > <https://github.com/apache/commons-bsf> and learn about becoming
> able
> > > to commit there
> > >
> > > Why "there", when you can commit directly here (at ASF "Commons")?
> > >
> > > > (not sure
> > > > where I would have to register/report my github id such that it can
> be
> > > associated with my ASF id).
> > >
> > > https://whimsy.apache.org/roster/committer/__self__
> > >
> > > HTH,
> > > Gilles
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>
Re: Commons bsf
Posted by Gilles Sadowski <gi...@gmail.com>.
Le mer. 1 févr. 2023 à 14:21, Alex O'Ree <al...@apache.org> a écrit :
>
> I'm not sure I have commit permissions to that repo. It would be rather
> rude of me to just commit to a project I've never supported before. IMO
Actually, I was replying to Rony Flatscher, who had asked (AFAICT from
the email message) and who is a member of the "Commons" PMC.
Any ASF committer can obtain write access to "Commons" repositories;
just ask Gary (PMC Chair).
Regards,
Gilles
>
> On Wed, Feb 1, 2023, 7:58 AM Gilles Sadowski <gi...@gmail.com> wrote:
>
> > Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
> > <ro...@apache.org> a écrit :
> > >
> > > [...]
> > > One thing that will take me some time is re-orienting myself to
> > > <https://github.com/apache/commons-bsf> and learn about becoming able
> > to commit there
> >
> > Why "there", when you can commit directly here (at ASF "Commons")?
> >
> > > (not sure
> > > where I would have to register/report my github id such that it can be
> > associated with my ASF id).
> >
> > https://whimsy.apache.org/roster/committer/__self__
> >
> > HTH,
> > Gilles
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: Commons bsf
Posted by Shawn Heisey <ap...@elyograg.org>.
On 2/1/23 06:20, Alex O'Ree wrote:
> I'm not sure I have commit permissions to that repo. It would be rather
> rude of me to just commit to a project I've never supported before. IMO
All Apache committers are able to commit on the commons projects. There
was an announcement a while back on that. Was a little surprised to see
that access granted. I haven't made any commits there myself.
It would be a good idea to discuss any changes you are thinking of
making on the dev list for commons to make sure they don't object to
your plan. Or maybe they can help you come up with a better approach.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: Commons bsf
Posted by aisen faith marrero <fa...@gmail.com>.
Join us on 2023
On Wed, Feb 1, 2023 at 1:21 PM Alex O'Ree <al...@apache.org> wrote:
> I'm not sure I have commit permissions to that repo. It would be rather
> rude of me to just commit to a project I've never supported before. IMO
>
> On Wed, Feb 1, 2023, 7:58 AM Gilles Sadowski <gi...@gmail.com> wrote:
>
> > Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
> > <ro...@apache.org> a écrit :
> > >
> > > [...]
> > > One thing that will take me some time is re-orienting myself to
> > > <https://github.com/apache/commons-bsf> and learn about becoming able
> > to commit there
> >
> > Why "there", when you can commit directly here (at ASF "Commons")?
> >
> > > (not sure
> > > where I would have to register/report my github id such that it can be
> > associated with my ASF id).
> >
> > https://whimsy.apache.org/roster/committer/__self__
> >
> > HTH,
> > Gilles
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> > For additional commands, e-mail: user-help@commons.apache.org
> >
> >
>
Re: Commons bsf
Posted by Alex O'Ree <al...@apache.org>.
I'm not sure I have commit permissions to that repo. It would be rather
rude of me to just commit to a project I've never supported before. IMO
On Wed, Feb 1, 2023, 7:58 AM Gilles Sadowski <gi...@gmail.com> wrote:
> Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
> <ro...@apache.org> a écrit :
> >
> > [...]
> > One thing that will take me some time is re-orienting myself to
> > <https://github.com/apache/commons-bsf> and learn about becoming able
> to commit there
>
> Why "there", when you can commit directly here (at ASF "Commons")?
>
> > (not sure
> > where I would have to register/report my github id such that it can be
> associated with my ASF id).
>
> https://whimsy.apache.org/roster/committer/__self__
>
> HTH,
> Gilles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>
Re: Commons bsf
Posted by aisen faith marrero <fa...@gmail.com>.
Hello! Good to see you.
On Wed, Feb 1, 2023 at 12:58 PM Gilles Sadowski <gi...@gmail.com>
wrote:
> Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
> <ro...@apache.org> a écrit :
> >
> > [...]
> > One thing that will take me some time is re-orienting myself to
> > <https://github.com/apache/commons-bsf> and learn about becoming able
> to commit there
>
> Why "there", when you can commit directly here (at ASF "Commons")?
>
> > (not sure
> > where I would have to register/report my github id such that it can be
> associated with my ASF id).
>
> https://whimsy.apache.org/roster/committer/__self__
>
> HTH,
> Gilles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>
Re: Commons bsf
Posted by Gilles Sadowski <gi...@gmail.com>.
Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
<ro...@apache.org> a écrit :
>
> [...]
> One thing that will take me some time is re-orienting myself to
> <https://github.com/apache/commons-bsf> and learn about becoming able to commit there
Why "there", when you can commit directly here (at ASF "Commons")?
> (not sure
> where I would have to register/report my github id such that it can be associated with my ASF id).
https://whimsy.apache.org/roster/committer/__self__
HTH,
Gilles
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: Commons bsf
Posted by aisen faith marrero <fa...@gmail.com>.
Have a great day! lia
On Wed, Feb 1, 2023 at 1:01 PM Alex O'Ree <al...@apache.org> wrote:
> Hmm if it's no longer needed, maybe consider a vote to move it to the attic
>
> On Wed, Feb 1, 2023, 7:27 AM Rony G. Flatscher (Apache) <ro...@apache.org>
> wrote:
>
> > On 01.02.2023 09:49, sebb wrote:
> > > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree <al...@apache.org> wrote:
> > >> No problem. There was some activity on github.
> > > Please note: That does not mean the component is being developed.
> > > Dependabot runs on most components, and that generates traffic.
> > > Also there may need to be changes to asf.yaml which affect all
> > > components on github.
> > > Etc. This is no indication that the component is being actively
> > > maintained, as such changes need very little (if any) knowledge of the
> > > component.
> >
> > Well, I have been interesting in keeping BSF up and going.
> >
> > >> I ran the owasp dependency
> > >> check thing against it and found a few issues, attempted to update
> some
> > of
> > >> the dependencies (jython) and hit a bit of a snag. I'm not entirely
> sure
> > >> where to go from here. I'm not sure if anyone else has attempted this
> or
> > >> not.
> > > Note that the component has a separate 3.x version, which is based on
> > > JSR-223 - see https://commons.apache.org/proper/commons-bsf/
> > >
> > > I’m not entirely sure that either are still needed.
> >
> > BSF 3.0, the open-source implementation JSR-223 (package javax.script)
> may
> > not be needed anymore
> > with OpenJDK containing it.
> >
> > >> On Tue, Jan 31, 2023 at 6:34 PM Gary Gregory <ga...@gmail.com>
> > wrote:
> > >>
> > >>> This is an open source project, so support is as best as us
> volunteers
> > see
> > >>> fit or have itches to scratch ;-)
> > >>>
> > >>> In this case the lack of activity might show that the original
> authors
> > >>> could have abandoned the component. Let's see how else pipes in.
> > At least one project (BSF4ooRexx, e.g. <
> > https://sourceforge.net/projects/bsf4oorexx/files/beta/>)
> > has been actively using it.
> > >>> On Tue, Jan 31, 2023, 17:21 Alex O'Ree <al...@apache.org> wrote:
> > >>>
> > >>>> Is the bsf library still supported? Looks like the website hasn't
> been
> > >>>> published since 2011.
> >
> > This is mostly a question of free time on one's hands. E.g. for the
> > BSF4ooRexx project I have a few
> > little changes applied to BSF which I have always been meaning to
> > incorporate.
> >
> > Alex, your initiative w.r.t. jython and the website are highly welcome!
> >
> > ---rony
> >
> > P.S.: Will try to assess the differences between the official BSF and the
> > one in BSF4ooRexx in the
> > next weeks (time permitting) and then adding the few enhancements with
> > JIRA tickets for tracking.
> > One thing that will take me some time is re-orienting myself to
> > <https://github.com/apache/commons-bsf> and learn about becoming able to
> > commit there (not sure
> > where I would have to register/report my github id such that it can be
> > associated with my ASF id).
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> > For additional commands, e-mail: user-help@commons.apache.org
> >
> >
>
Re: Commons bsf
Posted by Alex O'Ree <al...@apache.org>.
Hmm if it's no longer needed, maybe consider a vote to move it to the attic
On Wed, Feb 1, 2023, 7:27 AM Rony G. Flatscher (Apache) <ro...@apache.org>
wrote:
> On 01.02.2023 09:49, sebb wrote:
> > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree <al...@apache.org> wrote:
> >> No problem. There was some activity on github.
> > Please note: That does not mean the component is being developed.
> > Dependabot runs on most components, and that generates traffic.
> > Also there may need to be changes to asf.yaml which affect all
> > components on github.
> > Etc. This is no indication that the component is being actively
> > maintained, as such changes need very little (if any) knowledge of the
> > component.
>
> Well, I have been interesting in keeping BSF up and going.
>
> >> I ran the owasp dependency
> >> check thing against it and found a few issues, attempted to update some
> of
> >> the dependencies (jython) and hit a bit of a snag. I'm not entirely sure
> >> where to go from here. I'm not sure if anyone else has attempted this or
> >> not.
> > Note that the component has a separate 3.x version, which is based on
> > JSR-223 - see https://commons.apache.org/proper/commons-bsf/
> >
> > I’m not entirely sure that either are still needed.
>
> BSF 3.0, the open-source implementation JSR-223 (package javax.script) may
> not be needed anymore
> with OpenJDK containing it.
>
> >> On Tue, Jan 31, 2023 at 6:34 PM Gary Gregory <ga...@gmail.com>
> wrote:
> >>
> >>> This is an open source project, so support is as best as us volunteers
> see
> >>> fit or have itches to scratch ;-)
> >>>
> >>> In this case the lack of activity might show that the original authors
> >>> could have abandoned the component. Let's see how else pipes in.
> At least one project (BSF4ooRexx, e.g. <
> https://sourceforge.net/projects/bsf4oorexx/files/beta/>)
> has been actively using it.
> >>> On Tue, Jan 31, 2023, 17:21 Alex O'Ree <al...@apache.org> wrote:
> >>>
> >>>> Is the bsf library still supported? Looks like the website hasn't been
> >>>> published since 2011.
>
> This is mostly a question of free time on one's hands. E.g. for the
> BSF4ooRexx project I have a few
> little changes applied to BSF which I have always been meaning to
> incorporate.
>
> Alex, your initiative w.r.t. jython and the website are highly welcome!
>
> ---rony
>
> P.S.: Will try to assess the differences between the official BSF and the
> one in BSF4ooRexx in the
> next weeks (time permitting) and then adding the few enhancements with
> JIRA tickets for tracking.
> One thing that will take me some time is re-orienting myself to
> <https://github.com/apache/commons-bsf> and learn about becoming able to
> commit there (not sure
> where I would have to register/report my github id such that it can be
> associated with my ASF id).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>
Re: Commons bsf
Posted by "Rony G. Flatscher (Apache)" <ro...@apache.org>.
On 01.02.2023 09:49, sebb wrote:
> On Wed, 1 Feb 2023 at 00:22, Alex O'Ree <al...@apache.org> wrote:
>> No problem. There was some activity on github.
> Please note: That does not mean the component is being developed.
> Dependabot runs on most components, and that generates traffic.
> Also there may need to be changes to asf.yaml which affect all
> components on github.
> Etc. This is no indication that the component is being actively
> maintained, as such changes need very little (if any) knowledge of the
> component.
Well, I have been interesting in keeping BSF up and going.
>> I ran the owasp dependency
>> check thing against it and found a few issues, attempted to update some of
>> the dependencies (jython) and hit a bit of a snag. I'm not entirely sure
>> where to go from here. I'm not sure if anyone else has attempted this or
>> not.
> Note that the component has a separate 3.x version, which is based on
> JSR-223 - see https://commons.apache.org/proper/commons-bsf/
>
> I’m not entirely sure that either are still needed.
BSF 3.0, the open-source implementation JSR-223 (package javax.script) may not be needed anymore
with OpenJDK containing it.
>> On Tue, Jan 31, 2023 at 6:34 PM Gary Gregory <ga...@gmail.com> wrote:
>>
>>> This is an open source project, so support is as best as us volunteers see
>>> fit or have itches to scratch ;-)
>>>
>>> In this case the lack of activity might show that the original authors
>>> could have abandoned the component. Let's see how else pipes in.
At least one project (BSF4ooRexx, e.g. <https://sourceforge.net/projects/bsf4oorexx/files/beta/>)
has been actively using it.
>>> On Tue, Jan 31, 2023, 17:21 Alex O'Ree <al...@apache.org> wrote:
>>>
>>>> Is the bsf library still supported? Looks like the website hasn't been
>>>> published since 2011.
This is mostly a question of free time on one's hands. E.g. for the BSF4ooRexx project I have a few
little changes applied to BSF which I have always been meaning to incorporate.
Alex, your initiative w.r.t. jython and the website are highly welcome!
---rony
P.S.: Will try to assess the differences between the official BSF and the one in BSF4ooRexx in the
next weeks (time permitting) and then adding the few enhancements with JIRA tickets for tracking.
One thing that will take me some time is re-orienting myself to
<https://github.com/apache/commons-bsf> and learn about becoming able to commit there (not sure
where I would have to register/report my github id such that it can be associated with my ASF id).
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: Commons bsf
Posted by sebb <se...@gmail.com>.
On Wed, 1 Feb 2023 at 00:22, Alex O'Ree <al...@apache.org> wrote:
>
> No problem. There was some activity on github.
Please note: That does not mean the component is being developed.
Dependabot runs on most components, and that generates traffic.
Also there may need to be changes to asf.yaml which affect all
components on github.
Etc. This is no indication that the component is being actively
maintained, as such changes need very little (if any) knowledge of the
component.
> I ran the owasp dependency
> check thing against it and found a few issues, attempted to update some of
> the dependencies (jython) and hit a bit of a snag. I'm not entirely sure
> where to go from here. I'm not sure if anyone else has attempted this or
> not.
Note that the component has a separate 3.x version, which is based on
JSR-223 - see https://commons.apache.org/proper/commons-bsf/
I’m not entirely sure that either are still needed.
> On Tue, Jan 31, 2023 at 6:34 PM Gary Gregory <ga...@gmail.com> wrote:
>
> > This is an open source project, so support is as best as us volunteers see
> > fit or have itches to scratch ;-)
> >
> > In this case the lack of activity might show that the original authors
> > could have abandoned the component. Let's see how else pipes in.
> >
> > Gary
> >
> > On Tue, Jan 31, 2023, 17:21 Alex O'Ree <al...@apache.org> wrote:
> >
> > > Is the bsf library still supported? Looks like the website hasn't been
> > > published since 2011.
> > >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: Commons bsf
Posted by Alex O'Ree <al...@apache.org>.
No problem. There was some activity on github. I ran the owasp dependency
check thing against it and found a few issues, attempted to update some of
the dependencies (jython) and hit a bit of a snag. I'm not entirely sure
where to go from here. I'm not sure if anyone else has attempted this or
not.
On Tue, Jan 31, 2023 at 6:34 PM Gary Gregory <ga...@gmail.com> wrote:
> This is an open source project, so support is as best as us volunteers see
> fit or have itches to scratch ;-)
>
> In this case the lack of activity might show that the original authors
> could have abandoned the component. Let's see how else pipes in.
>
> Gary
>
> On Tue, Jan 31, 2023, 17:21 Alex O'Ree <al...@apache.org> wrote:
>
> > Is the bsf library still supported? Looks like the website hasn't been
> > published since 2011.
> >
>
Re: Commons bsf
Posted by Gary Gregory <ga...@gmail.com>.
This is an open source project, so support is as best as us volunteers see
fit or have itches to scratch ;-)
In this case the lack of activity might show that the original authors
could have abandoned the component. Let's see how else pipes in.
Gary
On Tue, Jan 31, 2023, 17:21 Alex O'Ree <al...@apache.org> wrote:
> Is the bsf library still supported? Looks like the website hasn't been
> published since 2011.
>