You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/11/30 13:06:49 UTC
[GitHub] [camel-quarkus] zregvart opened a new issue #2045: Create ASF distribution
zregvart opened a new issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045
We need a binary distribution to point to as a download from the website. The binary and the source distribution needs to be distributed via Apache mirrors.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] aldettinger commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
aldettinger commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-738164477
The source distribution is currently managed [manually](https://github.com/apache/camel-quarkus/commit/2b72581fe6ffec2dc8dce49ed2daf0002db53d16).
Still some improvement are possible:
- create releases on reporter.apache.org
https://reporter.apache.org/addrelease.html?camel
- upload release binaries to dist.apache.org
- group issues for a release, practice varies, especially for
GitHub driven sub-projects, we need to allow users to see what issues
are fixed in what release, maintaining a change log is good, but it's
not parsable and thus of no use on the website (or any other similar
use case)
Documentation references:
- https://www.apache.org/legal/release-policy.html
- https://infra.apache.org/release-publishing.html
- https://infra.apache.org/release-distribution.html
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] zregvart commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
zregvart commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-743489810
> Any hints @zregvart what the binary distribution should actually contain for Camel Quarkus?
For Camel (core) we do .zip and .tar.gz containing the built jars, does that make sense for Camel Quarkus?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] jamesnetherton closed issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
jamesnetherton closed issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] davsclaus commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
davsclaus commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-744329742
There is no value really for 99% of users. Its for offline / restricted internet users where they need to download a zip with JARs and then put together all the JARs they need themselves. The camel "core" zip is also just only the Camel JARs and has been like that always.
We just need the same for camel-quarkus.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] zregvart commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
zregvart commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-744343330
I guess if folk mainly depend on Maven central to pull in binaries, along with dependencies, should we stop distributing binaries as a whole? Perhaps we can take this to the users/dev mailing lists and see what feedback we gather there.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga edited a comment on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
ppalaga edited a comment on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-744326575
> For Camel (core) we do .zip and .tar.gz containing the built jars, does that make sense for Camel Quarkus??
I am struggling to figure out how such a bag of jars could be used for creating a Camel Quarkus application. To be able to use those jars, users need them in some sort of a Maven repo. In other words, zipped Maven repo is perhaps the only kind of binary distribution that could have some value for the users. But maybe I am overestimating the importance of the usability for the end users. Or maybe somebody sees some other elegant way how to fulfill the ASF rules and at the same time deliver some value to the end 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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-743416726
We group issues using [GH milestones](https://github.com/apache/camel-quarkus/milestones?state=closed) for quite some time.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-743440942
Any hints @zregvart what the binary distribution should actually contain for Camel Quarkus?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-744372751
Yes, creating a Camel Quarkus app is very Maven-repo centric. Whether in Maven or in Gradle based apps, the parts of the application are declared in terms of Maven artifact coordinates and the Quarkus toolling uses given tool's resolution mechanisms to get those parts.
Note that its impossible to assemble a Camel Quarkus app without Quarkus build Mojo (or the corresponding Gradle task), because that's where the Augmentation (build time analysis and transformation of the application code) is happening.
So there is no way how a user could "put together" an app by moving around jars we give him in a zip file. Unless of course, he installs the jars into his local Maven repo.
Zipped Maven repo is actually a perfect match for the Quarkus process, even in offline environments: it can be unzipped locally and declared as an additional repo in the application's build.gradle, pom.xml or in settings.xml. In that way, the Quarkus tooling can find the necessary artifacts where it expects them.
Having said that I would not mind having a look how we could provide a zipped maven repo containing our binary jars and nothing else.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] aldettinger commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
aldettinger commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-754505951
The release creation on reporter.apache.org has been added to the [further steps section](https://camel.apache.org/camel-quarkus/latest/contributor-guide/release-guide.html#_further_steps) of the release process.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-744326575
> For Camel (core) we do .zip and .tar.gz containing the built jars, does that make sense for Camel Quarkus??
I am struggling to figure out how such a bag of zips could be used for creating a Camel Quarkus application. To be able to use those jars, users need them in some sort of a Maven repo. In other words, zipped Maven repo is perhaps the only kind of binary distribution that could have some value for the users. But maybe I am overestimating the importance of the usability for the end users. Or maybe somebody sees some other elegant way how to fulfill the ASF rules and at the same time deliver some value to the end 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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] jamesnetherton commented on issue #2045: Create ASF distribution
Posted by GitBox <gi...@apache.org>.
jamesnetherton commented on issue #2045:
URL: https://github.com/apache/camel-quarkus/issues/2045#issuecomment-772426958
I think we can close this one now (feel free to reopen if not):
https://issues.apache.org/jira/browse/CAMEL-16038
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org