Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update JAR management reporting classes not identified #551

Conversation

masesdevelopers
Copy link
Contributor

Description

It is possible that the JVM used from JNetReflector does not support some classes, e.g. java.util.SequencedMap (available from JDK 21), or there is a missing dependency in the classpath: the tool now reports classes found in the JAR but not loaded.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@masesdevelopers masesdevelopers added enhancement New feature or request JNetReflector JNetReflector related issue labels Sep 27, 2024
@masesdevelopers masesdevelopers self-assigned this Sep 27, 2024
@masesdevelopers masesdevelopers merged commit b4f7a90 into masesgroup:master Sep 27, 2024
3 checks passed
@masesdevelopers masesdevelopers deleted the 542-jnetreflector-writes-some-files-using-execution-stub-with-different-behaviors-on-each-execution-5 branch September 27, 2024 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request JNetReflector JNetReflector related issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant