-
Notifications
You must be signed in to change notification settings - Fork 343
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
Breaking change after 7.2.0 ? #1040
Comments
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. |
okay so using :
So not sure if it's really a bug in |
Hmm, there was a patch version update for Maven, and this: 0da6d30#diff-b958f840c0529a7d4cc364d0e80267591bd50ed398b563d8d530513a5c9a3869R61. Can you see from your logs which Maven call produced the output? Can you make a minimal reproduction case maybe? The actual call to Maven to extract the licenses did not change. |
After upgrading to
|
@rhuitl @ttomaszewski I pushed a quick fix for this ba920d1 Im not sure what the jakarta jar is so this at least maintains functionality like the previous release if needed |
Hello, To add on to this, I am getting a similar error, just with a different zip file...
I also noticed that in my maven cache that file is either missing or just named differently.
For now I have downgraded back down to 7.1.0 and it works. |
^ I just encounted the same zip file error, although on a different file:
I was able to get past this by patching license_files.rb so that it doesn't attempt to open non-existing files.
|
Following up from that last comment, I also needed to apply the following patch in order to generate a CSV report:
|
Hi,
We are using
license finder
to audit all our projects. We capturestdout
to find new licences to check.For maven-based projects, we use
license_finder --no-prepare --enabled-package-managers=maven --maven-options=package --quiet --maven-include-groups=true
Since
7.2.0
released today, the output is polluted by messages coming from our test suite, so breaking everything.Did something changed regarding this ? Can we pass extra options to
license finder
to either ignore tests (like-Dmaven.test.skip=true -DskipTests=true
we commonly use when invoking maven directly) or simply ignore test output ?Thank you !
The text was updated successfully, but these errors were encountered: