Post

1 follower Follow
0

Performance issues - DMT - HTTP Maven package

Starting from 8.3.x, the DMT is able to remediate some alerts automatically when JAVA resource packages exist. The step that performs this remediation is called "Automatic Remediation". This is a Remediation loop. Before 8.3.11, the loop has no limit and can retrieve all the required dependencies, but the size of the output can be huge. For only one maven project in the source code, you may get more than 1 GB of artifact retrieved.

Since 8.3.11, the Remediation loop is limited to 3 level, then the artifacts retrieved are enough to avoid missing links during analysis. More over, the dependencies of Maven Packages are remediated during the maven extraction which save considerable time during the full package. 

Please sign in to leave a comment.