You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that could be implemented similar like the MavenPomFeatureModel, but instead of only considering dependencies it could consider the dependencies in the dependencyManagment section.
The question is, should standard dependencies then considered as well?
So my preferred solution would be that everything works as before, but we have a new delectable scope of import that then considered the dependencyManagment then user can decide if it is a "pom" or a "bom" (because they are both of type pom ...).
So my preferred solution would be that everything works as before, but we have a new delectable scope of import that then considered the dependencyManagment then user can decide if it is a "pom" or a "bom" (because they are both of type pom ...).
Sounds good. One can already select the import-scope, but it is not doing the expected things. I assume I just have to implement it.
Currently one could add a pom type already but this will not work for "bom" poms where only managed dependencies are declared.
The text was updated successfully, but these errors were encountered: