Skip to content

Class files in test project directories incorrectly excluded from analysis #107

Closed

Description

@rahlk

Describe the bug

When running the application on a test project located in codeanalyzer-java/src/test/resources/test-applications/plantsbywebsphere, .class files are not detected. This occurs because the file filtering logic excludes any paths containing test/resources/, even when these directories contain valid project files.

Steps To Reproduce

  1. Place a Java project in codeanalyzer-java/src/test/resources/test-applications/plantsbywebsphere.
  2. Run the application to analyze .class files.
  3. Observe that no .class files are found in the log output.

Observed behavior

The application incorrectly filters out .class files from the test project directory due to the absolute path containing test/resources/. This results in zero application classes being detected and registered, even though the build is successful and .class files are present.

Expected behavior

.class files should only be excluded if they are located in test/resources/ directories within the specific project path, not if the project itself resides in a directory named test/resources/.

Error Log

2025-02-07T21:58:40.366443234   [INFO]  Finding *.class files in /home/rkrsn/workspace/codellm-devkit/codeanalyzer-java/src/test/resources/test-applications/plantsbywebsphere
2025-02-07T21:58:40.369674335   [DEBUG] Application class files: 0
2025-02-07T21:58:40.369726402   [INFO]  Adding application classes to scope.
2025-02-07T21:58:42.055214269   [DONE]  There were a total of 33844 classes of which 0 are application classes.
2025-02-07T21:58:42.070370877   [INFO]  Registered 0 entrypoints.

Environment (please complete the following information):

  • OS: Fedora Linux 41 (Workstation Edition)
  • Version of Java: 21
  • Version of Maven: N/A
  • Version of Gradle: N/A

Additional context

The issue is likely due to applying filters based on absolute paths rather than paths relative to the provided project directory. This causes unintended exclusion of .class files when the project resides under directories like test/resources/.

Activity

  1. self-assigned this
    on Feb 8, 2025
  2. added a commit that references this issue on Feb 8, 2025
  3. rahlk commented on Feb 8, 2025

    @rahlk
    CollaboratorAuthor

    Fixed in commit c1d9824

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions