rangareddy opened a new issue, #870:
URL: https://github.com/apache/incubator-xtable/issues/870

   ### Describe the request
   
   On the [Downloads page](https://xtable.apache.org/releases/downloads) 
(`website/releases/downloads.mdx`), each release currently lists only:
   
   - **Source Release** (`.src.tgz` with `.asc` / `.sha512`)
   - **Release Notes**
   - **Maven Search** link (to central.sonatype.com)
   
   There is **no direct path/link to the XTable artifact (binary) jars**. Users 
who just want the built jars — especially the runnable bundled utilities jar — 
have to go through Maven search and navigate to find them.
   
   ### Proposal
   
   Under **each release** on the Downloads page, add the path/links to the 
published XTable artifact jars (convenience binaries on Maven Central), e.g.:
   
   - The Maven Central directory for the release, e.g.
     `https://repo1.maven.org/maven2/org/apache/xtable/`
   - The runnable bundled CLI jar, e.g.
     
`https://repo1.maven.org/maven2/org/apache/xtable/xtable-utilities_2.12/<version>/xtable-utilities_2.12-<version>-bundled.jar`
   - (optionally) the other published artifacts: `xtable-api`, 
`xtable-core_2.12`, `xtable-hudi-support-utils`, etc.
   
   Example for `0.3.0-incubating`:
   
   ```
   ### Release 0.3.0-incubating
   * Source Release: ... (unchanged)
   * Binary Artifacts: [Maven 
Central](https://repo1.maven.org/maven2/org/apache/xtable/) —
     bundled CLI: 
[xtable-utilities_2.12-0.3.0-incubating-bundled.jar](https://repo1.maven.org/maven2/org/apache/xtable/xtable-utilities_2.12/0.3.0-incubating/xtable-utilities_2.12-0.3.0-incubating-bundled.jar)
   * Release Notes: ... (unchanged)
   * Maven Search: ... (unchanged)
   ```
   
   ### Notes
   
   - The official ASF release remains the **source** release; the jars are 
convenience binaries published to Maven Central, which is acceptable to link 
from the Downloads page (as many ASF projects do).
   - Keep the source-release link and signatures/checksums prominent; the 
artifact-jar links are an addition, not a replacement.
   - This should be applied consistently to each release entry 
(0.2.0-incubating, 0.3.0-incubating, and future releases), and ideally 
documented in the release process so new releases include the artifact-jar 
links.
   


-- 
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]

Reply via email to