fix: remove duplicate isSealed and permittedSubclassNames fields from JVMClassInfo

[Himaswin]

Fixes #605

Removed duplicate isSealed and permittedSubclassNames field declarations
from JVMClassInfo as they already exist in parent class ClassInfo.

[Mahmoud-Khawaja]

Hi Himaswin,
Thank you for your pull request. can you please add some tests? maybe something to test isSealed or isPermittedSubclass(). we need to check that parsing a .class file correctly populates isSealed and permittedSubclassNames. this is gonna be a little bit hard i know but i dont think there is a way to do it other than this.

[Himaswin]

Hi Mahmoud, Thanks for the suggestion. I’ll try to add tests for isSealed and isPermittedSubclass() to verify that parsing the .class file correctly populates those fields. I’ll reach out if I have any doubts, if that’s okay.

…

On Sun, Mar 8, 2026 at 8:13 PM Mahmoud Khawaja ***@***.***> wrote: *Mahmoud-Khawaja* left a comment (javapathfinder/jpf-core#607) <#607 (comment)> Hi Himaswin, Thank you for your pull request. can you please add some tests? maybe something to test isSealed or isPermittedSubclass(). we need to check that parsing a .class file correctly populates isSealed and permittedSubclassNames. this is gonna be a little bit hard i know but i dont think there is a way to do it other than this. — Reply to this email directly, view it on GitHub <#607 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2DUBY4IJKWZLAXBOLFPZBD4PYEC3AVCNFSM6AAAAACWITZDVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMRQGMZTIMJRGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>