Re: Java 21 for jEdit ?

Yes, that's what I understand. There was a conversation about this some
time ago and that was the consensus at the time. The newer beanshell code
is licensed under Apache license, where the version in jEdit right now is
GPL, and GPL3 would let us include the newer beanshell code even though
it's using the Apache license. I'd be happy to update the beanshell code to
the newer version, but not for this release since it would need some pretty
good testing to make sure we don't break existing macros.

On Wed, Oct 4, 2023 at 3:05 PM Matthieu Casanova <[email protected]>
wrote:

> I am not sure I understand well (but I am not a licence expert).
> But today jEdit is GPL 2. And you say that adding some GPL 3 code would
> change all jEdit to GPL 3 automatically ?
> Any new code or it has to be specific ?
> Because if it is any new code I committed a few weeks ago that new class
> which comes with no dependencies to any other part of jEdit and since I am
> the only committer I suppose I can change it's licence to any licence right
> ?
>
> https://sourceforge.net/p/jedit/svn/25686/tree//jEdit/trunk/org/jedit/util/SystemManager.java
>
> Matthieu
>
> Mer 04 oct 2023, à 22:47, Dale Anson a écrit :
>
> The license issue shouldn't be hard to resolve, GPL 3 would allow Apache
> licensed code to be mixed in. We just need some new code with a GPL 3
> license committed to the project, then the rest is automatic.
>
> On Wed, Oct 4, 2023 at 2:10 PM Matthieu Casanova <[email protected]>
> wrote:
>
>
> Hey,
> are you able to reproduce it today ?
> I tried with a macro
>
> sb.bsh containing
>
> StringBuilder sb = new StringBuilder();
> sb.append("test");
> System.out.println(sb.toString());
>
> I run it with Java 17.0.8.1 (Adoptium) and it works.
> I tried to recompile jEdit with that same JDK and ran jEdit and the test
> and it also worked.
> Did I miss something or maybe someone fixed the bug already?
>
> As Dale told it seems we will not be able to upgrade Beanshell because of
> their licence change so we have the choice to find another alternative that
> would be compatible with GPL (I don't know any), otherwise we might try to
> solve the problem ourselves in our version of Beanshell.
>
> --
>   Matthieu Casanova
>   [email protected]
>
>
> Mer 04 oct 2023, à 22:03, Dale Anson a écrit :
>
> I believe it's in the same place it was last year. It isn't hard to
> upgrade the integrated beanshell to a newer, java 17+ compatible version,
> but there is still the GPL vs Apache license issue which hasn't been worked
> out.
>
> On Wed, Oct 4, 2023 at 1:40 PM Robert Schwenn <[email protected]>
> wrote:
>
>
> Hi,
>
> do You have in mind that there's a issue with integrated beanshell (
> https://sourceforge.net/p/jedit/bugs/4118/) not being compatible with
> java 17 (and presumably later)? Or is it fixed already (or a mistake)?
>
> Robert
>
>
>
> Am 02.10.2023 um 23:27 schrieb Matthieu Casanova:
>
> Hey,
> we missed java 17 and are still on java 11. Java 21 arrived and it is LTS,
> I think it would be nice that the next version of jEdit (after 5.7 release)
> would be java 21 which brings a lot of nice features especially virtual
> threads.
> Anyone against it ?
>
> Matthieu
>
>
> --
> -----------------------------------------------
> jEdit Developers' List
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>
> --
> -----------------------------------------------
> jEdit Developers' List
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>
>
> --
> -----------------------------------------------
> jEdit Developers' List
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>
>

-- 
-----------------------------------------------
jEdit Developers' List
[email protected]
https://lists.sourceforge.net/lists/listinfo/jedit-devel