That's great Jim!
On 12/16/20 11:13 AM, Jim Jagielski wrote:
Just a FYI: I have been invited to the official BeanShell team and so it is
likely that my fork will be folded back into beanshell.org as the v2.x version
while we work on the v3.x version in parallel.
Right now I have a 2.
Just a FYI: I have been invited to the official BeanShell team and so it is
likely that my fork will be folded back into beanshell.org as the v2.x version
while we work on the v3.x version in parallel.
Right now I have a 2.2.0b1 release and I'm looking into seeing how far we can
take it.
Just a FYI:
https://twitter.com/jimjag/status/1338840166828568576
TL;DR: I've forked beanshell and beanshell2 into something which maybe we can
baseline for AOO
-
To unsubscribe, e-mail: dev-uns
eb Jim Jagielski:
>>> There appears to be quite a large change in beanshell from 2.0b6 and what
>>> is currently HEAD of master.
>> I built it with the system version of Debian 10 bsh 2.0b4-19. and this
>> part works.
>
> This is odd. I bumbed the build.xml f
On 07.12.20 21:56, Mechtilde wrote:
Hello Jim
Am 07.12.20 um 20:35 schrieb Jim Jagielski:
There appears to be quite a large change in beanshell from 2.0b6 and what is
currently HEAD of master.
I built it with the system version of Debian 10 bsh 2.0b4-19. and this
part works.
This is odd
On 07.12.20 23:34, Dave Fisher wrote:
Sent from my iPhone
On Dec 7, 2020, at 2:08 PM, Peter Kovacs wrote:
On 07.12.20 21:56, Mechtilde wrote:
Hello Jim
Am 07.12.20 um 20:35 schrieb Jim Jagielski:
There appears to be quite a large change in beanshell from 2.0b6 and what is
currently
Sent from my iPhone
> On Dec 7, 2020, at 2:08 PM, Peter Kovacs wrote:
>
>
>> On 07.12.20 21:56, Mechtilde wrote:
>> Hello Jim
>>
>>> Am 07.12.20 um 20:35 schrieb Jim Jagielski:
>>> There appears to be quite a large change in beanshell from 2.
On 07.12.20 21:56, Mechtilde wrote:
Hello Jim
Am 07.12.20 um 20:35 schrieb Jim Jagielski:
There appears to be quite a large change in beanshell from 2.0b6 and what is
currently HEAD of master.
I built it with the system version of Debian 10 bsh 2.0b4-19. and this
part works.
Ok.
Now the
Hello Jim
Am 07.12.20 um 20:35 schrieb Jim Jagielski:
> There appears to be quite a large change in beanshell from 2.0b6 and what is
> currently HEAD of master.
I built it with the system version of Debian 10 bsh 2.0b4-19. and this
part works.
Now the build hangs with hsqldb
there I h
There appears to be quite a large change in beanshell from 2.0b6 and what is
currently HEAD of master.
Any interest in looking into getting beanshell into some more stable
situation... It looks like it's been majorly refac
UNO API's.
>
> The OpenOffice-Groovy [3] is the OpenOffice extension to add Groovy to the
> scripting framework. It
> is heavily influenced by the built-in Beanshell.
> I'm using Groovy's GroovyShell to evaluate the script [4].
> It includes the Groovy UNO Extension.
which uses Apache BSF and which is based on the BeanShell
implementation of the
ScriptProvider) in case you have not yet implemented the ScriptProvider part
for Groovy.
I'm planning a more formal announcement as soon as I finish the Readme's
for a couple of these but...
There
hich is based on the BeanShell
implementation of the
ScriptProvider) in case you have not yet implemented the ScriptProvider part
for Groovy.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional com
Hi Carl,
Am 13.07.20 um 22:07 schrieb Carl Marcum:
> Hi Matthias,
>
> On 7/13/20 10:16 AM, Matthias Seidel wrote:
>>
>> Hi Peter,
>>
>> Am 13.07.20 um 12:37 schrieb Peter:
>>> At build there is a beanshell switch, which turns the feature on.
>>
Hi Matthias,
On 7/13/20 10:16 AM, Matthias Seidel wrote:
Hi Peter,
Am 13.07.20 um 12:37 schrieb Peter:
At build there is a beanshell switch, which turns the feature on.
"--enable-beanshell" activates it.
This wasn't necessary for 4.1.x but we should include it now in
Hi Peter,
Am 13.07.20 um 12:37 schrieb Peter:
> At build there is a beanshell switch, which turns the feature on.
"--enable-beanshell" activates it.
This wasn't necessary for 4.1.x but we should include it now in our 42X
build scripts.
@Carl: This is for Groovy?
Reg
At build there is a beanshell switch, which turns the feature on.
Am 13.07.20 um 12:27 schrieb Carl Marcum:
Hi All,
Have Beanshell macros been intentionally disabled in trunk?
I don't see the option in Tools > Macros > Organize Macros.
Or maybe I need a configure flag for it?
T
Hi All,
Have Beanshell macros been intentionally disabled in trunk?
I don't see the option in Tools > Macros > Organize Macros.
Or maybe I need a configure flag for it?
Thanks,
Carl
-
To unsubscribe, e-mail: d
stlport from code. We already build without it, and no
one is using it. We have a Repository system for managing old code. We do not
need to carry stuff we do not use.
Another potential candidate to get Rid of is beanshell. I am looking into it,
the project moved to Apache Commons. I hope that it is
Repository system for managing old code. We do not
> need to carry stuff we do not use.
>
> Another potential candidate to get Rid of is beanshell. I am looking into it,
> the project moved to Apache Commons. I hope that it is still there under a
> different name (beanUtil?)
remove stlport from code. We already build without
it, and no one is using it. We have a Repository system for
managing old code. We do not need to carry stuff we do not use.
Another potential candidate to get Rid of is beanshell. I am
looking into it, the project moved to Apache Commons. I h
potential candidate to get Rid of is beanshell. I am looking
into it, the project moved to Apache Commons. I hope that it is still
there under a different name (beanUtil?)
Cleaning out stuff is important.
right.
Howeverr, when you write for which the ressources are used it would be
easier t
status:
STLPort is still considered -> I see no counter arguments to wards
removal from code, it will stay in the repository. I am fine with a tag
if that helps. I want to write a proposal in may.
BEANSHELL is canceled, because my understand that it moved into Apache
Common is wrong.
S
Am 25.04.20 um 03:50 schrieb Peter Kovacs:
I would like to remove stlport from code. We already build without it,
and no one is using it. We have a Repository system for managing old
code. We do not need to carry stuff we do not use.
Another potential candidate to get Rid of is beanshell. I
I have seen you on the repository of beanshell. I stared the project now
and fully watching it. It is all I can do for now. But if there is
something I send in patches.
So far no objections for STLPORT removal. -> STLPORT is still on.
Beanshell is still an own Project -> BEANSHELL is o
Hi guys;
FWIW, I am involved in beanshell in my spare time, which is not plenty
lately. As mentioned previously it is in github now and a much improved
version will be released one day (no ETA).
While looking for candidates to remove stuff, consider stax. It is
included in Java since JDK5
Okay, thanks Damjan.
I found the mail in Apache Commons and some other mentions.
So I think I got confused.
Am 25.04.20 um 08:42 schrieb Damjan Jovanovic:
On Sat, Apr 25, 2020 at 3:50 AM Peter Kovacs wrote:
Another potential candidate to get Rid of is beanshell. I am looking
into it, the
On Sat, Apr 25, 2020 at 3:50 AM Peter Kovacs wrote:
>
> Another potential candidate to get Rid of is beanshell. I am looking
> into it, the project moved to Apache Commons. I hope that it is still
> there under a different name (beanUtil?)
>
>
See https://github.com/beanshell
Maybe I was not clear enough.
beanshell we use is unmaintained and very old.
A potential successor is in Apache-Commons. I am investigating.
Without a valid successor we will not drop. In doubt we have to adopt
and maintain.
But I dont thionk so. I already found the vote in Apache Common to
Hello,
I want to brint to attention that we can use BEANSHELL for writing
Macros. This is one point beside Basic, Javascript and Python.
This shouldn't be cut.
Kind regards
Mechtilde
Am 25.04.20 um 03:50 schrieb Peter Kovacs:
> Hello all,
>
>
> I would like to remove stlp
Hello all,
I would like to remove stlport from code. We already build without it,
and no one is using it. We have a Repository system for managing old
code. We do not need to carry stuff we do not use.
Another potential candidate to get Rid of is beanshell. I am looking
into it, the
Hi
Sorry for noticing late.
beanshell was relicensed under an Apache License starting with bsh 2.0b5.
Apparently I had something to do with breaking the beanshell build
(thanks for fixing): on FreeBSD we use the external (prepackaged)
beanshell which is 2.0b6.
Pedro
Hi Jim,
Am 18.01.19 um 16:34 schrieb Jim Jagielski:
> Hrmmm... doing a re-build w/ --enable-beanshell causes as break in
> scripting/java:
>
>
> /Users/jim/src/asf/AOO42X/main/scripting/java/com/sun/star/script/framework/provider/beanshell/ScriptProviderForBeanShell.jav
Hrmmm... doing a re-build w/ --enable-beanshell causes as break in
scripting/java:
/Users/jim/src/asf/AOO42X/main/scripting/java/com/sun/star/script/framework/provider/beanshell/ScriptProviderForBeanShell.java:232:
error: package bsh does not exist
catch (bsh.EvalError e) {
not
I just noticed that when including CatB components, beanshell
is not included in trunk/4.2.x but IS with 4.1.x
Any idea why the change?
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e
other Apache
Projects.
The author of beanshell, Patrick Niemeyer, generously agreed to make
the sources for his project available under an Apache License and
further went through the process of submitting a SGA to the Apache
Software Foundation. A small group of us have been cleaning the code
Am 01/11/2015 09:50 PM, schrieb Pedro Giffuni:
Hello;
One of the great achievements behind this project is the ability to open
new code under a less restrictive license for use in other Apache Projects.
The author of beanshell, Patrick Niemeyer, generously agreed to make the
sources for his
Hello;
One of the great achievements behind this project is the ability to open
new code under a less restrictive license for use in other Apache Projects.
The author of beanshell, Patrick Niemeyer, generously agreed to make the
sources for his project available under an Apache License and
Pedro Giffuni wrote:
After the vote (which is apparently still open?), most of us that were
involved, have been too busy on other things.
The vote was considered closed some weeks ago closed due to inactivity
on the issue (but if I understand correctly work had been done then, but
was simply
Hi Pedro,
On 25.03.2014 16:29, Pedro Giffuni wrote:
> Hello;
>
> Concerning beanshell itself, we did everything we were supposed to do to get
> Beanshell into the
> ASF. The code was relicensed and the major IP-clearance process was done. The
> author also
> submitted a SGA
Hello;
Concerning beanshell itself, we did everything we were supposed to do to
get Beanshell into the ASF. The code was relicensed and the major
IP-clearance process was done. The author also submitted a SGA to the
ASF secretary. You can check out the code in apache-extras:
https
Buona sera Andrea,
On 24.03.2014 22:48, Andrea Pescetti wrote:
> Rony G. Flatscher (Apache) wrote:
>> While going after the current implementation of a script provider, I would
>> like to target the
>> beanshell implemantion.
>
> This is only marginally related to
Rony G. Flatscher (Apache) wrote:
While going after the current implementation of a script provider, I would like
to target the
beanshell implemantion.
This is only marginally related to what you are doing now, but note that
Beanshell itself was proposed for becoming an Incubator project
On 24.03.2014 16:32, Jürgen Schmidt wrote:
> On 3/24/14 4:00 PM, Rony G. Flatscher (Apache) wrote:
>> While going after the current implementation of a script provider, I would
>> like to target the
>> beanshell implemantion.
>>
>> Found an URL (via the web)
On 3/24/14 4:00 PM, Rony G. Flatscher (Apache) wrote:
> While going after the current implementation of a script provider, I would
> like to target the
> beanshell implemantion.
>
> Found an URL (via the web) pointing to:
>
>
> <http://svn.apache.org/repo
While going after the current implementation of a script provider, I would like
to target the
beanshell implemantion.
Found an URL (via the web) pointing to:
<http://svn.apache.org/repos/asf/openoffice/trunk/main/scripting/java/com/sun/star/script/framework/provider/beanshell/>
On Thu, Feb 21, 2013 at 3:07 AM, Andrea Pescetti wrote:
> There is a proposal for BeanShell to join the Apache Incubator:
> http://wiki.apache.org/incubator/BeanShellProposal
>
> BeanShell is one of the Apache OpenOffice build dependencies, currently
> minimally maintained, and i
There is a proposal for BeanShell to join the Apache Incubator:
http://wiki.apache.org/incubator/BeanShellProposal
BeanShell is one of the Apache OpenOffice build dependencies, currently
minimally maintained, and it would be good to have it at Apache too.
Pedro helped a lot in bringing
48 matches
Mail list logo
