fix: detect packages in multi-project repositories

[zermelo-wisen]

Fixes #283.

This PR addresses the issue of failure to autodetect package names in some multi-project repositories. Specifically, the Java AppMap agent was unable to auto-detect packages in the multi-project structure of the Retrofit repository. The agent only looked for src/main/java directories, which led to an appmap.yml configuration file with no detected packages, as shown below:

# This is the AppMap configuration file.
# For full documentation of this file for Java programs, see:
# https://appmap.io/docs/reference/appmap-java.html#configuration
name: retrofit
packages: []
# appmap-java init looks for source packages in src/main/java.
# This folder was not found in your project, so no packages were auto-detected.
# You can add your source packages by replacing the line above with lines like this:
# packages:
# - path: com.mycorp.pkg
# - path: org.otherstuff.pkg

The repository is structured with multiple subprojects, each containing their own src/main/java directories:

Changes Made

1. AppMapConfig.java: Updated AppMapConfig.java to traverse the root directory and collect packages from all relevant src/main/java directories across subprojects.

   • Introduced a method collectPackages to encapsulate the logic for collecting Java packages.
   • Modified the main initialization logic to traverse the root directory and look for src/main/java subdirectories.
   • Ensured the autodetection mechanism now works for projects with nested subprojects.

2. agent_cli.bats: Updated the test for the CLI agent initialization to verify the detection of packages within subprojects.

   • Added assertions to check for the presence of subproject package paths in CLI output.

3. Test Project Structure: Added a sample subproject structure to the test project for verifying the updated behavior.

[appland-release]

🎉 This PR is included in version 1.27.1 🎉

The release is available on:

• v1.27.1
• GitHub release

Your semantic-release bot 📦🚀