Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Hi, Christian, I am not qualified to speak about these things, being a Windows user and without a clue concerning all those Unix things. My naive perspective is this: as a Windows user, everything is wonderfully simple - download the installer, click, click, click. done. But with Unix, it seems that it's not quite so, and perhaps even Hackerish knowledge comes into play, and ease may hinge on levels of expertise and experience. And I think it is worth the effort to have a beautiful documentation of installation and upgrade, extending all knowledge, know-how and what-not on a silver tray. Am Mittwoch, 17. März 2021, 18:52:36 MEZ hat Christian Grün Folgendes geschrieben: Hi Hans-Jürgen, Should this perhaps be part of the official documentation? Especially installation and upgrade deserve maximum attention and helpfulness. I certainly agree. Suggestions are always welcome, either via this list or as directed edits in our Wiki. I hoped that the existing information on how to install BaseX is self-explanatory enough, but maybe we should add more details? Or are you specifically missing hints on how to update certain distributions (such as the ZIP distribution)? Viele GrüßeChristian Am Mittwoch, 17. März 2021, 18:07:38 MEZ hat Bridger Dyson-Smith Folgendes geschrieben: Hi Joris, On Wed, Mar 17, 2021 at 5:39 AM commandline-be wrote: ok, thanks. If i can i will try and figure out an upgrade approach or see if i can run a backport which does have the more recent version available. I've found that something like this following works very well for me across several operating systems: ```cd ~/binmkdir basex-src basex-datawget https://files.basex.org/releases/BaseX.zipunzip BaseX.ziprm -rf basex/src basex/dataln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data ~/bin/basex-data```You can include the ~/bin/basex directory path in your environmental $PATH and you're off to the races. Subsequent updates are basically grabbing the ZIP archive, unpacking it, removing the default src and data directories, and recreating the symbolic links. All of your database info is kept separately from the defaults, so you don't worry about overwriting in an upgrade. It's still manual and necessitates some steps, but it's been an easy method for me across several different unix-like operating systems (Redhat, Void, and FreeBSD) that don't have a package for installation. I know some other people have posted similar approaches here on the mailing list, but I can't think of an easy search term to help locate them. Essentialy, i dislike Ubuntu a lot and Arch well, i never got round to arch really. Best, Joris HTHBest, Bridger - - - mailto:commandl...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, 17 March 2021 10:35, Christian Grün wrote: > > Linux is eays, everything is a file. It are the specifics which make it > > hard, particularly configuration. > > Right. At the moment, there is no automatized process to get the > Debian/Ubuntu distribution updates automatized. > > > I think my issue with the Preferences panel may come from running the most > > recent basex and it overwriting configuration files since it writes a > > message to screen saying it overwrites the configuration file. > > Thanks for the insight. If you want to stick with the old version of > BaseX, you can delete the .basexgui file (which includes the GUI > configuration) to resolve the issue.
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Thanks for the perspective. Here's what i hope comes across as a polite rant as a reply. It aches me and i notice it aches others everywhere. I spent 20 years on and off with Linux, starting with a CT magazine CD somewhere late 90's. I've really grown stone cold tired of the package management nonsense with unmaintained, poorly maintained software. Except for the big packges like desktops that is for which no sane compilation procudure exists. Also get irritated with the so called distro specific narrative. There are exactly 2 systems, Debian and RedHat of which Debian is universally compatible and Redhat is not so much. It should not be an issue really. This implies developing compatible with the RedHat system is alwasy going to work on Debian, not vice versa. When it comes to package managers almost none of the work well or if they work well there is no sensible package maintenance happening. Or they build a great set of software like Sabayon Linux and stop the disro. The times i found myself downloading source and compiling from scratch to have all features and flags enabled became too many. Yet every time i go back almost to not using package managers. Such as I end up with now with BaseX By now i'm contemplating a no-package manager custom Linux distroy with update scripts for my personal choice of tools. Simply to avoid the cruft and 99% meaningless software in most distributions. Maybe i build it all on BaseX to manage configuration, compilation and other stuff. I'm a niche user who also happens to be picky and mostly atypical as an IT profile. The future will probably bring hard choices and hard work for me because of it. Br, Joris On Wed, 2021-03-17 at 13:47 -0400, Bridger Dyson-Smith wrote: > Joris - > > On Wed, Mar 17, 2021 at 1:40 PM commandline-be > wrote: > > Thanks for this. > > > > > > No problem and my pleasure. > > Basically I am pondering why I should use a packaged version and > > why not. > > > > > Why: I think there's an advantage to having a OS-based package that's > readily available - it's certainly very convenient to say `sudo yum > install basex` or `pkg install basex` or whatever your package > management expression happens to be, and whammo! you have a system- > wide BaseX installation. > > Why Not: > * someone has to maintain the package! Keep it up to date with minor > version bumps (one of the very nicest things about BaseX is how > quickly Christian and Co. respond to bugs and errors - minor bug > patches are infrequent but when there's an issue, there's a fix very > quickly), and modifying the default file paths to match your OS' > expectations. > * do you really need it installed system-wide? I've found that, at > least for my use-cases, an install to my home directory is sufficient > - but I'm not doing anything complicated! It would be great to hear > other user stories about this, which reminds me of a different email > I need to send to this list! > > > > > I did use the most recent .jar to test and it works well but the > > what about the server part etc. > > > > > > If you grab the ZIP archive, everything you'd want is included (http > server, GUI, client/server). > > > Br > > > > Joris > > > > > > Best, > Bridger > > > > > > > > > > > > Oorspronkelijk bericht > > Aan 17 mrt. 2021 18:07, Bridger Dyson-Smith < > > bdysonsm...@gmail.com> schreef: > > > > > > Hi Joris, > > > > > > On Wed, Mar 17, 2021 at 5:39 AM commandline-be > > > wrote: > > > > ok, thanks. > > > > > > > > > > > > If i can i will try and figure out an upgrade approach or see > > > > if i can run a backport which does have the more recent version > > > > available. > > > > > > > > > > > > > > I've found that something like this following works very well for > > > me across several operating systems: > > > > > > ``` > > > cd ~/bin > > > mkdir basex-src basex-data > > > wget https://files.basex.org/releases/BaseX.zip > > > unzip BaseX.zip > > > rm -rf basex/src basex/data > > > ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data > > > ~/bin/basex-data > > > ``` > > > You can include the ~/bin/basex directory path in your > > > environmental $PATH and you're off to the races. > > > > > > Subsequent updates are basically grabbing the ZIP archive, > > > unpacking it, removing the default src and data directories, and > > > recreating the symbolic links. > > > All of your database info is kept separately from the defaults, > > > so you don't worry about overwriting in an upgrade. > > > > > > It's still manual and necessitates some steps, but it's been an > > > easy method for me across several different unix-like operating > > > systems (Redhat, Void, and FreeBSD) that don't have a package for > > > installation. > > > > > > I know some other people have posted similar approaches here on > > > the mailing list, but I can't think of an easy search term to > > > help locate them. > > > > > > > Essentialy, i dislike Ubuntu a
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Thanks for this. Basically I am pondering why I should use a packaged version and why not. I did use the most recent .jar to test and it works well but the what about the server part etc. Br Joris \ Oorspronkelijk bericht Aan 17 mrt. 2021 18:07, Bridger Dyson-Smith < bdysonsm...@gmail.com> schreef: > > > > Hi Joris, > > > > > On Wed, Mar 17, 2021 at 5:39 AM commandline-be > <[commandl...@protonmail.com][commandline_protonmail.com]> wrote: > > > > ok, thanks. > > > > > > If i can i will try and figure out an upgrade approach or see if i can run > > a backport which does have the more recent version available. > > > > > > I've found that something like this following works very well for me across > several operating systems: > > > > > \`\`\` > > cd ~/bin > > mkdir basex-src basex-data > > wget https://files.basex.org/releases/BaseX.zip > > unzip BaseX.zip > > rm -rf basex/src basex/data > > ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data ~/bin/basex-data > > \`\`\` > > You can include the ~/bin/basex directory path in your environmental $PATH > and you're off to the races. > > > > > > Subsequent updates are basically grabbing the ZIP archive, unpacking it, > removing the default src and data directories, and recreating the symbolic > links. > > > All of your database info is kept separately from the defaults, so you don't > worry about overwriting in an upgrade. > > > > > It's still manual and necessitates some steps, but it's been an easy method > for me across several different unix-like operating systems (Redhat, Void, > and FreeBSD) that don't have a package for installation. > > > > > > I know some other people have posted similar approaches here on the mailing > list, but I can't think of an easy search term to help locate them. > > > Essentialy, i dislike Ubuntu a lot and Arch well, i never got round to arch > > really. > > > > Best, > > > > Joris > > > > > > HTH > > Best, > > > Bridger > > > > > > \- - - > > mailto:[commandl...@protonmail.com][commandline_protonmail.com] > > > > ‐‐‐ Original Message ‐‐‐ > > On Wednesday, 17 March 2021 10:35, Christian Grün > > <[christian.gr...@gmail.com][christian.gruen_gmail.com]> wrote: > > > > > > Linux is eays, everything is a file. It are the specifics which make it > > > > hard, particularly configuration. > > > > > > > > Right. At the moment, there is no automatized process to get the > > > Debian/Ubuntu distribution updates automatized. > > > > > > > > > I think my issue with the Preferences panel may come from running the > > > > most recent basex and it overwriting configuration files since it > > > > writes a message to screen saying it overwrites the configuration file. > > > > > > > > Thanks for the insight. If you want to stick with the old version of > > > BaseX, you can delete the .basexgui file (which includes the GUI > > > configuration) to resolve the issue. > > > > [commandline_protonmail.com]: mailto:commandl...@protonmail.com [christian.gruen_gmail.com]: mailto:christian.gr...@gmail.com signature.asc Description: OpenPGP digital signature
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
On Wed, Mar 17, 2021 at 2:06 PM Joris Lambrecht wrote: > Thanks for the perspective. Here's what i hope comes across as a polite > rant as a reply. It aches me and i notice it aches others everywhere. > > I spent 20 years on and off with Linux, starting with a CT magazine CD > somewhere late 90's. I've really grown stone cold tired of the package > management nonsense with unmaintained, poorly maintained software. > Except for the big packges like desktops that is for which no sane > compilation procudure exists. > > I can appreciate this, but I'm always remembering that many of these pieces of software are being maintained gratis, without any expectation of recompensense (or thanks, even!). That said, you are not wrong - managing widely-available downloads is a crazy process! Also get irritated with the so called distro specific narrative. There > are exactly 2 systems, Debian and RedHat of which Debian is universally > compatible and Redhat is not so much. It should not be an issue really. > This implies developing compatible with the RedHat system is alwasy > going to work on Debian, not vice versa. > > I only use Redhat for work, but every time it's an exercise in remembering "Is it yum? Is it rpm?" and I am sympathetic. That being said, and maybe I'm a different sort of outlier here, but there are a bunch of excellent operating systems, only a few of which derive from Linux. They all handle things differently, too, to be fair. When it comes to package managers almost none of the work well or if > they work well there is no sensible package maintenance happening. Or > they build a great set of software like Sabayon Linux and stop the > disro. > > The times i found myself downloading source and compiling from scratch > to have all features and flags enabled became too many. Yet every time > i go back almost to not using package managers. Such as I end up with > now with BaseX > > By now i'm contemplating a no-package manager custom Linux distroy with > update scripts for my personal choice of tools. Simply to avoid the > cruft and 99% meaningless software in most distributions. Maybe i build > it all on BaseX to manage configuration, compilation and other stuff. > > I'm a niche user who also happens to be picky and mostly atypical as an > IT profile. The future will probably bring hard choices and hard work > for me because of it. > > That resonates! Good luck (and welcome to BaseX) > > Br, > > Joris > > Bridger > On Wed, 2021-03-17 at 13:47 -0400, Bridger Dyson-Smith wrote: > > Joris - > > > > On Wed, Mar 17, 2021 at 1:40 PM commandline-be > > wrote: > > > Thanks for this. > > > > > > > > > > No problem and my pleasure. > > > Basically I am pondering why I should use a packaged version and > > > why not. > > > > > > > > > Why: I think there's an advantage to having a OS-based package that's > > readily available - it's certainly very convenient to say `sudo yum > > install basex` or `pkg install basex` or whatever your package > > management expression happens to be, and whammo! you have a system- > > wide BaseX installation. > > > > Why Not: > > * someone has to maintain the package! Keep it up to date with minor > > version bumps (one of the very nicest things about BaseX is how > > quickly Christian and Co. respond to bugs and errors - minor bug > > patches are infrequent but when there's an issue, there's a fix very > > quickly), and modifying the default file paths to match your OS' > > expectations. > > * do you really need it installed system-wide? I've found that, at > > least for my use-cases, an install to my home directory is sufficient > > - but I'm not doing anything complicated! It would be great to hear > > other user stories about this, which reminds me of a different email > > I need to send to this list! > > > > > > > > I did use the most recent .jar to test and it works well but the > > > what about the server part etc. > > > > > > > > > > If you grab the ZIP archive, everything you'd want is included (http > > server, GUI, client/server). > > > > > Br > > > > > > Joris > > > > > > > > > > Best, > > Bridger > > > > > > > > > > > > > > > > > > Oorspronkelijk bericht > > > Aan 17 mrt. 2021 18:07, Bridger Dyson-Smith < > > > bdysonsm...@gmail.com> schreef: > > > > > > > > Hi Joris, > > > > > > > > On Wed, Mar 17, 2021 at 5:39 AM commandline-be > > > > wrote: > > > > > ok, thanks. > > > > > > > > > > > > > > > If i can i will try and figure out an upgrade approach or see > > > > > if i can run a backport which does have the more recent version > > > > > available. > > > > > > > > > > > > > > > > > > I've found that something like this following works very well for > > > > me across several operating systems: > > > > > > > > ``` > > > > cd ~/bin > > > > mkdir basex-src basex-data > > > > wget https://files.basex.org/releases/BaseX.zip > > > > unzip BaseX.zip > > > > rm -rf basex/src basex/data > > > > ln -s ~/bin/basex-src ~/bin/basex/src; ln -s
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Hi, I like Debian very much. The package management is one of the best and most to all of the packages I use are well enough maintained and work and update as expected when using the buster-backports repository. It pains me to read, not for the first time, that the Debian BaseX package seems to be on a kind of less maintained base than the files downloadable at basex.org and no one cares about updates or better backports. Pure unmodified Debian stable has a tendency of aging. But may be some people develop their code exclusivly for Debian 10 stable packages. That is a valid approach. I have no clue if there is any list of packages activly maintained during the Debian stable lifecycle. I guess not. Ubuntu has such a list and a tool to check the setup for the maintenance state for each package. The ubuntu list of mnaintained packages is surprisingly short if you look at the over all huge number of packages available. For me this is less about the well maintained vanilla distribution of BaseX, which I use with any JDK on any OS, including Debian 10, then with the BaseX Debian package 9.0.1+ds-1 that is not part of the regular release process of basex.org and so outdated and furthermore created in a manner that is especially hard to understand and maintain seperately from the rest of Debian. Maybe I am wrong, but is the current maintainer of the Debian packages actually on this list? It seems to me we get error reports here which are totally lost on the person who might do something about the problems. Best regards Omar Siam Am 17.03.2021 um 19:06 schrieb Joris Lambrecht: Thanks for the perspective. Here's what i hope comes across as a polite rant as a reply. It aches me and i notice it aches others everywhere. I spent 20 years on and off with Linux, starting with a CT magazine CD somewhere late 90's. I've really grown stone cold tired of the package management nonsense with unmaintained, poorly maintained software. Except for the big packges like desktops that is for which no sane compilation procudure exists. Also get irritated with the so called distro specific narrative. There are exactly 2 systems, Debian and RedHat of which Debian is universally compatible and Redhat is not so much. It should not be an issue really. This implies developing compatible with the RedHat system is alwasy going to work on Debian, not vice versa. When it comes to package managers almost none of the work well or if they work well there is no sensible package maintenance happening. Or they build a great set of software like Sabayon Linux and stop the disro. The times i found myself downloading source and compiling from scratch to have all features and flags enabled became too many. Yet every time i go back almost to not using package managers. Such as I end up with now with BaseX By now i'm contemplating a no-package manager custom Linux distroy with update scripts for my personal choice of tools. Simply to avoid the cruft and 99% meaningless software in most distributions. Maybe i build it all on BaseX to manage configuration, compilation and other stuff. I'm a niche user who also happens to be picky and mostly atypical as an IT profile. The future will probably bring hard choices and hard work for me because of it. Br, Joris
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Hi Hans-Jürgen, Should this perhaps be part of the official documentation? Especially > installation and upgrade deserve maximum attention and helpfulness. > I certainly agree. Suggestions are always welcome, either via this list or as directed edits in our Wiki. I hoped that the existing information on how to install BaseX is self-explanatory enough, but maybe we should add more details? Or are you specifically missing hints on how to update certain distributions (such as the ZIP distribution)? Viele Grüße Christian > Am Mittwoch, 17. März 2021, 18:07:38 MEZ hat Bridger Dyson-Smith < > bdysonsm...@gmail.com> Folgendes geschrieben: > > > Hi Joris, > > On Wed, Mar 17, 2021 at 5:39 AM commandline-be > wrote: > > ok, thanks. > > > If i can i will try and figure out an upgrade approach or see if i can run > a backport which does have the more recent version available. > > I've found that something like this following works very well for me > across several operating systems: > > ``` > cd ~/bin > mkdir basex-src basex-data > wget https://files.basex.org/releases/BaseX.zip > unzip BaseX.zip > rm -rf basex/src basex/data > ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data > ~/bin/basex-data > ``` > You can include the ~/bin/basex directory path in your environmental $PATH > and you're off to the races. > > Subsequent updates are basically grabbing the ZIP archive, unpacking it, > removing the default src and data directories, and recreating the symbolic > links. > All of your database info is kept separately from the defaults, so you > don't worry about overwriting in an upgrade. > > It's still manual and necessitates some steps, but it's been an easy > method for me across several different unix-like operating systems (Redhat, > Void, and FreeBSD) that don't have a package for installation. > > I know some other people have posted similar approaches here on the > mailing list, but I can't think of an easy search term to help locate them. > > > Essentialy, i dislike Ubuntu a lot and Arch well, i never got round to > arch really. > > Best, > > Joris > > HTH > Best, > Bridger > > > > > - - - > mailto:commandl...@protonmail.com > > ‐‐‐ Original Message ‐‐‐ > On Wednesday, 17 March 2021 10:35, Christian Grün < > christian.gr...@gmail.com> wrote: > > > > Linux is eays, everything is a file. It are the specifics which make > it hard, particularly configuration. > > > > > Right. At the moment, there is no automatized process to get the > > Debian/Ubuntu distribution updates automatized. > > > > > > I think my issue with the Preferences panel may come from running the > most recent basex and it overwriting configuration files since it writes a > message to screen saying it overwrites the configuration file. > > > > > Thanks for the insight. If you want to stick with the old version of > > BaseX, you can delete the .basexgui file (which includes the GUI > > configuration) to resolve the issue. > >
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Joris - On Wed, Mar 17, 2021 at 1:40 PM commandline-be wrote: > Thanks for this. > > No problem and my pleasure. > Basically I am pondering why I should use a packaged version and why not. > Why: I think there's an advantage to having a OS-based package that's readily available - it's certainly very convenient to say `sudo yum install basex` or `pkg install basex` or whatever your package management expression happens to be, and whammo! you have a system-wide BaseX installation. Why Not: * someone has to maintain the package! Keep it up to date with minor version bumps (one of the very nicest things about BaseX is how quickly Christian and Co. respond to bugs and errors - minor bug patches are infrequent but when there's an issue, there's a fix very quickly), and modifying the default file paths to match your OS' expectations. * do you really need it installed system-wide? I've found that, at least for my use-cases, an install to my home directory is sufficient - but I'm not doing anything complicated! It would be great to hear other user stories about this, which reminds me of a different email I need to send to this list! > I did use the most recent .jar to test and it works well but the what > about the server part etc. > > If you grab the ZIP archive, everything you'd want is included (http server, GUI, client/server). > Br > > Joris > > Best, Bridger > > > > > > Oorspronkelijk bericht > Aan 17 mrt. 2021 18:07, Bridger Dyson-Smith < bdysonsm...@gmail.com> > schreef: > > > Hi Joris, > > On Wed, Mar 17, 2021 at 5:39 AM commandline-be > wrote: > >> ok, thanks. >> >> >> If i can i will try and figure out an upgrade approach or see if i can >> run a backport which does have the more recent version available. >> >> I've found that something like this following works very well for me > across several operating systems: > > ``` > cd ~/bin > mkdir basex-src basex-data > wget https://files.basex.org/releases/BaseX.zip > unzip BaseX.zip > rm -rf basex/src basex/data > ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data > ~/bin/basex-data > ``` > You can include the ~/bin/basex directory path in your environmental $PATH > and you're off to the races. > > Subsequent updates are basically grabbing the ZIP archive, unpacking it, > removing the default src and data directories, and recreating the symbolic > links. > All of your database info is kept separately from the defaults, so you > don't worry about overwriting in an upgrade. > > It's still manual and necessitates some steps, but it's been an easy > method for me across several different unix-like operating systems (Redhat, > Void, and FreeBSD) that don't have a package for installation. > > I know some other people have posted similar approaches here on the > mailing list, but I can't think of an easy search term to help locate them. > >> >> Essentialy, i dislike Ubuntu a lot and Arch well, i never got round to >> arch really. >> >> Best, >> >> Joris >> >> HTH > Best, > Bridger > > >> >> - - - >> mailto:commandl...@protonmail.com >> >> ‐‐‐ Original Message ‐‐‐ >> On Wednesday, 17 March 2021 10:35, Christian Grün < >> christian.gr...@gmail.com> wrote: >> >> > > Linux is eays, everything is a file. It are the specifics which make >> it hard, particularly configuration. >> > >> >> > Right. At the moment, there is no automatized process to get the >> > Debian/Ubuntu distribution updates automatized. >> > >> >> > > I think my issue with the Preferences panel may come from running the >> most recent basex and it overwriting configuration files since it writes a >> message to screen saying it overwrites the configuration file. >> > >> >> > Thanks for the insight. If you want to stick with the old version of >> > BaseX, you can delete the .basexgui file (which includes the GUI >> > configuration) to resolve the issue. >> >>
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
> > Basically I am pondering why I should use a packaged version and why not. Did you already check our documention [1]? Best, Christian [1] https://docs.basex.org/wiki/Startup > I did use the most recent .jar to test and it works well but the what > about the server part etc. > > Br > > Joris > > > > > > > Oorspronkelijk bericht > Aan 17 mrt. 2021 18:07, Bridger Dyson-Smith < bdysonsm...@gmail.com> > schreef: > > > Hi Joris, > > On Wed, Mar 17, 2021 at 5:39 AM commandline-be > wrote: > >> ok, thanks. >> >> >> If i can i will try and figure out an upgrade approach or see if i can >> run a backport which does have the more recent version available. >> >> I've found that something like this following works very well for me > across several operating systems: > > ``` > cd ~/bin > mkdir basex-src basex-data > wget https://files.basex.org/releases/BaseX.zip > unzip BaseX.zip > rm -rf basex/src basex/data > ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data > ~/bin/basex-data > ``` > You can include the ~/bin/basex directory path in your environmental $PATH > and you're off to the races. > > Subsequent updates are basically grabbing the ZIP archive, unpacking it, > removing the default src and data directories, and recreating the symbolic > links. > All of your database info is kept separately from the defaults, so you > don't worry about overwriting in an upgrade. > > It's still manual and necessitates some steps, but it's been an easy > method for me across several different unix-like operating systems (Redhat, > Void, and FreeBSD) that don't have a package for installation. > > I know some other people have posted similar approaches here on the > mailing list, but I can't think of an easy search term to help locate them. > >> >> Essentialy, i dislike Ubuntu a lot and Arch well, i never got round to >> arch really. >> >> Best, >> >> Joris >> >> HTH > Best, > Bridger > > >> >> - - - >> mailto:commandl...@protonmail.com >> >> ‐‐‐ Original Message ‐‐‐ >> On Wednesday, 17 March 2021 10:35, Christian Grün < >> christian.gr...@gmail.com> wrote: >> >> > > Linux is eays, everything is a file. It are the specifics which make >> it hard, particularly configuration. >> > >> >> > Right. At the moment, there is no automatized process to get the >> > Debian/Ubuntu distribution updates automatized. >> > >> >> > > I think my issue with the Preferences panel may come from running the >> most recent basex and it overwriting configuration files since it writes a >> message to screen saying it overwrites the configuration file. >> > >> >> > Thanks for the insight. If you want to stick with the old version of >> > BaseX, you can delete the .basexgui file (which includes the GUI >> > configuration) to resolve the issue. >> >>
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Should this perhaps be part of the official documentation? Especially installation and upgrade deserve maximum attention and helpfulness. Am Mittwoch, 17. März 2021, 18:07:38 MEZ hat Bridger Dyson-Smith Folgendes geschrieben: Hi Joris, On Wed, Mar 17, 2021 at 5:39 AM commandline-be wrote: ok, thanks. If i can i will try and figure out an upgrade approach or see if i can run a backport which does have the more recent version available. I've found that something like this following works very well for me across several operating systems: ```cd ~/binmkdir basex-src basex-datawget https://files.basex.org/releases/BaseX.zipunzip BaseX.ziprm -rf basex/src basex/dataln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data ~/bin/basex-data```You can include the ~/bin/basex directory path in your environmental $PATH and you're off to the races. Subsequent updates are basically grabbing the ZIP archive, unpacking it, removing the default src and data directories, and recreating the symbolic links. All of your database info is kept separately from the defaults, so you don't worry about overwriting in an upgrade. It's still manual and necessitates some steps, but it's been an easy method for me across several different unix-like operating systems (Redhat, Void, and FreeBSD) that don't have a package for installation. I know some other people have posted similar approaches here on the mailing list, but I can't think of an easy search term to help locate them. Essentialy, i dislike Ubuntu a lot and Arch well, i never got round to arch really. Best, Joris HTHBest, Bridger - - - mailto:commandl...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, 17 March 2021 10:35, Christian Grün wrote: > > Linux is eays, everything is a file. It are the specifics which make it > > hard, particularly configuration. > > Right. At the moment, there is no automatized process to get the > Debian/Ubuntu distribution updates automatized. > > > I think my issue with the Preferences panel may come from running the most > > recent basex and it overwriting configuration files since it writes a > > message to screen saying it overwrites the configuration file. > > Thanks for the insight. If you want to stick with the old version of > BaseX, you can delete the .basexgui file (which includes the GUI > configuration) to resolve the issue.
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Hi Joris, On Wed, Mar 17, 2021 at 5:39 AM commandline-be wrote: > ok, thanks. > > > If i can i will try and figure out an upgrade approach or see if i can run > a backport which does have the more recent version available. > > I've found that something like this following works very well for me across several operating systems: ``` cd ~/bin mkdir basex-src basex-data wget https://files.basex.org/releases/BaseX.zip unzip BaseX.zip rm -rf basex/src basex/data ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data ~/bin/basex-data ``` You can include the ~/bin/basex directory path in your environmental $PATH and you're off to the races. Subsequent updates are basically grabbing the ZIP archive, unpacking it, removing the default src and data directories, and recreating the symbolic links. All of your database info is kept separately from the defaults, so you don't worry about overwriting in an upgrade. It's still manual and necessitates some steps, but it's been an easy method for me across several different unix-like operating systems (Redhat, Void, and FreeBSD) that don't have a package for installation. I know some other people have posted similar approaches here on the mailing list, but I can't think of an easy search term to help locate them. > > Essentialy, i dislike Ubuntu a lot and Arch well, i never got round to > arch really. > > Best, > > Joris > > HTH Best, Bridger > > - - - > mailto:commandl...@protonmail.com > > ‐‐‐ Original Message ‐‐‐ > On Wednesday, 17 March 2021 10:35, Christian Grün < > christian.gr...@gmail.com> wrote: > > > > Linux is eays, everything is a file. It are the specifics which make > it hard, particularly configuration. > > > > > Right. At the moment, there is no automatized process to get the > > Debian/Ubuntu distribution updates automatized. > > > > > > I think my issue with the Preferences panel may come from running the > most recent basex and it overwriting configuration files since it writes a > message to screen saying it overwrites the configuration file. > > > > > Thanks for the insight. If you want to stick with the old version of > > BaseX, you can delete the .basexgui file (which includes the GUI > > configuration) to resolve the issue. > >
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
ok, thanks. If i can i will try and figure out an upgrade approach or see if i can run a backport which does have the more recent version available. Essentialy, i dislike Ubuntu a lot and Arch well, i never got round to arch really. Best, Joris - - - mailto:commandl...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, 17 March 2021 10:35, Christian Grün wrote: > > Linux is eays, everything is a file. It are the specifics which make it > > hard, particularly configuration. > > Right. At the moment, there is no automatized process to get the > Debian/Ubuntu distribution updates automatized. > > > I think my issue with the Preferences panel may come from running the most > > recent basex and it overwriting configuration files since it writes a > > message to screen saying it overwrites the configuration file. > > Thanks for the insight. If you want to stick with the old version of > BaseX, you can delete the .basexgui file (which includes the GUI > configuration) to resolve the issue. signature.asc Description: OpenPGP digital signature
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
> Linux is eays, everything is a file. It are the specifics which make it hard, > particularly configuration. Right. At the moment, there is no automatized process to get the Debian/Ubuntu distribution updates automatized. > I think my issue with the Preferences panel may come from running the most > recent basex and it overwriting configuration files since it writes a message > to screen saying it overwrites the configuration file. Thanks for the insight. If you want to stick with the old version of BaseX, you can delete the .basexgui file (which includes the GUI configuration) to resolve the issue.
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Linux is eays, everything is a file. It are the specifics which make it hard, particularly configuration. On the website i found Debian, Ubuntu, Arch listed. With regards to Debian, Debian has the .jar deployed as part of maven, which also included a version specific .pom file. Since i don't know maven i'm not daring to try anything there. I think my issue with the Preferences panel may come from running the most recent basex and it overwriting configuration files since it writes a message to screen saying it overwrites the configuration file. - - - mailto:commandl...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, 17 March 2021 10:17, Christian Grün wrote: > > Is there a guide how to upgrade a packed version of Basex with the > > downloaded version of basex ? > > I must confess I know too little about the Debian distribution. > > > mailto:commandl...@protonmail.com > > ‐‐‐ Original Message ‐‐‐ > > On Wednesday, 17 March 2021 09:56, Christian Grün christian.gr...@gmail.com > > wrote: > > > > > It seems you are using an older version of BaseX. Does the problem > > > also happen with the latest version [1,2]? > > > > > Thanks, > > > Christian > > > > > [1] https://basex.org/download/ > > > [2] https://docs.basex.org/wiki/Startup > > > > > On Wed, Mar 17, 2021 at 9:50 AM commandline-be > > > commandl...@protonmail.com wrote: > > > > > > Hey, > > > > To split off this bug report from the 'first post on this mailinglist' > > > > thread. > > > > Noteworthy but probably not relevant is every time is start basexgui i > > > > see > > > > [warning] /usr/bin/basexgui: Unable to locate > > > > /usr/share/java/tagsoup.jar in /usr/share/java > > > > [warning] /usr/bin/basexgui: Unable to locate /usr/share/java/jline.jar > > > > in /usr/share/java > > > > This is the output i see in the terminal when running the command > > > > basexgui and selecting Preferences in the window. This repeats every > > > > time i select Preferences. > > > > Exception in thread "AWT-EventQueue-0" > > > > java.lang.IndexOutOfBoundsException: Index: 3, Tab count: 3 > > > > at > > > > java.desktop/javax.swing.JTabbedPane.checkIndex(JTabbedPane.java:1758) > > > > at > > > > java.desktop/javax.swing.JTabbedPane.setSelectedIndex(JTabbedPane.java:595) > > > > at org.basex.gui.dialog.DialogPrefs.(DialogPrefs.java:44) > > > > at org.basex.gui.dialog.DialogPrefs.show(DialogPrefs.java:56) > > > > at org.basex.gui.GUIMenuCmd$50.execute(GUIMenuCmd.java:778) > > > > at org.basex.gui.GUIMenu.lambda$newItem$0(GUIMenu.java:77) > > > > at > > > > java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) > > > > at > > > > java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) > > > > at > > > > java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) > > > > at > > > > java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) > > > > at > > > > java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369) > > > > at > > > > java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020) > > > > at > > > > java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064) > > > > at > > > > java.desktop/java.awt.Component.processMouseEvent(Component.java:6635) > > > > at > > > > java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) > > > > at java.desktop/java.awt.Component.processEvent(Component.java:6400) > > > > at java.desktop/java.awt.Container.processEvent(Container.java:2263) > > > > at > > > > java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5011) > > > > at > > > > java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) > > > > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) > > > > at > > > > java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) > > > > at > > > > java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) > > > > at > > > > java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) > > > > at > > > > java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) > > > > at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) > > > > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) > > > > at > > > > java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) > > > > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) > > > > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) > > > > at java.base/java.security.AccessController.doPrivileged(Native Method) > > > > at > > > > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > > > > at > > > >
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
> Is there a guide how to upgrade a packed version of Basex with the downloaded > version of basex ? I must confess I know too little about the Debian distribution. > - - - > mailto:commandl...@protonmail.com > > ‐‐‐ Original Message ‐‐‐ > On Wednesday, 17 March 2021 09:56, Christian Grün > wrote: > > > It seems you are using an older version of BaseX. Does the problem > > also happen with the latest version [1,2]? > > > > > Thanks, > > Christian > > > > > [1] https://basex.org/download/ > > [2] https://docs.basex.org/wiki/Startup > > > > > On Wed, Mar 17, 2021 at 9:50 AM commandline-be > > commandl...@protonmail.com wrote: > > > > > > Hey, > > > To split off this bug report from the 'first post on this mailinglist' > > > thread. > > > Noteworthy but probably not relevant is every time is start basexgui i see > > > [warning] /usr/bin/basexgui: Unable to locate /usr/share/java/tagsoup.jar > > > in /usr/share/java > > > [warning] /usr/bin/basexgui: Unable to locate /usr/share/java/jline.jar > > > in /usr/share/java > > > This is the output i see in the terminal when running the command > > > basexgui and selecting Preferences in the window. This repeats every time > > > i select Preferences. > > > Exception in thread "AWT-EventQueue-0" > > > java.lang.IndexOutOfBoundsException: Index: 3, Tab count: 3 > > > at java.desktop/javax.swing.JTabbedPane.checkIndex(JTabbedPane.java:1758) > > > at > > > java.desktop/javax.swing.JTabbedPane.setSelectedIndex(JTabbedPane.java:595) > > > at org.basex.gui.dialog.DialogPrefs.(DialogPrefs.java:44) > > > at org.basex.gui.dialog.DialogPrefs.show(DialogPrefs.java:56) > > > at org.basex.gui.GUIMenuCmd$50.execute(GUIMenuCmd.java:778) > > > at org.basex.gui.GUIMenu.lambda$newItem$0(GUIMenu.java:77) > > > at > > > java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) > > > at > > > java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) > > > at > > > java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) > > > at > > > java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) > > > at > > > java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369) > > > at > > > java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020) > > > at > > > java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064) > > > at java.desktop/java.awt.Component.processMouseEvent(Component.java:6635) > > > at > > > java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) > > > at java.desktop/java.awt.Component.processEvent(Component.java:6400) > > > at java.desktop/java.awt.Container.processEvent(Container.java:2263) > > > at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5011) > > > at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) > > > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) > > > at > > > java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) > > > at > > > java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) > > > at > > > java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) > > > at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) > > > at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) > > > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) > > > at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) > > > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) > > > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) > > > at java.base/java.security.AccessController.doPrivileged(Native Method) > > > at > > > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > > > at > > > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) > > > at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) > > > at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) > > > at java.base/java.security.AccessController.doPrivileged(Native Method) > > > at > > > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > > > at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742) > > > at > > > java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) > > > at > > > java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) > > > at > > > java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) > > > at > > > java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) > > >
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
Hey Christian, I don't know, this new version is not available on Debian. I did test running the .jar of the new version and it did not show this problem. Is there a guide how to upgrade a packed version of Basex with the downloaded version of basex ? For the old version this problem 'suddenly' emerged after using it without issue for at least a week. Br, Joris - - - mailto:commandl...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, 17 March 2021 09:56, Christian Grün wrote: > It seems you are using an older version of BaseX. Does the problem > also happen with the latest version [1,2]? > > Thanks, > Christian > > [1] https://basex.org/download/ > [2] https://docs.basex.org/wiki/Startup > > On Wed, Mar 17, 2021 at 9:50 AM commandline-be > commandl...@protonmail.com wrote: > > > Hey, > > To split off this bug report from the 'first post on this mailinglist' > > thread. > > Noteworthy but probably not relevant is every time is start basexgui i see > > [warning] /usr/bin/basexgui: Unable to locate /usr/share/java/tagsoup.jar > > in /usr/share/java > > [warning] /usr/bin/basexgui: Unable to locate /usr/share/java/jline.jar in > > /usr/share/java > > This is the output i see in the terminal when running the command basexgui > > and selecting Preferences in the window. This repeats every time i select > > Preferences. > > Exception in thread "AWT-EventQueue-0" java.lang.IndexOutOfBoundsException: > > Index: 3, Tab count: 3 > > at java.desktop/javax.swing.JTabbedPane.checkIndex(JTabbedPane.java:1758) > > at > > java.desktop/javax.swing.JTabbedPane.setSelectedIndex(JTabbedPane.java:595) > > at org.basex.gui.dialog.DialogPrefs.(DialogPrefs.java:44) > > at org.basex.gui.dialog.DialogPrefs.show(DialogPrefs.java:56) > > at org.basex.gui.GUIMenuCmd$50.execute(GUIMenuCmd.java:778) > > at org.basex.gui.GUIMenu.lambda$newItem$0(GUIMenu.java:77) > > at > > java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) > > at > > java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) > > at > > java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) > > at > > java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) > > at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369) > > at > > java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020) > > at > > java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064) > > at java.desktop/java.awt.Component.processMouseEvent(Component.java:6635) > > at > > java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) > > at java.desktop/java.awt.Component.processEvent(Component.java:6400) > > at java.desktop/java.awt.Container.processEvent(Container.java:2263) > > at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5011) > > at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) > > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) > > at > > java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) > > at > > java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) > > at > > java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) > > at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) > > at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) > > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) > > at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) > > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) > > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) > > at java.base/java.security.AccessController.doPrivileged(Native Method) > > at > > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > > at > > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) > > at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) > > at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) > > at java.base/java.security.AccessController.doPrivileged(Native Method) > > at > > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > > at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742) > > at > > java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) > > at > > java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) > > at > > java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) > > at > >
Re: [basex-talk] Preferences do not open, Exception in thread AWT-EventQueue-0
It seems you are using an older version of BaseX. Does the problem also happen with the latest version [1,2]? Thanks, Christian [1] https://basex.org/download/ [2] https://docs.basex.org/wiki/Startup On Wed, Mar 17, 2021 at 9:50 AM commandline-be wrote: > > Hey, > > To split off this bug report from the 'first post on this mailinglist' thread. > > Noteworthy but probably not relevant is every time is start basexgui i see > [warning] /usr/bin/basexgui: Unable to locate /usr/share/java/tagsoup.jar > in /usr/share/java > [warning] /usr/bin/basexgui: Unable to locate /usr/share/java/jline.jar > in /usr/share/java > > This is the output i see in the terminal when running the command basexgui > and selecting Preferences in the window. This repeats every time i select > Preferences. > > Exception in thread "AWT-EventQueue-0" java.lang.IndexOutOfBoundsException: > Index: 3, Tab count: 3 > at java.desktop/javax.swing.JTabbedPane.checkIndex(JTabbedPane.java:1758) > at java.desktop/javax.swing.JTabbedPane.setSelectedIndex(JTabbedPane.java:595) > at org.basex.gui.dialog.DialogPrefs.(DialogPrefs.java:44) > at org.basex.gui.dialog.DialogPrefs.show(DialogPrefs.java:56) > at org.basex.gui.GUIMenuCmd$50.execute(GUIMenuCmd.java:778) > at org.basex.gui.GUIMenu.lambda$newItem$0(GUIMenu.java:77) > at > java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) > at > java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) > at > java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) > at > java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) > at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369) > at > java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020) > at > java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064) > at java.desktop/java.awt.Component.processMouseEvent(Component.java:6635) > at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) > at java.desktop/java.awt.Component.processEvent(Component.java:6400) > at java.desktop/java.awt.Container.processEvent(Container.java:2263) > at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5011) > at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) > at > java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) > at > java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) > at > java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) > at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) > at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4843) > at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > at > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) > at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) > at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742) > at > java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) > at > java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) > at > java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) > at > java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) > at > java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) > at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) > > > Best, > > Joris > - - - > mailto:commandl...@protonmail.com > > >
