Request: Backport Java Upgrade & bsh Removal to 2.0.x (Release 2.0.9)

[TusharVerma015]

Hi @mimno ,

I came across the existing pull request for the Java upgrade and removal of the incompatible BeanShell (bsh) dependency: #213
.

We are currently using MALLET in a legacy codebase, and upgrading directly to version 2.1.0 is not feasible for us. The changes in 2.1.0 forcing us to regenerate our existing models, which would have a significant impact on our system.

Would it be possible to cherry-pick the Java upgrade and bsh removal changes onto the 2.0.8 branch and release it as a new version (e.g., 2.0.9)? This would allow teams like ours to benefit from these important updates without introducing breaking changes from 2.1.0.

Please let us know your thoughts. We’d really appreciate your consideration.

Thanks for your work on MALLET!

[raghu298]

Hi @mimno,

This sounds good approach to help users who are still on 2.0.8 while also addressing the existing jakarta incomptiable issues.

Would it be possible for us to try cherry-picking those changes onto the 2.0.8 branch and proceed with a release?

[mimno]

I made a branch https://github.com/mimno/Mallet/tree/mallet-jdk1.8 to be available for people who don't want to switch to newer Java. Would it be enough to just make this a named release, or are there changes that went along with the 2.1.0 release that you would like to add? I'm assuming if you were ok with the previous version, you're ok with beanshell?

[mimno]

Also, is it the JDK 17 update that is an issue, or the switch to HPPC from GNU trove?

[raghu298]

@mimno i think the bsh removal is the concern can we remove bsh totally from the mallet-jdk1.8 branch

[raghu298]

@mimno As per above the user is not able to use 2.1.0 version as switching from hppc to gnu trove have problematic what I understood and its existing legacy code migration may have impacts what I feel and he want bsh removal

[mimno]

I'm seeing right now if Claude can make a branch that maintains serialization compatibility with Trove. But an alternative is to port the model files. Can I ask what type of models you use?

[mimno]

Can you take a look at https://github.com/mimno/TroveMallet/releases/tag/v2.0.9? This applies some of the updates to Mallet since the 2016 conversion from trove to HPPC, so it should have bug fixes and performance improvements but still be compatible with existing serialized models. I've broken it out to a new repo to reduce confusion.

[TusharVerma015]

Hi, thanks for this. Just want to confirm few things. Is bsh removed from here? We are currently into 2.0.8 and we are using mallet based models so we don't want the existing functionality to break.

[mimno]

It should just have bug fixes and improvements, but no breaking changes. If you could try it in a test environment I'd like to hear what you find! Thanks for using Mallet.

[raghu298]

@mimno user ask is for Jakarta incompatible bsh part and I think it's still part of the v2.0.9 tag

[TusharVerma015]

@mimno is bsh removed in this v2.0.9 tag? It is jakarta incompatible and mallet is using it and it's blocking us. I just wanted to confirm if that is been taken care of in this tag that you gave

[TusharVerma015]

@mimno

Hi,

I noticed that version 2.0.10 includes Java 17 support and has the bsh dependency removed, which is great.

I wanted to check if this version will be actively maintained going forward. In case it won’t be, would it be possible to release a 2.0.9 variant without the bsh dependency?

The presence of bsh in 2.0.9 is currently impacting our services due to its incompatibility with Jakarta, so having a compatible version would be really helpful for us given our existing setup.

Below is the link for 2.0.10 for your reference.
https://central.sonatype.com/artifact/io.github.mallet-ml/mallet

Thanks in advance for your support!

[TusharVerma015]

Hi @mimno , just following up on the above

[TusharVerma015]

Hi @mimno , can you please look into this as we are blocked on this?

[mimno]

I clauded a 2.0.10 release: https://github.com/mimno/TroveMallet/releases/tag/v2.0.10 It keeps trove, but drops beanshell, upgrades to JUnit 4, separates out the tests, and upgrades to Java 11. How does that look?

…

On Tue, Mar 24, 2026 at 12:55 AM Tushar Verma ***@***.***> wrote: *TusharVerma015* left a comment (mimno/Mallet#217) <#217 (comment)> Hi @mimno <https://github.com/mimno> , just following up on the above — Reply to this email directly, view it on GitHub <#217?email_source=notifications&email_token=AARPWOTUIIW6VCUYMTJD7OD4SIILBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJRGUZTSMRUGAZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4115392403>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARPWOWN2DVPNIDGQWVANXT4SIILBAVCNFSM6AAAAACWUSKVAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMJVGM4TENBQGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>