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
Currently Maven updater can only substitute elements in pom.xml, however, we may want to add new section (for example <dependencyManagment/>) to pom.xml for guided remediation.
The text was updated successfully, but these errors were encountered:
#989
For the purpose of overriding dependency requirements, we may need to
add new dependencies or even dependency management section to pom.xml.
This PR:
- moves the patch generation from suggester to updater
- before writing patches, prepare dependency and property patches
- when updating dependencies, if a dependency is not from the base
project, we should add a new section
- when updating a project, if dependency management is not updated and
there are patches from dependency management, add a new dependency
management section
- marks the parent dependency patch to have type "pom"
TODOs:
- need to find a way to differentiate patches for guided remediation or
general updates, since we should not add new sections for general
updates (using `OrigRequire` seems reasonable)
- make the indentation for the new sections configuration, now defaults
to a white space
Currently Maven updater can only substitute elements in pom.xml, however, we may want to add new section (for example
<dependencyManagment/>
) to pom.xml for guided remediation.The text was updated successfully, but these errors were encountered: