Change Details

As far as the latest discussion and development went so far, this means: - [ ] maven exporter/indexer [1] - [x] D6395: maven lister - [ ] D6396: maven (package) loader [1] in charge of extracting information that the maven lister will be able to list properly The maven index exporter is in charge of downloading all index files, extracting and exporting them as raw text files. It is executed on a separate server and relies on a Docker image. Once the text file is generated, it has to be made available on a local http server so the lister can fetch it and start the parsing (extract src jars and scm info). The full export process is documented in [1] and a list of maven repositories that can be used/extracted with the tool is provided at [2]. The repository also provides a list of downloadable text files [3] ready-to-use by the lister. One can simply uncompress the tar.bz2 on the local http server and run the lister for tests. [1] https://github.com/borisbaldassari/maven-index-exporter [2] https://github.com/borisbaldassari/maven-index-exporter/tree/main/docs/maven_repositories [3] https://icedrive.net/1/01BQpqC6rA

As far as the latest discussion and development went so far, this means: - [ ] D6740: maven exporter/indexer [1] - [x] D6395: maven lister - [x] D6396: maven (package) loader - [ ] Docker diff that connects the tooling ^ together [1] in charge of extracting information that the maven lister will be able to list properly The maven index exporter is in charge of downloading all index files, extracting and exporting them as raw text files. It is executed on a separate server and relies on a Docker image. Once the text file is generated, it has to be made available on a local http server so the lister can fetch it and start the parsing (extract src jars and scm info). The full export process is documented in [1] and a list of maven repositories that can be used/extracted with the tool is provided at [2]. The repository also provides a list of downloadable text files [3] ready-to-use by the lister. One can simply uncompress the tar.bz2 on the local http server and run the lister for tests. [1] https://github.com/borisbaldassari/maven-index-exporter [2] https://github.com/borisbaldassari/maven-index-exporter/tree/main/docs/maven_repositories [3] https://icedrive.net/1/01BQpqC6rA

As far as the latest discussion and development went so far, this means: - [ ] D6740: maven exporter/indexer [1] - [x] D6395: maven lister - [ - [x] D6396: maven (package) loaderder - [ ] Docker diff that connects the tooling ^ together [1] in charge of extracting information that the maven lister will be able to list properly The maven index exporter is in charge of downloading all index files, extracting and exporting them as raw text files. It is executed on a separate server and relies on a Docker image. Once the text file is generated, it has to be made available on a local http server so the lister can fetch it and start the parsing (extract src jars and scm info). The full export process is documented in [1] and a list of maven repositories that can be used/extracted with the tool is provided at [2]. The repository also provides a list of downloadable text files [3] ready-to-use by the lister. One can simply uncompress the tar.bz2 on the local http server and run the lister for tests. [1] https://github.com/borisbaldassari/maven-index-exporter [2] https://github.com/borisbaldassari/maven-index-exporter/tree/main/docs/maven_repositories [3] https://icedrive.net/1/01BQpqC6rA