[Feature]: goal to bulk upload protoc plugins from URLs to Maven repository

[ascopes]

Have been thinking about how many people in a locked down corporate environment may want to publish a protoc plugin found on GitHub or elsewhere to their internal Maven registries.

Given there are a bunch of standard classifiers we can use to auto-detect CPU architecture and OS without explicit configuration, perhaps we could define a new goal that allows users to specify a set of URLs for each architecture they need, and the goal downloads and extracts the artifacts before republishing them to Maven Central via the maven-deploy-plugin.

For example, perhaps this could be a packaging so users can define shell projects that have a predefined set of relevant goals configured automatically:

<project>
  <groupId>org.mycompany</groupId>
  <artifactId>protoc-gen-foobar</artifactId>
  <version>1.2.3</version>
  <packaging>thirdparty-protoc-plugin</packaging>

  <properties>
    <protobuf.thirdparty.plugin.url.windows.x86_64>zip:https://somesite.com/${project.version}/windows-amd64.zip!/protoc-gen-foobar.exe</protobuf.thirdparty.plugin.url.windows.x86_64>

    <protobuf.thirdparty.plugin.url.linux.x86_64>tar:gz:https://somesite.com/${project.version}/linux-amd64.tgz!/protoc-gen-foobar.exe</protobuf.thirdparty.plugin.url.linux.x86_64>
  </properties>

  <build>
    <plugins>
      <plugin>
        <groupId>io.github.ascopes</groupId>
        <artifactId>protobuf-maven-plugin</artifactId>
        <extensions>true</extensions>
      </plugin>
    </plugins>
  </build>
</project>

In this case, each URL could be fetched by a goal in this plugin for each URL the user specifies in config, and then marked as being attached to the build. The maven-deploy-plugin could then be further bound to the deploy phase so that mvn clean package deploy transfers the artifacts to the right place with the right classifiers.

The format of this is totally down for debate if it is considered to be useful enough to implement.

[ascopes]

@cdprete perhaps this would be of interest to your use case?

[cdprete]

Hello @ascopes.

Yes, on the paper, but in reality it won't work since that the download of those artifacts from those URLs will be blocked.

[ascopes]

Ah I see, that is a pain.

[cdprete]

Yep, that's why I've said I need that protoc-doc-gen to be mirrored into our Artifactory ;)