mattcasters opened a new issue, #7547: URL: https://github.com/apache/hop/issues/7547
### What would you like to happen? Since Apache Hop is an ASF project, we already have access to the premier open-source artifact hosting infrastructure. The ASF provides a managed Sonatype Nexus instance (repository.apache.org) that automatically syncs with Maven Central. How it works: Instead of bundling the plugins into the final assembly zip, we change the packaging of our plugins to separate, standalone artifacts (e.g., .zip or .jar files with their dependencies shaded or explicitly targeted). During your standard ASF release process, these are deployed to Maven Central as distinct modules. How Hop handles it: we can build a lightweight "Plugin Manager" or "Marketplace" UI/CLI inside Hop. When a user wants a plugin, Hop uses a standard HTTP client or Maven resolver library to fetch the plugin zip directly from Maven Central using its GAV (Group, Artifact, Version) coordinates, then unpacks it into the local plugins/ directory. Why it’s great: Zero infrastructure management for our team, massive global bandwidth via Central's CDN, and perfect compliance with the ASF lifecycle. ### Issue Priority Priority: 2 ### Issue Component Component: Other -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
