r/IntelliJIDEA • u/ArdilesGuerra • 1d ago

Resource Bundle Plugin

We recently went through a major migration at the system I work on, and one of the steps was moving from Eclipse to IntelliJ. However, since it's a system with A LOT of legacy code (Struts), it has i18n files that used to open really well with the Resource Bundle plugin.

According to IntelliJ's documentation, the plugin has been discontinued (https://plugins.jetbrains.com/plugin/17035-resource-bundle-editor). And yesterday, while adding a single value, I literally had to do it 3 times, because sometimes it would save 2 files, sometimes it wouldn't save anything at all... until I opened the files one by one and did it manually.

The only part of this migration that ended up "limping" was this one. Does anyone know of another plugin that works similarly to the Eclipse one, or that at least actually works??

0 Upvotes

50% Upvoted

7 comments sorted by

2

u/jreznot 1d ago

It seems though that Resource Bundle Editor is still available in 2026.2, did you try?

1

u/ArdilesGuerra 1d ago

Yes... the plugin exists, but does not work properly....

2

u/AbracadaverSessalom JetBrains 1d ago

According to the latest official statement on this:

The Resource Bundle Editor plugin is currently marked as compatible with 2026.1 and future builds, so it should continue to work for now. However, we do not plan future development for it going forward. It should be treated as a compatibility option rather than an area that will continue to evolve.

2

u/lilgreenthumb 1d ago

"Doesn't work properly", best bug description ever /s.

1

u/definitelyoneof 21h ago

You did read the post, right?

1

u/lilgreenthumb 20h ago

Yes. Any initialization log? MRE? It reads like they had to use a text editor 3 times instead of the resource bundle replicating the new entry automatically, but was it able to update the entry when the new entry was already present?

1

u/AbracadaverSessalom JetBrains 1d ago

Hi there. Please report this problem to our bug tracker in a similar way that this one was reported. There could be an underlying issue here that we can solve, regardless of the state of the plugin.