There is a bug in the type checking of JClass when the application path does not specify a specific package name.

[YunFy26]

📝 Overall Description

In options.yml

appClassPath: [project/BOOT-INF/classes]

#appClassPath: [project/BOOT-INF/classes/org/example/springtest]

The first configuration causes incorrect type checking.

For example, there is an interface type

package org.example.springtest;

public interface Injection {
    String sayInjection();
}

If the first appClassPath configuration is used, it will result in

JClass aClass = World.get().getClassHierarchy().getClass("org.example.springtest.Injection");
aClass.isAbstract() == true;
aClass.isInterface() == true;

I have created a repo to reproduce this bug, please check it.

🎯 Expected Behavior

None

🐛 Current Behavior

None

🔄 Reproducible Example

No response

⚙️ Tai-e Arguments

🔍 Click here to see Tai-e Options

{{The content of 'output/options.yml' file}}

🔍 Click here to see Tai-e Analysis Plan

{{The content of 'output/tai-e-plan.yml' file}}

📜 Tai-e Log

🔍 Click here to see Tai-e Log

{{The content of 'output/tai-e.log' file}}

ℹ️ Additional Information

No response

[zhangt2333]

The first configuration causes incorrect type checking.

As stated in the Java Language Specification, §9.1.1.1, Every interface is implicitly abstract.

appClassPath: [project/BOOT-INF/classes/org/example/springtest]

This class path is incorrect in your case. It results in World.get().getClassHierarchy().getClass("org.example.springtest.Injection") retrieving a phantom class, which is expected to be located at project/BOOT-INF/classes/org/example/springtest/org/example/springtest/Injection. Consequently, the modifiers for this phantom class may not be reliable.

[YunFy26]

Got it. Thanks!