2.0.7
Resolved issues
| Internal ID | Call ID | Description | Impact |
|---|---|---|---|
| EXTMVNHTTP-70 | - | Port new internal remediation policy from File System Extractor | Extraction levels are limited to two for dependent artifacts, no limit for parent artifacts. The total number of artifacts extracted using additional levels is limited to ten times the number of remediation artifacts (extracted at the base level), the first two additional levels are not started if this number is greater than three times the number of remediation artifacts. |
| EXTMVNHTTP-65 | - | Artifact with POM packaging extracting additional resources "JAR","War" and "Zip" files | The pom file with packaging POM (<packaging>POM</packaging>), does not extract additional resources "JAR","War" and "Zip" files. |
2.0.6
Resolved issues
| Internal ID | Call ID | Description | Impact |
|---|---|---|---|
| EXTMVNHTTP-61 | - | Replace the static thresholds to dynamic thresholds | Improve the internal remediation loop to at most 2 levels. Replace the static thresholds of 15 000 and 10 000 to dynamic thresholds computed from the initial number of required artifacts (e.g., as 10 times and 3 times this number). Consider a Maven version range of the form x.y as being [x.y,], to let the extractor and the validation engine choose the best fitting version |
2.0.5
CAST highly recommends that you use ≥ 2.0.6 where possible.
Resolved issues
| Internal ID | Call ID | Description | Impact |
|---|---|---|---|
| EXTMVNHTTP-57 | - | Add a limit to the recursive extraction of the Maven dependent artifacts. | The number of artifacts that will be extracted for each recursive loop is limited to 10000. The maximum number of artifacts that will be extracted for all recursive loops is 15000. |
2.0.4
CAST highly recommends that you use ≥ 2.0.6 where possible.
Updates
EXTMVNHTTP-52 - Extract artifact with a version range
The extractor has been updated to correctly extract artifacts when a given dependency has a version number in a range. For example, given the following code, the extractor should take the best available version:
<dependency> <groupId>xalan</groupId> <artifactId>xalan</artifactId> <version>[2.4.1,2.4.2]</version> </dependency>
Resolved issues
| Internal ID | Call ID | Description | Impact |
|---|---|---|---|
| EXTMVNHTTP-51 | - | Extracts recursively the Maven dependent artifacts. | No impact on packaging results, however, the number of remediation loops has been reduced to improve performance. |
2.0.3
CAST highly recommends that you use ≥ 2.0.6 where possible.
Resolved issues
| Internal ID | Call ID | Description |
|---|---|---|
| EXTMVNHTTP-46 | - | Extracts recursively the POM parent artifacts |
| EXTMVNHTTP-41 | - | WAR files are not picked up by the DMT2.0.2 |
2.0.2
Resolved issues
| Internal ID | Call ID | Description |
|---|---|---|
| EXTMVNHTTP-45 | 13793 | The Automatic remediation step in packaging take long time for Maven packaging |
| EXTMVNHTTP-42 | - | Single connection to improve the performance |
2.0.1
Resolved issues
| Internal ID | Call ID | Description |
|---|---|---|
| EXTMVNHTTP-40 | - | Maven HTTP Extractor raised a null pointer Exception |
2.0.0
Updates
- The Classifier string is now supported for specifying Artifacts (see below).
- This extension is shipped and installed (in a from scratch installation scenario and in an upgrade scenario) by default with CAST AIP ≥ 8.3.3.
