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
Please document this process on readme so its known how to use. Further explain instructions to install software or rewrite it so its not using yet additional software to update libraries. My preference would be to use a proper bot (renovate) and configure it to group them (simple).
The text was updated successfully, but these errors were encountered:
It was doing more than just keeping them up-to-date. What it was specifically doing was deleting them from the POM, and then automatically resolving the version ranges specified in the JDT core POM for all its transitive dependencies, and re-adding them to the POM. This way, it didn't just update them, but updated them to only within the range supported by upstream JDT core, and also removed any that would have been removed upstream. Renovate couldn't do that.
The only software it required was software that's available out of the box on *nix systems. It wasn't really intended to be used by everybody... just automation for me so I didn't have to manually run it when we bumped the JDT core library to the latest Eclipse. The description of it was in 1ac162a when it was added, and it takes no arguments. It just required running right after updating the JDT core dependency. Very simple.
In any case, it was a temporary workaround and we don't need it now because upstream doesn't use version ranges anymore, and it has already been deleted. So, we can close this issue.
Please document this process on readme so its known how to use. Further explain instructions to install software or rewrite it so its not using yet additional software to update libraries. My preference would be to use a proper bot (renovate) and configure it to group them (simple).
The text was updated successfully, but these errors were encountered: