Is your feature request related to a problem? Please describe.
I have used a common dir for all jdk versions extracted from zip versions and am using a .cmd file to switch between the different major releases, I did bascially the same when I still used Oracle installers, e.g. putting a version into c:\Tools\jdk\java-8-432 and replacing the dir with the new version each time. This is easily accomodated by the zip versions since they have a version directory as base dir in the archive.
Now for the update check that means that the custom paths change each time a minor version is replaced, which is easy to adapt, but would be more convenient if the custom paths would support wildcards and pick up all directories that it finds, e.g. using c:\Tools\jdk\jdk-*, this way both old and new versions would be picked up and when an old version is removed, it just disappears from the list
I'm sure that it's not a 'known-not-a-bug'
See: https://github.com/tushev/aojdk-updatewatcher/wiki/Known-not-a-bugs
[X] Yes
Describe the solution you'd like
I would like to be able to add path entries with 1 or more * wildcards that are expanded when starting the overview page based on the matching paths actually existing
Describe alternatives you've considered
I have coonsidered changing to paths not mentioning the minor version, but I kind of find that less clear.
I have considered writing an additional script to replace the path list in a config file (or what the program uses to store the paths) to automate the replacement of the paths
Additional context
n/a
Is your feature request related to a problem? Please describe.
I have used a common dir for all jdk versions extracted from zip versions and am using a .cmd file to switch between the different major releases, I did bascially the same when I still used Oracle installers, e.g. putting a version into c:\Tools\jdk\java-8-432 and replacing the dir with the new version each time. This is easily accomodated by the zip versions since they have a version directory as base dir in the archive.
Now for the update check that means that the custom paths change each time a minor version is replaced, which is easy to adapt, but would be more convenient if the custom paths would support wildcards and pick up all directories that it finds, e.g. using c:\Tools\jdk\jdk-*, this way both old and new versions would be picked up and when an old version is removed, it just disappears from the list
I'm sure that it's not a 'known-not-a-bug'
See: https://github.com/tushev/aojdk-updatewatcher/wiki/Known-not-a-bugs
[X] Yes
Describe the solution you'd like
I would like to be able to add path entries with 1 or more * wildcards that are expanded when starting the overview page based on the matching paths actually existing
Describe alternatives you've considered
I have coonsidered changing to paths not mentioning the minor version, but I kind of find that less clear.
I have considered writing an additional script to replace the path list in a config file (or what the program uses to store the paths) to automate the replacement of the paths
Additional context
n/a