t jupiter, getting
> repo's in sync.
Thank you for this pointer. I missed these postings because I was filtering the
subject for "bsf" to
catch any communication about Apache BSF. Background is, that I use Apache BSF
for a Java bridge [1]
from/to ooRexx [2] over the course of twe
t; WRT Java 6, I would say forget it from my POV and interest. I am trying to
> move all components to Java 8, which is the oldest Java LTS release.
>
> Remember that no one will force an app onto a new version, it's up to the
> app.
>
> It's not clear to me if we h
, which is the oldest Java LTS release.
Remember that no one will force an app onto a new version, it's up to the
app.
It's not clear to me if we have even interest for a BSF release. It looks
like the last functional commit was from 2014, not a great sign...
Any thoughts folks?
Gary
On T
Just noticed that there was some activity on GitHub related to BSF (e.g.
<https://github.com/apache/commons-bsf/pull/1> (updating to JUnit 4.13.1),
<https://github.com/apache/commons-bsf/pull/2> (dependabot), and the like), but
I cannot find any
discussions about it in dev@common
Hi Rony,
Thanks for that!
Rgds,Rory
On 20/06/2015 17:27, Rony G. Flatscher (Apache) wrote:
Hi Rory,
just ran "jdeps -jdkinternals" on both, BSF 2.4.0 and BSF 3.1, both have no
internal dependencies.
Best regards,
---rony
On 15.06.2015 14:19, Rony G. Flatscher (Apache)
Hi Rory,
just ran "jdeps -jdkinternals" on both, BSF 2.4.0 and BSF 3.1, both have no
internal dependencies.
Best regards,
---rony
On 15.06.2015 14:19, Rony G. Flatscher (Apache) wrote:
> On 15.06.2015 10:04, Rory O'Donnell wrote:
>> Hi Benedict,
>>
>&g
So I think, we are clean here.
Regards
Oliver
Am 15.06.2015 um 10:04 schrieb Rory O'Donnell:
Hi Benedict,
I'm contacting you in relation to Apache Commons Configuration & Bean
Scripting Framework (BSF), both projects seems to be very popular
dependencies for other open sou
gt;
> Hi Benedict,
>
> I'm contacting you in relation to Apache Commons Configuration & Bean
> Scripting Framework (BSF), both projects seems to be very popular
> dependencies for other open source projects.
>
> As part of the preparations for JDK 9, Oracle’s engineers
Thanks Oliver, looking forward to hearing from you.
Rgds,Rory
On 17/06/2015 20:52, Oliver Heger wrote:
Hi Rory,
Am 15.06.2015 um 10:04 schrieb Rory O'Donnell:
Hi Benedict,
I'm contacting you in relation to Apache Commons Configuration & Bean
Scripting Framework (BSF), both
Hi Rory,
Am 15.06.2015 um 10:04 schrieb Rory O'Donnell:
>
> Hi Benedict,
>
> I'm contacting you in relation to Apache Commons Configuration & Bean
> Scripting Framework (BSF), both projects seems to be very popular
> dependencies for other open sour
On 15.06.2015 10:04, Rory O'Donnell wrote:
>
> Hi Benedict,
>
> I'm contacting you in relation to Apache Commons Configuration & Bean
> Scripting Framework (BSF),
> both projects seems to be very popular dependencies for other open source
> projects.
>
&
Hi Benedict,
I'm contacting you in relation to Apache Commons Configuration & Bean
Scripting Framework (BSF), both projects seems to be very popular
dependencies for other open source projects.
As part of the preparations for JDK 9, Oracle’s engineers have been
analyzing op
On 23 March 2013 00:25, sebb wrote:
> On 23 March 2013 00:19, Jörg Schaible wrote:
>> sebb wrote:
>>
>>> On 22 March 2013 19:58, Gary Gregory wrote:
I published the CSV site after your commit, but some links are still
incorrect, for example:
https://commons.apache.org/proper/relea
hor: sebb
>>>> Date: Fri Mar 22 17:49:27 2013
>>>> New Revision: 1459912
>>>>
>>>> URL: http://svn.apache.org/r1459912
>>>> Log:
>>>> Fix up URLs so they point to actual sites; this allows relative URLs to
>>>> work pr
t;>> work properly
>>>
>>> Modified:
>>> commons/proper/bcel/trunk/pom.xml
>>> commons/proper/beanutils/trunk/pom.xml
>>> commons/proper/betwixt/trunk/pom.xml
>>> commons/proper/bsf/trunk/pom.xml
>>> commons/p
l sites; this allows relative URLs to
>> work properly
>>
>> Modified:
>> commons/proper/bcel/trunk/pom.xml
>> commons/proper/beanutils/trunk/pom.xml
>> commons/proper/betwixt/trunk/pom.xml
>> commons/proper/bsf/trunk/pom.xml
>> commons/proper
l
> commons/proper/betwixt/trunk/pom.xml
> commons/proper/bsf/trunk/pom.xml
> commons/proper/chain/trunk/pom.xml
> commons/proper/cli/trunk/pom.xml
> commons/proper/codec/trunk/pom.xml
> commons/proper/collections/trunk/pom.xml
> commons/proper/compre
On 13.06.2012 19:19, sebb wrote:
> On 13 June 2012 17:01, Joseph Kesselman wrote:
>> Just a quick note/quibble re BSF's history:
>>
>> I, Joe Kesselman (the same IBMer who contributed some code to Xerces and
>> quite a lot to Xalan) did a lot of the early prototy
I am sensing that he would like the "history" item at
http://commons.apache.org/bsf/faq.html updated to include him.
Ralph
On Jun 13, 2012, at 10:19 AM, sebb wrote:
> On 13 June 2012 17:01, Joseph Kesselman wrote:
>> Just a quick note/quibble re BSF's history:
>
On 13 June 2012 17:01, Joseph Kesselman wrote:
> Just a quick note/quibble re BSF's history:
>
> I, Joe Kesselman (the same IBMer who contributed some code to Xerces and
> quite a lot to Xalan) did a lot of the early prototyping work on BSF. The
> concept and initial
Just a quick note/quibble re BSF's history:
I, Joe Kesselman (the same IBMer who contributed some code to Xerces and
quite a lot to Xalan) did a lot of the early prototyping work on BSF.
The concept and initial sketch was certainly Sanjiva's, as part of some
other bean compositi
wvc?rev=1301865&view=rev
> Log:
> Updating copyright dates in notice per expressive last entries in each
> components svn log
>
> Modified:
>commons/proper/bcel/trunk/NOTICE.txt
>commons/proper/beanutils/trunk/NOTICE.txt
>commons/proper/betwixt/trunk/NOTICE.t
Jira notifications for BSF were being sent to the Jakarta list:
notificati...@jakarta.apache.org
I think I've now changed BSF Jira so the notifications will go to the
normal Commons list for Jira mails:
iss...@commons.apache.o
es to the old location, in case there are
other download pages / links lurking somewhere...
> Hen
>
> On Fri, Nov 11, 2011 at 4:08 PM, sebb wrote:
>> At present, BSF, BCEL and JCS downloads still use /dist/jakarta/.
>>
>> I've just started the process of moving JMet
At present, BSF, BCEL and JCS downloads still use /dist/jakarta/.
I've just started the process of moving JMeter files to the new JMeter
TLP, so I thought I might as well do the same for the remaining
Jakarta downloads.
This is what I propose for the Commons moves:
- copy (cp -p) archives,
On Sun, Sep 11, 2011 at 10:39 AM, sebb wrote:
> On 11 September 2011 18:14, Henri Yandell wrote:
>> On Sun, Sep 11, 2011 at 6:28 AM, sebb wrote:
>>> On 11 September 2011 11:45, sebb wrote:
>>>> On 11 September 2011 07:35, Henri Yandell wrote:
>
On 11 September 2011 18:14, Henri Yandell wrote:
> On Sun, Sep 11, 2011 at 6:28 AM, sebb wrote:
>> On 11 September 2011 11:45, sebb wrote:
>>> On 11 September 2011 07:35, Henri Yandell wrote:
>>>> The site for BSF is still on jakarta.apache.org. Is someone wor
On Sun, Sep 11, 2011 at 6:28 AM, sebb wrote:
> On 11 September 2011 11:45, sebb wrote:
>> On 11 September 2011 07:35, Henri Yandell wrote:
>>> The site for BSF is still on jakarta.apache.org. Is someone working on
>>> moving it over to Commons?
>>
>> I c
BSF taglibs is in the attic [0], with SVN here [1]
However, there's a taglibs folder [2] under BSF which appears to be a
later version of BSF taglibs.
I assume this is also retired?
If so, maybe the folder should be moved elsewhere in SVN?
[0] http://attic.apache.org/projects/ja
On 11 September 2011 11:45, sebb wrote:
> On 11 September 2011 07:35, Henri Yandell wrote:
>> The site for BSF is still on jakarta.apache.org. Is someone working on
>> moving it over to Commons?
>
> I can take care of that.
Done; however the FAQ page needs a bit of rework
On 11 September 2011 07:35, Henri Yandell wrote:
> The site for BSF is still on jakarta.apache.org. Is someone working on
> moving it over to Commons?
I can take care of that.
> Hen
>
> -
> To unsubscribe, e-
The site for BSF is still on jakarta.apache.org. Is someone working on
moving it over to Commons?
Hen
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
the vote duly passes.
Thanks to all who voted.
On 17 August 2011 00:20, sebb wrote:
> On 13 August 2011 01:13, sebb wrote:
>> BSF [1] needs to move out of Jakarta.
>>
>> It's not really big enough to warrant its own TLP.
>>
>> IMO Commons would be a good
On 13 August 2011 01:13, sebb wrote:
> BSF [1] needs to move out of Jakarta.
>
> It's not really big enough to warrant its own TLP.
>
> IMO Commons would be a good alternative home for BSF.
>
> Can we please vote to:
>
> 1. Accept BSF as a Commons Component
&
+1
On Fri, Aug 12, 2011 at 11:55 PM, Henri Yandell wrote:
> +1.
>
> On Fri, Aug 12, 2011 at 5:28 PM, Matt Benson wrote:
>> +1 for both sub-votes.
>>
>> Matt
>>
>> On Fri, Aug 12, 2011 at 7:13 PM, sebb wrote:
>>> BSF [1] needs to move out o
+1
Oliver
Am 13.08.2011 02:13, schrieb sebb:
BSF [1] needs to move out of Jakarta.
It's not really big enough to warrant its own TLP.
IMO Commons would be a good alternative home for BSF.
Can we please vote to:
1. Accept BSF as a Commons Component
2. Offer Commons karma to BSF devel
+1
Gary
On Aug 12, 2011, at 20:14, "sebb" wrote:
> BSF [1] needs to move out of Jakarta.
>
> It's not really big enough to warrant its own TLP.
>
> IMO Commons would be a good alternative home for BSF.
>
> Can we please vote to:
>
> 1. Accep
+1 for both
welcome to commons!!!
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sat, Aug 13, 2011 at 12:14 PM, Christian Grobmeier
wrote:
> +1 to both votes
>
> On Sat, Aug 13, 2011 at 2:13 AM, sebb wrote:
>> BSF [1] needs to move out of Jakarta.
>&g
+1 to both votes
On Sat, Aug 13, 2011 at 2:13 AM, sebb wrote:
> BSF [1] needs to move out of Jakarta.
>
> It's not really big enough to warrant its own TLP.
>
> IMO Commons would be a good alternative home for BSF.
>
> Can we please vote to:
>
> 1. Accept BSF as
Le 13/08/2011 02:13, sebb a écrit :
BSF [1] needs to move out of Jakarta.
It's not really big enough to warrant its own TLP.
IMO Commons would be a good alternative home for BSF.
Can we please vote to:
1. Accept BSF as a Commons Component
2. Offer Commons karma to BSF developers.
The
On 2011-08-13, sebb wrote:
> 1. Accept BSF as a Commons Component
+1
> 2. Offer Commons karma to BSF developers.
> The ones who made commits since the start of 2008 and are not already
> in Commons are:
> 2a) Rony G. Flatscher (rony)
> 2b) Ant Elder (ant
+1.
On Fri, Aug 12, 2011 at 5:28 PM, Matt Benson wrote:
> +1 for both sub-votes.
>
> Matt
>
> On Fri, Aug 12, 2011 at 7:13 PM, sebb wrote:
>> BSF [1] needs to move out of Jakarta.
>>
>> It's not really big enough to warrant its own TLP.
>>
>> IM
+1 for both sub-votes.
Matt
On Fri, Aug 12, 2011 at 7:13 PM, sebb wrote:
> BSF [1] needs to move out of Jakarta.
>
> It's not really big enough to warrant its own TLP.
>
> IMO Commons would be a good alternative home for BSF.
>
> Can we please vote to:
>
> 1. A
BSF [1] needs to move out of Jakarta.
It's not really big enough to warrant its own TLP.
IMO Commons would be a good alternative home for BSF.
Can we please vote to:
1. Accept BSF as a Commons Component
2. Offer Commons karma to BSF developers.
The ones who made commits since the sta
+1 for me as well,
sounds BSF perfectly fits Apache Commons community :)
All the best,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Aug 10, 2011 at 8:18 PM, Jörg Schaible wrote:
> sebb wrote:
>
>> BSF [1] needs to move out of Jakarta.
>>
>
sebb wrote:
> BSF [1] needs to move out of Jakarta.
>
> It's not really big enough to warrant its own TLP.
>
> It looks like it would be a suitable addition to Commons.
>
> Any objections, or should I start a vote?
>
> [1] ht
OK by me.
Gary
On Wed, Aug 10, 2011 at 10:51 AM, sebb wrote:
> BSF [1] needs to move out of Jakarta.
>
> It's not really big enough to warrant its own TLP.
>
> It looks like it would be a suitable addition to Commons.
>
> Any objections, or should I
BSF [1] needs to move out of Jakarta.
It's not really big enough to warrant its own TLP.
It looks like it would be a suitable addition to Commons.
Any objections, or should I start a vote?
[1] http://jakarta.apache.or
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-bsf has an issue affecting its community integration
2 repos [1, 2].
I remembered a related discussion so I went back to the archives,
there was a vote [3] on the corresponding m2 repo artifacts about a
month back, I will ping the bsf list for status.
-Rahul
[1]
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/bsf/bsf-api/
[2] http:
s message in context:
http://www.nabble.com/-JEXL--2.0-and-BSF---JSR-223-tp24706519p24735171.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
ugh.
> --
> View this message in context:
> http://www.nabble.com/-JEXL--2.0-and-BSF---JSR-223-tp24706519p24734383.html
>
> Sent from the Commons - Dev mailing list archive at Nabble.com.
>
>
> -
&g
nd pass it down to Jexl if we
want to be more faithfull to the jsr-223 API intent in this respect (if this
is what you had in mind a couple of message ago).
--
View this message in context:
http://www.nabble.com/-JEXL--2.0-and-BSF---JSR-223-tp24706519p24734383.html
Sent from the Commons - Dev ma
Ok, thank you both for the explanation.
--
View this message in context:
http://www.nabble.com/-JEXL--2.0-and-BSF---JSR-223-tp24706519p24733769.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
-
To
On Wed, Jul 29, 2009 at 4:58 PM, Henrib wrote:
>
> sebb-2-2 wrote:
>>
>> Of course if you try to use the new classes on Java 1.5 without also
>> providing BSF 3.0 the JVM will complain, but otherwise the Jexl jar
>> will run fine on Java 1.5.
>>
>
> I
On 29/07/2009, Henrib wrote:
>
>
>
> sebb-2-2 wrote:
> >
> > Of course if you try to use the new classes on Java 1.5 without also
> > providing BSF 3.0 the JVM will complain, but otherwise the Jexl jar
> > will run fine on Java 1.5.
> >
>
&g
sebb-2-2 wrote:
>
> Of course if you try to use the new classes on Java 1.5 without also
> providing BSF 3.0 the JVM will complain, but otherwise the Jexl jar
> will run fine on Java 1.5.
>
I'm sorry I don't understand this correctly. Are you saying that that BS
nient.
> May be we can expose what is necessary from Jexl for the jsr-233 to be
> efficiently implemented but still leave it as an option ?
> Cheers
I'm proposing to use BSF 3.0 API which defines the JSR-223 APIs but
runs on Java 1.4+ as a compile-time only dependency.
I've
s an option ?
Cheers
--
View this message in context:
http://www.nabble.com/-JEXL--2.0-and-BSF---JSR-223-tp24706519p24724270.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsu
On Tue, Jul 28, 2009 at 9:21 PM, sebb wrote:
> On 29/07/2009, Rahul Akolkar wrote:
>> On Tue, Jul 28, 2009 at 3:41 PM, sebb wrote:
>> > Although Jexl 2.0 works OK currently with Apache BSF 3.0, it relies on
>> > the factory & engine provided by BSF 3.0.
>>
On 29/07/2009, Rahul Akolkar wrote:
> On Tue, Jul 28, 2009 at 3:41 PM, sebb wrote:
> > Although Jexl 2.0 works OK currently with Apache BSF 3.0, it relies on
> > the factory & engine provided by BSF 3.0.
> >
> > Now Java 1.6 has scripting built-in, so
On Tue, Jul 28, 2009 at 3:41 PM, sebb wrote:
> Although Jexl 2.0 works OK currently with Apache BSF 3.0, it relies on
> the factory & engine provided by BSF 3.0.
>
> Now Java 1.6 has scripting built-in, so I think it would make sense to
> include the necessary classes and pr
Although Jexl 2.0 works OK currently with Apache BSF 3.0, it relies on
the factory & engine provided by BSF 3.0.
Now Java 1.6 has scripting built-in, so I think it would make sense to
include the necessary classes and property file in Jexl. This would
allow it to be used without the BSF jar.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-bsf has an issue affecting its community integration
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-bsf has an issue affecting its community integration.
This
On 11/10/07, sebb <[EMAIL PROTECTED]> wrote:
> Or both:
>
> the classname and extension type(s) should be added to
> Languages.properties (*) in BSF, and the implementation included in
> the JEXL jar.
>
> (*) If BSF allows for scanning additional property files, th
Or both:
the classname and extension type(s) should be added to
Languages.properties (*) in BSF, and the implementation included in
the JEXL jar.
(*) If BSF allows for scanning additional property files, that would
not be essential.
S.
On 10/11/2007, Dion Gillard <[EMAIL PROTECTED]> wrote
So should this go in BSF or Jexl?
On 11/10/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> On 11/10/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > On 11/9/07, sebb <[EMAIL PROTECTED]> wrote:
> > > Are there any plans to add a BSF wrapper to JEXL?
> >
On 11/10/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> On 11/9/07, sebb <[EMAIL PROTECTED]> wrote:
> > Are there any plans to add a BSF wrapper to JEXL?
> >
>
>
> At some point (well over a year ago, before v1.1), I had one for some
> prototyping I was doi
FWIW,
Jexl is a supported scripting language for the JDK 1.6 (was it in 1.5)
scripting engine.
On 11/10/07, sebb <[EMAIL PROTECTED]> wrote:
> Are there any plans to add a BSF wrapper to JEXL?
>
> -
> To u
On 11/9/07, sebb <[EMAIL PROTECTED]> wrote:
> Are there any plans to add a BSF wrapper to JEXL?
>
At some point (well over a year ago, before v1.1), I had one for some
prototyping I was doing. I never intended to put it anywhere, but if
there is interest, we can polish it and pr
Are there any plans to add a BSF wrapper to JEXL?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
81 matches
Mail list logo
