Re: jexl upgrade path from 1.x

[Alex O'Ree]

Perhaps I wasn't clear. Let's pretend I'm a user of jexl 1.x looking to
upgrade to a newer version. Is there any documentation for migrating to a
newer version?

On Tue, Jan 31, 2023 at 8:56 PM Gilles Sadowski 
wrote:

> Hi.
>
> Le mer. 1 févr. 2023 à 02:37, Alex O'Ree  a écrit :
> >
> > Hi i'm doing some maintenance work on the bsf library
>
> Please move the discussion to the "dev" mailing list.
>
> > which currently
> > depends on a jexl 1.x. There's a few imports that aren't exactly
> resolving.
> >
> > import org.apache.commons.jexl.JexlContext;
> > moved to import org.apache.commons.jexl3.JexlContext;
> >
> > import org.apache.commons.jexl.JexlHelper;
> > unknown what happened to this but seems to have been removed in 2.x
> >
> > import org.apache.commons.jexl.Script;
> > i think moved to import org.apache.commons.jexl3.JexlScriptScript;
> >
> > import org.apache.commons.jexl.ScriptFactory;
> > not sure what this maps to in the current code base
> >
> > I found some notes in the release notes about a jexl-comat library but
> > couldn't find it published anywhere. I also poked around the website
> > looking for some kind of migration guide.
> >
> > Any pointers to how i can update this code base?
>
> I'd be wary to release a new version of this component, using a
> dependency that is more than 10 years old.
> IMHO, the way to go is to depend on the lastest (i.e. supported)
> version of JEXL.
>
> Please post specific questions about upgrading the BSF codebase
> using a "Subject:" line with the "[BSF]" prefix (on "dev@").[1]
>
> Thanks,
> Gilles
>
> [1] There are dozens of components, sharing the same ML.
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>

Re: Commons bsf

[Shawn Heisey]

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-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: Commons bsf

[aisen faith marrero]

Watch our YouTube videos about Innovation.

On Wed, Feb 1, 2023 at 12:27 PM Rony G. Flatscher (Apache) 
wrote:

> On 01.02.2023 09:49, sebb wrote:
> > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree  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 
> 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  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
>  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-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>

Re: Commons bsf

[aisen faith marrero]

Hello! Good to see you.

On Wed, Feb 1, 2023 at 12:58 PM Gilles Sadowski 
wrote:

> Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
>  a écrit :
> >
> > [...]
> > One thing that will take me some time is re-orienting myself to
> >  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-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>

Re: Commons bsf

[aisen faith marrero]

Have a great day! lia

On Wed, Feb 1, 2023 at 1:01 PM Alex O'Ree  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) 
> wrote:
>
> > On 01.02.2023 09:49, sebb wrote:
> > > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree  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 
> > 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  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
> >  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-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org
> >
> >
>

Re: Commons bsf

[aisen faith marrero]

Join us on 2023

On Wed, Feb 1, 2023 at 1:21 PM 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
>
> On Wed, Feb 1, 2023, 7:58 AM Gilles Sadowski  wrote:
>
> > Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
> >  a écrit :
> > >
> > > [...]
> > > One thing that will take me some time is re-orienting myself to
> > >  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-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org
> >
> >
>

Re: Commons bsf

[aisen faith marrero]

Hey

On Wed, Feb 1, 2023 at 1:32 PM robertlazarski 
wrote:

> On Wed, Feb 1, 2023 at 2:27 AM Rony G. Flatscher (Apache)  >
> wrote:
>
> > On 01.02.2023 09:49, sebb wrote:
> > > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree  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

[aisen faith marrero]

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  wrote:

> Le mer. 1 févr. 2023 à 14:21, Alex O'Ree  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 
> wrote:
> >
> > > Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
> > >  a écrit :
> > > >
> > > > [...]
> > > > One thing that will take me some time is re-orienting myself to
> > > >  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-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>

Re: Commons bsf

[aisen faith marrero]

Thank you for your application for the role of senior data.

On Wed, Feb 1, 2023 at 1:43 PM robertlazarski 
wrote:

> On Wed, Feb 1, 2023 at 3:32 AM robertlazarski 
> 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

[robertlazarski]

On Wed, Feb 1, 2023 at 3:32 AM robertlazarski 
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

[Gilles Sadowski]

Le mer. 1 févr. 2023 à 14:21, Alex O'Ree  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  wrote:
>
> > Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
> >  a écrit :
> > >
> > > [...]
> > > One thing that will take me some time is re-orienting myself to
> > >  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-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: Commons bsf

[robertlazarski]

On Wed, Feb 1, 2023 at 2:27 AM Rony G. Flatscher (Apache) 
wrote:

> On 01.02.2023 09:49, sebb wrote:
> > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree  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

[Alex O'Ree]

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  wrote:

> Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
>  a écrit :
> >
> > [...]
> > One thing that will take me some time is re-orienting myself to
> >  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-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>

Re: Commons bsf

[Alex O'Ree]

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) 
wrote:

> On 01.02.2023 09:49, sebb wrote:
> > On Wed, 1 Feb 2023 at 00:22, Alex O'Ree  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 
> 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  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
>  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-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>

Re: Commons bsf

[Gilles Sadowski]

Le mer. 1 févr. 2023 à 13:27, Rony G. Flatscher (Apache)
 a écrit :
>
> [...]
> One thing that will take me some time is re-orienting myself to
>  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-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: Commons bsf

[Rony G. Flatscher (Apache)]

On 01.02.2023 09:49, sebb wrote:

On Wed, 1 Feb 2023 at 00:22, Alex O'Ree  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  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. ) 
has been actively using it.

On Tue, Jan 31, 2023, 17:21 Alex O'Ree  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 
 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-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: Commons bsf

[sebb]

On Wed, 1 Feb 2023 at 00:22, Alex O'Ree  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  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  wrote:
> >
> > > Is the bsf library still supported? Looks like the website hasn't been
> > > published since 2011.
> > >
> >

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org