You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently evaluating License Finder at work and we are facing an issue with Maven project in a subdirectory when scanning multiple projects using the --aggregate_paths option.
To simply and quickly evaluate License Finder, we are using the Docker image in interactive mode (docker run -v $PWD:/scan -it licensefinder/license_finder).
In our case we have a mono repository that is organized this way (simplified/redacted view):
The project directory is mounted at the path /scan and we run License Finder with /LicenseFinder/bin/license_finder report --aggregate_paths='.' './frontend/' './backend/'
Scanning NPM projects located at . and ./frontend/ works fine.
But scanning the Maven project (with submodules) located at ./backend/ fails with the following:
LicenseFinder::Maven: is active
LicenseFinder::Maven: is not installed
This is because it is not able to find the ./mvnw command from the root directory of the project. Indeed that file is located in the backend directory.
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
In the case of Maven Wrapper the path to the command should not be relative to project_path (i.e. ./mvnw) but relative to working directory (as in $PWD) (e.g. backend/mvnw).
We are currently evaluating License Finder at work and we are facing an issue with Maven project in a subdirectory when scanning multiple projects using the
--aggregate_paths
option.To simply and quickly evaluate License Finder, we are using the Docker image in interactive mode (
docker run -v $PWD:/scan -it licensefinder/license_finder
).In our case we have a mono repository that is organized this way (simplified/redacted view):
The
project
directory is mounted at the path/scan
and we run License Finder with/LicenseFinder/bin/license_finder report --aggregate_paths='.' './frontend/' './backend/'
Scanning NPM projects located at
.
and./frontend/
works fine.But scanning the Maven project (with submodules) located at
./backend/
fails with the following:This is because it is not able to find the
./mvnw
command from the root directory of the project. Indeed that file is located in thebackend
directory.In
PackageManager
it checks that a command exists:And in
Maven
the command is defined as:In the case of Maven Wrapper the path to the command should not be relative (
./mvnw
) but absolute w.r.tproject_path
.We tested with the following and it works as expected:
We will shortly create a PR to fix that issue.
The text was updated successfully, but these errors were encountered: