You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@baremaps.apache.org by "bchapuis (via GitHub)" <gi...@apache.org> on 2023/02/20 17:07:35 UTC

[GitHub] [incubator-baremaps] bchapuis commented on issue #492: Publish a first incubating release

bchapuis commented on issue #492:
URL: https://github.com/apache/incubator-baremaps/issues/492#issuecomment-1437327293

   @aalmiray Thanks a lot for reaching out and for your work on jreleaser. I'm getting familiar with the Apache guidelines and from what I understand the most important part of a release is the source code. The binaries, artifacts, etc. are provided as a convenient way to install the project, but they are not really considered as being part of the release. 
   
   Regarding your comment, from what I understand, I should use the maven assembly plugin to generate an archive containing the source code, and then use JReleaser and the `<files>` section to upload this artifact. Is that correct? What I was originally looking for was a way to do this with JReleaser.


-- 
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: commits-unsubscribe@baremaps.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org