Thanks, Joche.
I am not sure (couldn't get an answer about that from devs), but I think
the plugins are loaded before the script can run, that's precisely the
problem. And also why editing their content would probably not work, as you
say.
Initially I had a question about Groovy and Java, I thoug
On 07.09.20 19:23, Manuel Souto Pico wrote:
Thanks, Jochen.
I'll share this thread (and your comments) with the Java developers that
work on OmegaT (the application).
which seems to be open source and the code is available... I located the
plugin loading code, but I think I do not have the ene
Thanks, Jochen.
I'll share this thread (and your comments) with the Java developers that
work on OmegaT (the application).
To answer your question: the purpose is to update the jar files (if there
is an update available) before the user actually works on the application.
So the sequence is:
1) t
answers inline
On 07.09.20 13:48, Manuel Souto Pico wrote:
[...]
My Groovy script runs within a Java application (called OmegaT). This
application extends its functionality by loading the jar files it finds
in the /plugins folder of the installation. Even though they are
optional and added/remov
Thank you guys for your replies.
And thanks Jochen for asking about what is not clear. I didn't want to give
more detail initially to not make my message too long.
My Groovy script runs within a Java application (called OmegaT). This
application extends its functionality by loading the jar files
Hi Manuel,
I must say, I find this all a little bit confusing.
True certainly is that Java has a general problem with keeping files
open on the windows platform, if these are kept open by some objects.
ClassLoaders keeping jars open is a prime example for this and was
reason for a many bug repor
Maybe you could rename and overwrite the files.
On Mon, 7 Sep 2020 at 10:42, Manuel Souto Pico
wrote:
> Hi there again,
>
> Unfortunately the suggested solution --method deleteOnExit()-- didn't
> really help. I thought it was working but for some reason the files I had
> to delete were not locke
Hi there again,
Unfortunately the suggested solution --method deleteOnExit()-- didn't
really help. I thought it was working but for some reason the files I had
to delete were not locked at that particular moment. Maybe because the Java
application had been running but idle for some time... I don't
Hello everyone!
I want to share with you a quick update on the 2020 Groovy Ecosystem Usage
Report survey. 254 responses collected in the 10 days - that's impressive!
But I know we can do better. If you haven't cast your vote yet, here's the
link to the survey - https://bit.ly/2020-groovy-ecosystem