Details
-
Story
-
Resolution: Unresolved
-
Major
-
None
-
5.1.1.Final
-
None
-
False
-
False
-
Undefined
-
---
-
---
Description
The analysis report showcases totally different story points if the application includes dependencies ahead of time. For example, the sample application is Spring Boot Petclinic microservices(https://github.com/spring-petclinic/spring-petclinic-microservices) then you can run two analysis reports:
1) Using a zip file thaat doesn't include the target directory.
Target: quarkus / Source: springboot
The report showcases only 1 story point as below:
2) Run "mvn package"
Target: quarkus / Source: springboot
The report showcases only 418 story points as below:
It means the end-user probably assumes all dependencies that are specified in pom.xml should be analyzed when the report is issued. It turns out that it doesn't so I think we need to add this feature by default. In the meantime, we also need to add this to the document(https://access.redhat.com/documentation/en-us/migration_toolkit_for_applications/5.1/).