Re: Beanshell
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.2.0b1 release and I'm looking into seeing how far we can take it. On Dec 15, 2020, at 8:38 AM, Jim Jagielski wrote: 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-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Beanshell
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. > On Dec 15, 2020, at 8:38 AM, Jim Jagielski wrote: > > 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-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Beanshell
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-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Beanshell (Re: Source and target of Java version (Was: Review of PR 109))
Just a FYI that I've been hacking on https://github.com/jimjag/beanshell2 which is merge of 2.0b6 and beanshell2. > On Dec 7, 2020, at 8:06 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 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 file from 1.5 to 1.7 according to the > Errormessage. > > Now I have 1 error: > > /home/legine/workspace/AOO/github/main/beanshell/unxlngx6.pro/misc/build/BeanShell-2.0b6/src/bsh/util/AWTConsole.java:217: > error: cannot find symbol > ((java.awt.peer.TextComponentPeer)getPeer()).setCaretPosition( > > and 96 warnings > > A lot look like: warning: [deprecation] > > So how could Debian build them if they use an older Code? > > However it looks like this code queen needs some serious attention. (Java 14 > throws deprecation for 1.7) > > I check tomorrow, and look into fixing the code. > >> >> Now the build hangs with hsqldb >> >> there I have no success to change to the system version of hsqldb 1.8.0 >>> Any interest in looking into getting beanshell into some more stable >>> situation... It looks like it's been majorly refactored. >> kind regards >> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Beanshell (Re: Source and target of Java version (Was: Review of PR 109))
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. I bumbed the build.xml file from 1.5 to 1.7 according to the Errormessage. Now I have 1 error: /home/legine/workspace/AOO/github/main/beanshell/unxlngx6.pro/misc/build/BeanShell-2.0b6/src/bsh/util/AWTConsole.java:217: error: cannot find symbol ((java.awt.peer.TextComponentPeer)getPeer()).setCaretPosition( and 96 warnings A lot look like: warning: [deprecation] So how could Debian build them if they use an older Code? However it looks like this code queen needs some serious attention. (Java 14 throws deprecation for 1.7) I check tomorrow, and look into fixing the code. Now the build hangs with hsqldb there I have no success to change to the system version of hsqldb 1.8.0 Any interest in looking into getting beanshell into some more stable situation... It looks like it's been majorly refactored. kind regards - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Beanshell (Re: Source and target of Java version (Was: Review of PR 109))
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 HEAD of master. I built it with the system version of Debian 10 bsh 2.0b4-19. and this part works. Ok. Now the build hangs with hsqldb there I have no success to change to the system version of hsqldb 1.8.0 Well, the issue is that Java has removed a insecure System API, which HSQLDB uses: cannot find symbol System.runFinalizersOnExit(true); All resources I found are saying you should not use this API. So maybe you can remove the code. Maybe not because the Programmer has been super smart. This link might help. https://help.semmle.com/wiki/plugins/servlet/mobile?contentId=29393456#content/view/29393456 We’ll need to look at finalize methods in the Java we use. I researched in the Discussion Archives of hsqldb. I found [1] which states the use is only conveniance and can commented out. I am trying a build with removed lines. If it works out we could place 2 patches. [1] https://sourceforge.net/p/hsqldb/discussion/73674/thread/82623c95/?limit=25#fc78/e01b Maybe we can try a later version and it works?! Maybe 1.9 works? - I do not know. But this one is a real action point. And thgus I started the discussion. Figuring out what we do now is here imho the most vital part. Any interest in looking into getting beanshell into some more stable situation... It looks like it's been majorly refactored. kind regards - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Beanshell (Re: Source and target of Java version (Was: Review of PR 109))
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 HEAD of master. >> I built it with the system version of Debian 10 bsh 2.0b4-19. and this >> part works. > Ok. >> >> Now the build hangs with hsqldb >> >> there I have no success to change to the system version of hsqldb 1.8.0 > > Well, the issue is that Java has removed a insecure System API, which HSQLDB > uses: > > cannot find symbol System.runFinalizersOnExit(true); > > All resources I found are saying you should not use this API. So maybe you > can remove the code. Maybe not because the Programmer has been super smart. This link might help. https://help.semmle.com/wiki/plugins/servlet/mobile?contentId=29393456#content/view/29393456 We’ll need to look at finalize methods in the Java we use. > > Maybe we can try a later version and it works?! Maybe 1.9 works? > > - I do not know. But this one is a real action point. And thgus I started the > discussion. Figuring out what we do now is here imho the most vital part. > >>> Any interest in looking into getting beanshell into some more stable >>> situation... It looks like it's been majorly refactored. >> kind regards >>
Re: Beanshell (Re: Source and target of Java version (Was: Review of PR 109))
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 build hangs with hsqldb there I have no success to change to the system version of hsqldb 1.8.0 Well, the issue is that Java has removed a insecure System API, which HSQLDB uses: cannot find symbol System.runFinalizersOnExit(true); All resources I found are saying you should not use this API. So maybe you can remove the code. Maybe not because the Programmer has been super smart. Maybe we can try a later version and it works?! Maybe 1.9 works? - I do not know. But this one is a real action point. And thgus I started the discussion. Figuring out what we do now is here imho the most vital part. Any interest in looking into getting beanshell into some more stable situation... It looks like it's been majorly refactored. kind regards
Re: Beanshell (Re: Source and target of Java version (Was: Review of PR 109))
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 have no success to change to the system version of hsqldb 1.8.0 > > Any interest in looking into getting beanshell into some more stable > situation... It looks like it's been majorly refactored. kind regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
Beanshell (Re: Source and target of Java version (Was: Review of PR 109))
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 refactored. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Question ad Groovy implementation (Re: Beanshell Scripting
Hi Carl, On 15.07.2020 01:49, Carl Marcum wrote: > Hi Rony, > > On 7/14/20 10:11 AM, Rony G. Flatscher wrote: >> Hi Carl, >> >> ... cut ... > > I'm planning a more formal announcement as soon as I finish the Readme's for > a couple of these but... > > There are a few inter-dependent projects. > > The Groovy UNO Extension [1] extends the Java UNO API's with convenience > methods for Groovy > Extensions and Client apps. > It's documentation is here [2]. > It uses Groovy's Extension mechanism to extend the 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. > You can get it on Bintray here [5]. > > The third project is OpenOffice-Groovy-Macros [6] an extension to add a lot > of the sample macros > included in AOO rewritten in Groovy. > Probably more useful copy-paste from github since you can't edit these from > the extension like you > can with the built-in macros. > You can get it on Bintray here [7]. > > I plan to add them to the Extension site after I get some more testing done. > > I'm also working on an Extension project generator similar to the NetBeans > plugin but IDE > independent. > Not ready to show that one yet. > > I have copies of the 4.1.6 UNO jars for use by Maven, Gradle and Groovy > scripts in Bintray [8]. > > Please let me know if you have any questions. Thank you *very* much for your explanations and pointers! I can now understand/relate better what you are up to, very interesting! Best regards ---rony > > [1] https://github.com/cbmarcum/guno-extension > [2] https://cbmarcum.github.io/guno-extension/ > [3] https://github.com/cbmarcum/openoffice-groovy > [4] http://www.groovy-lang.org/integrating.html#integ-groovyshell > [5] https://bintray.com/cmarcum/openoffice-extensions/openoffice-groovy#files > [6] https://github.com/cbmarcum/openoffice-groovy-macros > [7] > https://bintray.com/cmarcum/openoffice-extensions/openoffice-groovy-macros#files > [8] https://bintray.com/cmarcum/maven - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Question ad Groovy implementation (Re: Beanshell Scripting
Hi Rony, On 7/14/20 10:11 AM, Rony G. Flatscher wrote: Hi Carl, On 13.07.2020 22:07, Carl Marcum wrote: ... cut ... Currently my Groovy macro is a standalone extension. We can discuss later after I announce it's information whether it could be added to the office at some point or left as a soon-to-be-popular extension ;) Could you briefly explain what your extension does (e.g. generically allowing the implementation of UNO classes/components in Groovy)? ---rony P.S.: AFAIK Groovy uses Apache BSF. If so it may be helpful to look at the ooRexx ScriptProvider implementation (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 are a few inter-dependent projects. The Groovy UNO Extension [1] extends the Java UNO API's with convenience methods for Groovy Extensions and Client apps. It's documentation is here [2]. It uses Groovy's Extension mechanism to extend the 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. You can get it on Bintray here [5]. The third project is OpenOffice-Groovy-Macros [6] an extension to add a lot of the sample macros included in AOO rewritten in Groovy. Probably more useful copy-paste from github since you can't edit these from the extension like you can with the built-in macros. You can get it on Bintray here [7]. I plan to add them to the Extension site after I get some more testing done. I'm also working on an Extension project generator similar to the NetBeans plugin but IDE independent. Not ready to show that one yet. I have copies of the 4.1.6 UNO jars for use by Maven, Gradle and Groovy scripts in Bintray [8]. Please let me know if you have any questions. Best regards, Carl [1] https://github.com/cbmarcum/guno-extension [2] https://cbmarcum.github.io/guno-extension/ [3] https://github.com/cbmarcum/openoffice-groovy [4] http://www.groovy-lang.org/integrating.html#integ-groovyshell [5] https://bintray.com/cmarcum/openoffice-extensions/openoffice-groovy#files [6] https://github.com/cbmarcum/openoffice-groovy-macros [7] https://bintray.com/cmarcum/openoffice-extensions/openoffice-groovy-macros#files [8] https://bintray.com/cmarcum/maven - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Question ad Groovy implementation (Re: Beanshell Scripting
Hi Carl, On 13.07.2020 22:07, Carl Marcum wrote: ... cut ... > Currently my Groovy macro is a standalone extension. > > We can discuss later after I announce it's information whether it could be > added to the office at > some point or left as a soon-to-be-popular extension ;) Could you briefly explain what your extension does (e.g. generically allowing the implementation of UNO classes/components in Groovy)? ---rony P.S.: AFAIK Groovy uses Apache BSF. If so it may be helpful to look at the ooRexx ScriptProvider implementation (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. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Beanshell Scripting
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. >> >> "--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? >> > > No not for Groovy. I just noticed Beanshell was missing from the > Macro language list when I was testing a Python update PR. Thanks for spotting this! I have now added beanshell to our buildbots and to my private Windows builds. Regards, Matthias > > Currently my Groovy macro is a standalone extension. > > We can discuss later after I announce it's information whether it > could be added to the office at some point or left as a > soon-to-be-popular extension ;) > > Thanks for the config switch. > > Best regards, > Carl > >> Regards, >> >> Matthias >> >>> >>> >>> 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? >>>> >>>> Thanks, >>>> Carl >>>> >>>> - >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>> >>> >>> >>> - >>> To unsubscribe, e-mail:dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail:dev-h...@openoffice.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Beanshell Scripting
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 our 42X build scripts. @Carl: This is for Groovy? No not for Groovy. I just noticed Beanshell was missing from the Macro language list when I was testing a Python update PR. Currently my Groovy macro is a standalone extension. We can discuss later after I announce it's information whether it could be added to the office at some point or left as a soon-to-be-popular extension ;) Thanks for the config switch. Best regards, Carl Regards, Matthias 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? Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail:dev-unsubscr...@openoffice.apache.org For additional commands, e-mail:dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Beanshell Scripting
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? Regards, Matthias > > > 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? >> >> Thanks, >> Carl >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org smime.p7s Description: S/MIME Cryptographic Signature
Re: Beanshell Scripting
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? Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Beanshell Scripting
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: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
yes kind of. I have seeb BeanUtil and maybe BSF (I am not sure) and I thought those were successor with the project. But it quickly turned out it has been a misunderstanding on my side. BSF supplies a nice vierity of Scripting Languages. Maybe it is good to keep it in mind for later. As an option, if wwe want to do something fancy. New Feature stuff you know. Am 01.05.20 um 20:04 schrieb Dave Fisher: Were you looking for Apache Commons BSF? http://commons.apache.org/proper/commons-bsf/ On Apr 24, 2020, at 6:50 PM, Peter Kovacs wrote: 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 project moved to Apache Commons. I hope that it is still there under a different name (beanUtil?) Cleaning out stuff is important. Any Objections? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
Were you looking for Apache Commons BSF? http://commons.apache.org/proper/commons-bsf/ > On Apr 24, 2020, at 6:50 PM, Peter Kovacs wrote: > > 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 project moved to Apache Commons. I hope that it is still there under a > different name (beanUtil?) > > Cleaning out stuff is important. > > Any Objections? > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
I just wanted to say in a complicated way that I told what I knew. And I don't think it is worth to do a lot of research to convince others. Am 30.04.20 um 00:41 schrieb Marcus: Am 29.04.20 um 12:13 schrieb Peter Kovacs: Please understand that I assume a per default some resistance towards change. I see it as feature not as failure, we are a bit conservative for a reason. But as a reaction I save my time a bit, where I think it is a waste. I don't understand what you want to tell me here as this is out of context. So which Information do you exactly need? Actually I cannot really help here as I'm not a developer. However I would think that it is helping more to tell some more background of the potential removal candidate. Thats all. ;-) Thanks Marcus Am 29.04.20 um 00:56 schrieb Marcus: 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 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 to judge if it can be really dropped or not. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
Am 29.04.20 um 12:13 schrieb Peter Kovacs: Please understand that I assume a per default some resistance towards change. I see it as feature not as failure, we are a bit conservative for a reason. But as a reaction I save my time a bit, where I think it is a waste. I don't understand what you want to tell me here as this is out of context. So which Information do you exactly need? Actually I cannot really help here as I'm not a developer. However I would think that it is helping more to tell some more background of the potential removal candidate. Thats all. ;-) Thanks Marcus Am 29.04.20 um 00:56 schrieb Marcus: 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 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 to judge if it can be really dropped or not. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
Hi Markus, Please understand that I assume a per default some resistance towards change. I see it as feature not as failure, we are a bit conservative for a reason. But as a reaction I save my time a bit, where I think it is a waste. So which Information do you exactly need? My Current 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. STAX is still considered, because it is now part of a JDK. Therefor the work includes to ensure that all Calls point to the JDK delivered Stax and still work. Hope fully May. SAXON is undecided on my end. I overlooked the dependency to filter (a error in my dependency overview). I am not sure if I really want to migrate to libXML2, which needs to be done in order to make Saxon obsolete. On the other hand we should investigate to update Saxon to version 10. So I am not sure which way is better. Especially since I would like to move away from libXML2 in long term. I am in favor of Apache Xerxes, which is a more natural partner for us. And I have an Idea how filter should evolve. But all this are other stories. All the Best Peter Am 29.04.20 um 00:56 schrieb Marcus: 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 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 to judge if it can be really dropped or not. Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
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 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 to judge if it can be really dropped or not. Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
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 off. I open up a new discussion for removal of stax. Thanks Pedro, very much appreciated. Am 26.04.20 um 04:33 schrieb Pedro Giffuni: 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. Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
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. Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
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 project moved to Apache Commons. I hope that it is still there under a different name (beanUtil?) See https://github.com/beanshell/beanshell#history BeanShell was apparently only proposed as an incubator project, it never entered incubation. Its current home is that GitHub project. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
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/beanshell#history BeanShell was apparently only proposed as an incubator project, it never entered incubation. Its current home is that GitHub project.
Re: drop ressources (stlport, maybe 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 integrate beanshell. I just could not find it, with my tomato eyes :) Am 25.04.20 um 07:37 schrieb Mechtilde: 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 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 still there under a different name (beanUtil?) Cleaning out stuff is important. Any Objections? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: drop ressources (stlport, maybe beanshell)
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 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 still > there under a different name (beanUtil?) > > Cleaning out stuff is important. > > Any Objections? > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
drop ressources (stlport, maybe beanshell)
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 project moved to Apache Commons. I hope that it is still there under a different name (beanUtil?) Cleaning out stuff is important. Any Objections? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: beanshell
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. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: beanshell
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.java:232:
> error: package bsh does not exist
> catch (bsh.EvalError e) {
>
> not sure if this was/is in any way connected to the removal
> from CatB.
>
> Anyone else try building 4.2.x/trunk w/ beanshell?
I am not sure, but Linux32 and Windows builds (AOO42X) from buildbot
were unsuccessful.
Will force new builds with your latest commits...
Regards,
Matthias
>
>> On Jan 17, 2019, at 2:58 PM, Jim Jagielski wrote:
>>
>> 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-mail: dev-h...@openoffice.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
smime.p7s
Description: S/MIME Cryptographic Signature
Re: beanshell
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 sure if this was/is in any way connected to the removal
from CatB.
Anyone else try building 4.2.x/trunk w/ beanshell?
> On Jan 17, 2019, at 2:58 PM, Jim Jagielski wrote:
>
> 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-mail: dev-h...@openoffice.apache.org
>
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
beanshell
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-mail: dev-h...@openoffice.apache.org
Re: Beanshell now under an Apache License
Actually ... I had to revert this as I had forgotten about some small adjustments. Will be back to this later. Pedro. On 01/11/15 15:50, Pedro Giffuni wrote: 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 further went through the process of submitting a SGA to the Apache Software Foundation. A small group of us have been cleaning the code and finally we were able to roll out a release under the new license just before ApacheCon EU 2014. I have been rather lazy and after a friendly reminder from the Apache Taverna project (in incubation), also consumers of Beanshell, I have finally updated to tarball in Apache OpenOffice. As a result of this now beanshell will be built as regular Category-A software and other Apache Projects will also find this code more accessible. Enjoy! Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Beanshell now under an Apache License
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 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 and finally we were able to roll out a release under the new license just before ApacheCon EU 2014. I have been rather lazy and after a friendly reminder from the Apache Taverna project (in incubation), also consumers of Beanshell, I have finally updated to tarball in Apache OpenOffice. As a result of this now beanshell will be built as regular Category-A software and other Apache Projects will also find this code more accessible. that's great news. Thanks for your efforts. To remove the build dependencies is always the best thing. :-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Beanshell now under an Apache License
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 further went through the process of submitting a SGA to the Apache Software Foundation. A small group of us have been cleaning the code and finally we were able to roll out a release under the new license just before ApacheCon EU 2014. I have been rather lazy and after a friendly reminder from the Apache Taverna project (in incubation), also consumers of Beanshell, I have finally updated to tarball in Apache OpenOffice. As a result of this now beanshell will be built as regular Category-A software and other Apache Projects will also find this code more accessible. Enjoy! Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: URL-location for latest beanshell provider source code ?
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 invisible to the Incubator): http://markmail.org/message/ktpdncki6zdooar4 Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: URL-location for latest beanshell provider source code ?
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 to the ASF secretary. You can check out the code in
> apache-extras:
>
> https://code.google.com/a/apache-extras.org/p/beanshell/
>
> As I see it, what stalled the process were basic doubts about the value of
> the incubation process
> itself. In other words, we already did most of what was meant to be done in
> incubation (the
> IP-clearance and the SGA) so if any Apache Project needs the code they can
> consume it directly.
>
> After the vote (which is apparently still open?), most of us that were
> involved, have been too
> busy on other things.
Thank you for this update!
> I would have thought that the Beanshell code was more valuable to the rest of
> the ASF than to
> Apache OpenOffice, where the extension is optional. Beyond AOO, what I would
> have really liked is
> to see the Apache Commons BSF update their support for Beanshell and take it
> in.
The Apache Commons BSF is only working on scripting language /engines/ in two
forms, one being the
pre-javax.script ("pure" Apache versions that originate from the IBM opensource
project donated to
Apache later to originally allow using scripting languages in JSPs) a.k.a. BSF
version 2.x, and a
non-backward compatible version 3.x framework implementing the JSR-223
(javax.script) specs.
BeanShell itself should probably be its own project under the Apache Commons
umbrella.
---rony
Re: URL-location for latest beanshell provider source code ?
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://code.google.com/a/apache-extras.org/p/beanshell/ As I see it, what stalled the process were basic doubts about the value of the incubation process itself. In other words, we already did most of what was meant to be done in incubation (the IP-clearance and the SGA) so if any Apache Project needs the code they can consume it directly. After the vote (which is apparently still open?), most of us that were involved, have been too busy on other things. I would have thought that the Beanshell code was more valuable to the rest of the ASF than to Apache OpenOffice, where the extension is optional. Beyond AOO, what I would have really liked is to see the Apache Commons BSF update their support for Beanshell and take it in. best regards, Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: URL-location for latest beanshell provider source code ?
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 what you are doing now, but note that > Beanshell itself was > proposed for becoming an Incubator project, even if the effort is now stalled > (I think nobody has > taken care of all the initial reviews, grants, etc yet): > http://wiki.apache.org/incubator/BeanShellProposal > > So if, done this, you would like to help bring Beanshell itself to Apache the > first steps are > already done! If I can help from the second line, whatever has to be done there, yes. Unfortunately, I have been tied down heavily with too many tasks to be able to step up into the front line for this initiative, which I too think is very important, especially for AOO! ---rony P.S.: My current interest in beanshell here is to double-check while researching a problem I have been experiencing on MacOSX-AOO with a ScriptProvider for ooRexx, which I had developed and am maintaining. (The same code works flawlessly dispatching ooRexx scripts on 32- and 64-bit.) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: URL-location for latest beanshell provider source code ?
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, even if the effort is now stalled (I think nobody has taken care of all the initial reviews, grants, etc yet): http://wiki.apache.org/incubator/BeanShellProposal So if, done this, you would like to help bring Beanshell itself to Apache the first steps are already done! Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: URL-location for latest beanshell provider source code ?
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) pointing to: >> >> >> <http://svn.apache.org/repos/asf/openoffice/trunk/main/scripting/java/com/sun/star/script/framework/provider/beanshell/> >> >> Just double-checking: would that be the URL to the latest version? If not >> where should I start to >> research/find the latest version? > the link goes directly in trunk of our svn repository, means trunk > contains the latest and greatest version and that is the place to start :-) Jürgen, thank you very much for reassuring this! ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: URL-location for latest beanshell provider source code ?
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/repos/asf/openoffice/trunk/main/scripting/java/com/sun/star/script/framework/provider/beanshell/> > > Just double-checking: would that be the URL to the latest version? If not > where should I start to > research/find the latest version? the link goes directly in trunk of our svn repository, means trunk contains the latest and greatest version and that is the place to start Juergen > > ---rony > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
URL-location for latest beanshell provider source code ?
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/> Just double-checking: would that be the URL to the latest version? If not where should I start to research/find the latest version? ---rony
Re: BeanShell to join the Apache Incubator
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 it would be good to have it at Apache too. > > Pedro helped a lot in bringing BeanShell to the incubator and is one of the > initial committers. If anybody is interested, please join too! > This looks like a great idea. I know Pedro has been pushing for this for a while now, so it is good to see it moving forward. -Rob > Regards, > Andrea.
BeanShell to join the Apache Incubator
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 BeanShell to the incubator and is one of the initial committers. If anybody is interested, please join too! Regards, Andrea.
