I like the idea of having a “custom” lib folder, also for the .zip distribution. That would make updating to new versions of BaseX a little easier.
Sent from my Windows 10 phone
From: Christian Grünmailto:christian.gruen@gmail.com Sent: Thursday, May 11, 2017 4:09 PM To: Andy Buncemailto:bunce.andy@gmail.com Cc: basex-talk@mailman.uni-konstanz.demailto:basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Java Modules - Constructor
In fact I have modified the bat to add a "lib2" folder where I can easier manage extension jars.
set CP=%MAIN%/BaseX.jar;%MAIN%/lib/*;%MAIN%/lib2/*
Good point. For the Windows executable, I thought about adding a 'custom' sub-directory in the lib folder. The jars in the lib directory could be deleted with each update, but the custom folder would be preserved.
But is the original problem a bug? That is after installing the jar via REPO install t:new("aaa") fails although it works when added to lib/
Be sure I’ll check this out later this week.