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

[core] java.lang.* type name collisions #1526

Closed
nitram84 opened this issue Jun 10, 2022 · 1 comment
Closed

[core] java.lang.* type name collisions #1526

nitram84 opened this issue Jun 10, 2022 · 1 comment
Labels
bug Core Issues in jadx-core module

Comments

@nitram84
Copy link
Contributor

I would like to report some type name collisions with java.lang.* classes. I tested with latest git version and of course the option "Use import statements" is enabled. This issue is similar to #1406.

Case 1: Same package

package jadx.test;

public class System {
  public static void doSomething() {
  }
}
package jadx.test;

public class JavaLangTypeCollision {
  public void doSomething() {
    System.doSomething();
    java.lang.System.out.println("Hello World");
  }
}

Case 2: Inner classes

public class JavaLangTypeCollision2 {
  public void doSomething() {
    System.doSomething();
    java.lang.System.out.println("Hello World");
  }

  public static class System {
    public static void doSomething() {
    }
  }
}

Case 3: Same class (my favorite example)

public class System {
  public static void main(String[] args) {
    java.lang.System.out.println("Hello world");
  }
}
@nitram84 nitram84 added bug Core Issues in jadx-core module labels Jun 10, 2022
@skylot
Copy link
Owner

skylot commented Jun 15, 2022

Fixed. Thank you for test cases 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Core Issues in jadx-core module
Projects
None yet
Development

No branches or pull requests

2 participants