-
Notifications
You must be signed in to change notification settings - Fork 8
MTA-5964 - Added --disable-maven-search flag in CLI guide #179
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
MTA-5964 - Added --disable-maven-search flag in CLI guide #179
Conversation
a79842c
to
fe12b05
Compare
ad578c4
to
c13717a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thank you! |
Thank you a quick review, Igor! |
@jmle @eemcmullan Could you review the |
f6dc9de
to
4e16c7a
Compare
|`--context-lines` (int)|A number of lines of source code to include in the output for each incident. The default is 100. | ||
|`--disable-maven-search`| Set the flag to `true` to disable {ProductShortName} from relying on the Maven search index to determine if a dependency is publicly available (such as an open-source dependency) or internal to the Java binary application during analysis. | ||
|
||
When you disable Maven search, {ProductShortName} at first tries to determine dependencies from the compiled JAR file. If this method does not succeed, {ProductShortName} goes through the directory structure to determine dependencies. This method may not produce a reliable dependency classification since the package structure can differ from what is expected by {ProductShortName}. You may see more dependencies in the `dependencies.yaml` file because some dependencies may be wrongly classified as internal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion:
When you disable Maven search, {ProductShortName} at first tries to determine dependencies from the JAR files' POM file, if any. If this method does not succeed, {ProductShortName} goes through the directory structure of the JAR to try to determine its identity.
The rest looks good 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jmle! I have updated as you suggested.
|`--context-lines` (int)|A number of lines of source code to include in the output for each incident. The default is 100. | ||
|`--disable-maven-search`| Set the flag to `true` to disable {ProductShortName} from relying on the Maven search index to determine if a dependency is publicly available (such as an open-source dependency) or internal to the Java binary application during analysis. | ||
|
||
When you disable Maven search, {ProductShortName} at first tries to determine dependencies from the the JAR file's POM file (if any). If this method does not succeed, {ProductShortName} goes through the directory structure to determine dependencies. This method may not produce a reliable dependency classification since the package structure can differ from what is expected by {ProductShortName}. You may see more dependencies in the `dependencies.yaml` file because some dependencies may be wrongly classified as internal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of noting dependencies in dependencies.yaml
, it would probably be better to mention this could cause more incidents vs using maven search.
Signed-off-by: Prabha Kylasamiyer Sundara Rajan <[email protected]>
f7ed6c3
to
2ef8157
Compare
JIRA
Version
Preview