I refactored how sormuras/modules scans and presents module name-uri pairs.
This pro code here...
|
private static void updateModuleNameList() { |
|
var moduleNameListURI = uri("https://raw.githubusercontent.com/sormuras/modules/master/module-maven.properties"); |
|
var resolverResourceFile = location("src/main/resources/com.github.forax.pro.plugin.resolver/com/github/forax/pro/plugin/resolver/module-maven.properties"); |
|
|
|
try { |
|
var tmpDir = createTempDirectory("pro"); |
|
download(moduleNameListURI, tmpDir); |
|
System.out.println("download " + moduleNameListURI); |
|
createDirectories(resolverResourceFile.getParent()); |
|
move(tmpDir.resolve("module-maven.properties"), |
|
resolverResourceFile, |
|
REPLACE_EXISTING); |
|
} catch(IOException | UncheckedIOException e) { |
|
System.err.println("can not update module name list " + e.getMessage()); |
|
} |
|
} |
...still works, but refers to a stalled (read: no longer daily updated) module-maven.properties file.
Now, daily updates of the new database are presented in two ways:
Also, stable versions are collected here: https://github.com/sormuras/modules/releases
I refactored how sormuras/modules scans and presents module name-uri pairs.
This pro code here...
pro/src/main/java/com.github.forax.pro.bootstrap/com/github/forax/pro/bootstrap/Bootstrap.java
Lines 185 to 200 in 1dac8c7
...still works, but refers to a stalled (read: no longer daily updated)
module-maven.propertiesfile.Now, daily updates of the new database are presented in two ways:
module:uriformat: modules.propertiesAlso, stable versions are collected here: https://github.com/sormuras/modules/releases