-
Notifications
You must be signed in to change notification settings - Fork 66
Bayesian Stack Report: does not update during pipeline runs #207
Comments
Che while editing pom.xml |
A gist of the Jenkins output |
This issue was moved to fabric8-ui/fabric8-recommender#242 |
@burrsutter because of the scope "import", the dependency logback-core 1.1.10, the stack analysis could not detect the appropriate reference stack and hence no recommendations were generated. Removing the scope should get you the recommendation that you are looking for. |
Import removal was the trick...now just make the Che and build/pipeline experience the same, I should not get a warning/recommendation in one but not the other - at least on the same exact thing in the pom.xml |
@burrsutter can we close this issue? |
Closing this issue as it appears resolved. @burrsutter please reopen if needed. |
https://screencast.com/t/gATQgadjjBV
shows 2 deps but there are 3, I added one, a bad one
https://github.com/burrsutter/vertxbasic23/blob/master/pom.xml#L44
and no recommendations are offered, even with the bad dep added to my pom.xml
Note: this dep is flagged in Che, just not during the pipeline run
The text was updated successfully, but these errors were encountered: