You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@flagon.apache.org by "rc10house (via GitHub)" <gi...@apache.org> on 2025/02/27 19:57:36 UTC
[I] 2.4.0 release doesn't include build directory (flagon)
rc10house opened a new issue, #58:
URL: https://github.com/apache/flagon/issues/58
When downloading the `2.4.0` release as a `.zip` archive. The contents doesn't include a `build/` directory. @Jyyjy is this the intended behavior?
--
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: notifications-unsubscribe@flagon.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@flagon.apache.org
For additional commands, e-mail: notifications-help@flagon.apache.org
Re: [I] 2.4.0 release doesn't include build directory (flagon)
Posted by "Jyyjy (via GitHub)" <gi...@apache.org>.
Jyyjy commented on issue #58:
URL: https://github.com/apache/flagon/issues/58#issuecomment-2689284497
I wouldn't say it's intended, but I don't think excluding build/ violates [Apache policy](https://www.apache.org/legal/release-policy.html#artifacts). I'm not opposed to changing the release process such that future releases include build/ in src, but I would oppose patching 2.4.0 just to include build/.
There's two main release artifacts, the src archive and the bin archive. And there's two main places where you would download these artifacts, [Apache](https://downloads.apache.org//flagon/useralejs/2.4.0/) and [GitHub](https://github.com/apache/flagon-useralejs/releases/tag/2.4.0).
I see that there is no build/ in the src artifacts in either of these places. And the bin artifact is missing from the GitHub tag artifacts. There is an additional source code artifact generated by default in the GitHub tag artifacts that contains build/ because it is a simple snapshot of the repo.
--
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: notifications-unsubscribe@flagon.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@flagon.apache.org
For additional commands, e-mail: notifications-help@flagon.apache.org
Re: [I] 2.4.0 release doesn't include build directory (flagon)
Posted by "brucearctor (via GitHub)" <gi...@apache.org>.
brucearctor closed issue #58: 2.4.0 release doesn't include build directory
URL: https://github.com/apache/flagon/issues/58
--
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: notifications-unsubscribe@flagon.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@flagon.apache.org
For additional commands, e-mail: notifications-help@flagon.apache.org
Re: [I] 2.4.0 release doesn't include build directory (flagon)
Posted by "brucearctor (via GitHub)" <gi...@apache.org>.
brucearctor commented on issue #58:
URL: https://github.com/apache/flagon/issues/58#issuecomment-4954142483
Closing as by-design. Apache releases are **source releases** — the ASF distributes source tarballs, not pre-built binaries. The `build/` directory is intentionally excluded from the release archive. To get built artifacts, use the npm package: `npm install flagon-userale`. We'll add a note about this to the release documentation (#134) so it's clearer for future users.
--
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: notifications-unsubscribe@flagon.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@flagon.apache.org
For additional commands, e-mail: notifications-help@flagon.apache.org