Re: Website build issues

Thanks James for fixing this so quickly. The build is back to normal. Thanks again, Gregor On Thu, Apr 25, 2024 at 12:31 PM James Netherton wrote: > > Hi Gregor, > > I reverted the offending change. Hopefully it fixes things. > > -- > James > > On Thu, 25 Apr 2024 at 11:11, Gregor Zurowski > wr

Re: Website build issues

Hi Gregor, I reverted the offending change. Hopefully it fixes things. -- James On Thu, 25 Apr 2024 at 11:11, Gregor Zurowski wrote: > Hi, > > I am about to release Camel 4.4.2 and getting the following errors > building the website: > > ``` > [check:html ] > > /home/jenkins/712657a4/works

Re: Website build issues

I guess James Netherton could help on this. Il gio 25 apr 2024, 12:11 Gregor Zurowski ha scritto: > Hi, > > I am about to release Camel 4.4.2 and getting the following errors > building the website: > > ``` > [check:html ] > > /home/jenkins/712657a4/workspace/Camel_Camel.website_main_2/camel

Re: Website build | Docker Registry Authentication Fails

Hi, most likely rate limiting towards Docker Hub, a new build seems to be running okay now[1] zoran [1] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/1405/console On Mon, Nov 20, 2023 at 2:52 PM Gregor Zurowski wrote: > > Hi Everyone, > > I am getting the following error on

Re: Website build error

Thanks a lot for fixing the issue. On Fri, Oct 27, 2023 at 4:14 PM Claus Ibsen wrote: > > Hi Gregor > > The website build is fixed now and the 4.0.2 release is on the front page. > Thanks for the help Zoran. > > > > On Fri, Oct 27, 2023 at 1:37 PM Gregor Zurowski > wrote: > > > Hi Everyone: > >

Re: Website build error

Hi Gregor The website build is fixed now and the 4.0.2 release is on the front page. Thanks for the help Zoran. On Fri, Oct 27, 2023 at 1:37 PM Gregor Zurowski wrote: > Hi Everyone: > > The current website build is breaking with the following error: > > ``` > > /home/jenkins/712657a4/workspac

Re: Website build error

Hi Thanks I wonder what that can be. I have not seen such error before. Zoran in case you are listening then any help is appreciated. On Fri, Oct 27, 2023 at 1:37 PM Gregor Zurowski wrote: > Hi Everyone: > > The current website build is breaking with the following error: > > ``` > > /home/jenk

Re: Website build error

Hi Zoran, Thanks for fixing the issue. I confirm that the build went through successfully. Thanks again Gregor On Fri, May 5, 2023 at 3:04 PM Zoran Regvart wrote: > > Hi Gregor, > should be fixed now[1][2], > > zoran > > [1] > https://github.com/apache/camel-website/commit/30806acd4858fa133dab

Re: Website build error

Hi Gregor, should be fixed now[1][2], zoran [1] https://github.com/apache/camel-website/commit/30806acd4858fa133dabfd715cb8d68b805ec386 [2] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/1214/ On Fri, May 5, 2023 at 11:44 AM Gregor Zurowski wrote: > > Hi Everyone: > > I am s

Re: Website build stuck

Hi Thanks Zoran I stopped and delete these PR jobs - its a waste of time when people work on a draft PR. The website is just updated with the 3.16 release blurb. On Mon, Mar 28, 2022 at 11:30 AM Zoran Regvart wrote: > > Hi Cameleers, > This reminds me of the "Are we the baddies" sketch/meme[1]

Re: Website build stuck

Hi Cameleers, This reminds me of the "Are we the baddies" sketch/meme[1]. The reason why PR#800 is not built is because PR#809[2] is taking up all the CI resources. I do wish that branches are not pushed to camel-website git repository directly but built from forks using GitHub Actions. For branch

Re: Website build stuck

It's related to the other jobs. I don't think there is so much we could do. Don't know of there is an ongoing issue on Jenkins, but i don't think so Il lun 28 mar 2022, 10:27 Gregor Zurowski ha scritto: > Hi Everyone, > > I pushed some changes for the 3.16.0 release to the camel-website > reposi

Re: [Website] Ongoing problem with broken links in blog posts

I opened some issues... > On Feb 8, 2022, at 11:25 AM, Zoran Regvart wrote: > > Hi David & Cameleers, > > On Tue, Feb 8, 2022 at 7:57 PM David Jencks > wrote: >> We have a problem in a lot of blog posts that they link into the Antora >> generated docs. > > Ye

Re: [Website] Ongoing problem with broken links in blog posts

Hi David & Cameleers, On Tue, Feb 8, 2022 at 7:57 PM David Jencks wrote: > We have a problem in a lot of blog posts that they link into the Antora > generated docs. Yes this happens with increasing frequency and it is problematic > Many link to the “next” version of the docs which has two prob

Re: Website/doc changes after Camel 3.15.0 release

Hi Its not a LTS release so we are not going to cut a 3.15.1 release and when so, then this change is maybe not as important. However David may know if this can lead to problems with the website docs for the 3.15.0. The build can maybe use the 3.15.0 release tag from git to build the docs. On F

Re: Website build and CI error - overall improved a lot

Hi Cameleers, On Thu, Jan 13, 2022 at 6:07 AM David Jencks wrote: > — you have to build the site locally to see the built page that shows the > problem. Maybe Zoran knows a way, but I don’t know how to see the CI built > site if the build broke. We could, both on Jenkins* and on GitHub publis

Re: Website build and CI error - overall improved a lot

Indeed, very nice work, David. Thank you! On Wed, Jan 12, 2022 at 11:07 PM David Jencks wrote: > The spring-boot completeness check is a complicated thing…. Antora isn’t > really designed to run IT tests :-) > > Do you have any suggestions about how to make fixing such problems easier > or bette

Re: Website build and CI error - overall improved a lot

The spring-boot completeness check is a complicated thing…. Antora isn’t really designed to run IT tests :-) Do you have any suggestions about how to make fixing such problems easier or better documented? IIRC… — you get a build error that hints you should look at the spring boot index page.

Re: Website build and CI error - overall improved a lot

I'd also would like to add the following: the work done to document the interdependencies between subprojects is really really good and it helps a lot to understand where to look and how to fix something. Thanks a lot for that work David. Il giorno mer 12 gen 2022 alle ore 18:18 Claus Ibsen ha s

Re: [Website] POC local/partial builds

Hi David, thanks, I see your points, I have just a few acknowledgements/comments to add On Tue, Dec 21, 2021 at 7:42 PM David Jencks wrote: > > Hi Zoran, inline after extracting a couple of concrete proposals. > > 1. I’m going to open a website issue and PR for publishing the site manifest > wi

Re: [Website] POC local/partial builds

Hi Zoran, inline after extracting a couple of concrete proposals. 1. I’m going to open a website issue and PR for publishing the site manifest with the site, to enable immediate quick local “xref check” builds without needing to build the full site. 2. I’m going to open a website issue propos

Re: [Website] POC local/partial builds

Hi David, On Mon, Dec 20, 2021 at 10:23 PM David Jencks wrote: > > (Mostly general info, everyone please read) > > Hi Antonin, > > Sorry, somehow I missed this earlier! > > This work should help with that issue. I’m finding it really great for stuff > I do, it’s also really easy to adapt to cre

Re: [Website] POC local/partial builds

(Mostly general info, everyone please read) Hi Antonin, Sorry, somehow I missed this earlier! This work should help with that issue. I’m finding it really great for stuff I do, it’s also really easy to adapt to create a website PR for integrating lots of branch changes, cf. https://github.com

Re: [Website] POC local/partial builds

Hi David, Thanks a lot for your initiative. I hesitated to comment, both because I'm definitely foreign to the doc building process, and also as you did not mention Camel K. However, this, if I understand it correctly would help solving the following issue: https://github.com/apache/camel-k/is

Re: [Website] POC local/partial builds

Although there have been some comments on the associated PRs, and I’ve merged some of them, I’m slightly disappointed that there has been no discussion here, although there have been complaints about one of the problems this is intended to help with (broken website builds). I mention in future

Re: [Website] activemq URI syntax inconsistency

Perhaps there are (at least) two issues here: 1. How many colons? The “grammar” activemq:destinationType:destinationName can’t possibly under any interpretation yield a sentence with one colon, so something like activemq:[destinationType:]destinationName is more correct. 2. What are the destin

Re: [Website] activemq URI syntax inconsistency

Hi The correct syntax is in the json file, that are taken from the source code You are not correct about 2 colons, as when the option is left out (to use its default value) then the colon is not needed either, so you just use activemq:cheese when its a queue, and if you need topic then use act

Re: [Website] .htaccess Rewrite rules not working?

Just so this isn’t left dangling any longer, I came up with https://github.com/apache/camel-website/pull/673 which - uses Antora to generate the components/latest to components/3.13.x redirects, - Adds some modified redirectMatch rules to redirect components/ to components/3.13.x - merges this i

Re: Website updates after release

Master issue for the new version: https://github.com/apache/camel-website/issues/670 Release guide update PR: https://github.com/apache/camel/pull/6436 There were more parts than I thought! My PRs are on top of the PRs for https://github.com/apache/camel-website/pull/669: some of the PRs for #

Re: Website updates after release

Ok, thanks for taking care of this. I will review the documentation once you have a PR for it. Thanks, Gregor On Fri, Nov 12, 2021 at 3:38 PM David Jencks wrote: > > I’m happy to take care of this and update the instructions to the best of my > ability :-) > > > On Nov 12, 2021, at 3:03 AM, Gre

Re: Website updates after release

I’m happy to take care of this and update the instructions to the best of my ability :-) > On Nov 12, 2021, at 3:03 AM, Gregor Zurowski wrote: > > Hi Everyone: > > I wanted to apply the changes described in > https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release

Re: [website] Code highlighting

Hi David, On Tue, Nov 9, 2021 at 2:38 PM David Jencks wrote: > > > > > On Nov 9, 2021, at 12:02 AM, Zoran Regvart wrote: > > > > Hi David, > > > > On Tue, Nov 9, 2021 at 2:14 AM David Jencks > > wrote: > >> > >> (prompted by seeing a recent highlight.js upgrade in the website) > >> > >> Someon

Re: [website] Code highlighting

> On Nov 9, 2021, at 12:02 AM, Zoran Regvart wrote: > > Hi David, > > On Tue, Nov 9, 2021 at 2:14 AM David Jencks wrote: >> >> (prompted by seeing a recent highlight.js upgrade in the website) >> >> Someone pointed out shiki (https://shiki.matsu.io) on the Antora zulip >> recently and I wr

Re: [website] Code highlighting

Hi David, On Tue, Nov 9, 2021 at 2:14 AM David Jencks wrote: > > (prompted by seeing a recent highlight.js upgrade in the website) > > Someone pointed out shiki (https://shiki.matsu.io) on the Antora zulip > recently and I wrote an Antora extension to set it up and use it as the > (build time)

Re: Website build broken

Hi Cameleers, David, thanks for the fixes David, I still don't fully understand why `yarn workspaces foreach ... build` stopped working, but it seems like Yarn upgrade helped fix that. The website build is back to green. zoran On Wed, Nov 3, 2021 at 10:06 PM David Jencks wrote: > > I’ve proposed

Re: Website build broken

I’ve proposed a couple of PRs that do fix the website build and expose some info on this new springdoc thing, but I have no way to know how appropriate my new page is. https://github.com/apache/camel/pull/6375 https://github.com/apache/camel-spring-boot/pull/403 I’d suggest we apply the PRs and

Re: Website build broken

Why does eaf68b5767c827d3b463b061a6e8aebc062cce46 add this file? docs/components/modules/spring-boot/partials/openapi-java-starter.adoc Obviously I need to document better how the spring-boot docs work now. Where? The source adoc file shouldn’t exist either: where did it come from? Running the

Re: Website build broken

Maybe the copying isn’t configured quite right or the results of running it weren’t committed? IIRC it’s in the docs pom. I can investigate in a few hours. David Jencks > On Nov 3, 2021, at 6:43 AM, Claus Ibsen wrote: > > Hi > > There is a new spring-boot module called camel-springdoc-starte

Re: Website build broken

Hi There is a new spring-boot module called camel-springdoc-starter which could be the cause of this. I checked which -starter has .adoc files and its only ~/workspace/camel-spring-boot/components-starter main ❯ find . -name '*.adoc' ./camel-springdoc-starter/src/main/docs/springdoc-starter.adoc

Re: Website build broken

Please don’t remove that include, it’s there to tell you that someone made the camel spring boot system inconsistent. The inconsistency is that there’s a .json file for a starter with no corresponding documentation page. If you build the site locally and look at the spring boot index page you’

Re: [Website] .htaccess Rewrite rules not working?

Hi David, I'm a bit confused as to what are we trying to achieve here, redirect /latest to /, e.g.: /camel/components/latest to /camel/components/3.12.x Am I on point thus far? Some questions below: On Sun, Oct 31, 2021 at 4:26 PM David Jencks wrote: > > I looked into this a little bit, using t

Re: [Website] .htaccess Rewrite rules not working?

I looked into this a little bit, using the Antora 3 `latest-version-segment` feature: urls: redirect_facility: httpd latest_version_segment_strategy: redirect:from latest_version_segment: latest This generates the following in the generated .htaccess: Redirect 302 /manual/latest /manual R

Re: [Website] .htaccess Rewrite rules not working?

Hi Cameleers, ... and the redirects don't seem to work for camel-k, I'll have a fix shortly, for some reason I did not include camel-k in the tests... zoran On Fri, Oct 29, 2021 at 5:14 PM Zoran Regvart wrote: > > Hi Cameleers, > happy to say that the tests from the PR below pass on the live sit

Re: [Website] .htaccess Rewrite rules not working?

Hi Cameleers, happy to say that the tests from the PR below pass on the live site... zoran On Fri, Oct 29, 2021 at 3:39 PM Zoran Regvart wrote: > > Hi Cameleers, > I've created a PR that I think will solve the issues outlined in this thread: > > https://github.com/apache/camel-website/pull/659 >

Re: [Website] .htaccess Rewrite rules not working?

Hi David, On Fri, Oct 29, 2021 at 4:24 PM David Jencks wrote: > > Well, I agree and am considering how to make that happen. This redirects the > previous `latest` links to the same pages which are now at `next` so at least > we don’t have broken links (someone pointed one out on Zulip just now

Re: [Website] .htaccess Rewrite rules not working?

Hi Antonin, On Fri, Oct 29, 2021 at 4:10 PM Antonin Stefanutti wrote: > Naively / intuitively, I would assume 'latest' points to the latest released > version, while 'next' points to what is going to be the next version released. > > If I understand it correctly, 'latest' is redirected to 'next'

Re: [Website] .htaccess Rewrite rules not working?

Well, I agree and am considering how to make that happen. This redirects the previous `latest` links to the same pages which are now at `next` so at least we don’t have broken links (someone pointed one out on Zulip just now). Currently the latest released main camel version is 3.12.x. Taking

Re: [Website] .htaccess Rewrite rules not working?

Naively / intuitively, I would assume 'latest' points to the latest released version, while 'next' points to what is going to be the next version released. If I understand it correctly, 'latest' is redirected to 'next'. That being said, I appreciate it may be more complex to implement, if that

Re: [Website] .htaccess Rewrite rules not working?

Hi Cameleers, I've created a PR that I think will solve the issues outlined in this thread: https://github.com/apache/camel-website/pull/659 Please have a look, there is a test script there I'd be happy to hear if I missed a test case there, so I can add it and make sure the redirects work as exp

Re: [Website] .htaccess Rewrite rules not working?

Hi David & Claus, note the slash before the dollar sign on those, that means that the URL needs to end with a slash, so: $ curl -v https://camel.apache.org/components/latest gives 404, whereas: $ curl -v https://camel.apache.org/components/latest/ redirects to https://camel.apache.org/component

Re: [Website] .htaccess Rewrite rules not working?

Hi I also get an error page for /latest ~/workspace ❯ curl -i https://camel.apache.org/components/latest HTTP/2 404 On Fri, Oct 29, 2021 at 5:33 AM David Jencks wrote: > > Well, that’s not a very useful url… I tried > > % curl -k https://camel.apache.org/components/activemq-component.html >

Re: [Website] .htaccess Rewrite rules not working?

Well, that’s not a very useful url… I tried % curl -k https://camel.apache.org/components/activemq-component.html Page Not Found :: Apache Camel https://camel.apache.org/components/latest/activemq-component.html I also got the error page for % curl -k https://camel.apache.org/components/

Re: [Website] .htaccess Rewrite rules not working?

Hi David, I've tried the one on 1288 line: $ curl https://camel.apache.org/components/ 301 Moved Permanently Moved Permanently The document has moved https://camel.apache.org/components/next/";>here. and a couple below it, and it works on my end, a typo at your end? zoran On Wed, Oct 27, 20

Re: [Website and many projects] Please check the preview and review

Hi Zoran, > On Oct 26, 2021, at 12:58 AM, Zoran Regvart wrote: > > Hi David, > > On Mon, Oct 25, 2021 at 5:07 PM David Jencks wrote: >> The promise of pnp seems to be only partially fulfilled. If I run yarn >> build-all on a clean checkout, it fails because the stuff in >> antora-ui-camel/.

Re: [Website] Preview of unversioned manual, and 'next' for prerelease versions

Hi This looks good to me. One nitpick would be to spell prerelease as pre-release as then its IMHO a bit nicer to read. On Tue, Oct 26, 2021 at 7:49 AM David Jencks wrote: > > Please take a look at the preview for > https://github.com/apache/camel-website/issues/642 at > https://pr-654--camel

Re: [Website and many projects] Please check the preview and review

Hi David, On Mon, Oct 25, 2021 at 5:07 PM David Jencks wrote: > The promise of pnp seems to be only partially fulfilled. If I run yarn > build-all on a clean checkout, it fails because the stuff in > antora-ui-camel/.yarn/unplugged is for linux, not macOS. I have to run yarn > workspaces for

Re: [Website and many projects] Please check the preview and review

Hi Zoran, Many thanks for fixing this. Your explanation is what I thought should be happening but…. The yarn docs indicate that pnp is supposed to be the default strategy for .yarnrc nodeLinker, however when I run yarn install it adds node_modules and removes .pnp.js. If I explicitly set nod

Re: [Website and many projects] Please check the preview and review

Hi David, I think the issue should be fixed now[1]. The goal of Yarn cache as implemented using PnP is to maintain a hashed artifact of the dependency in `.yarn/cache`, so any time a dependency is changed a corresponding change needs to be made in `.yarn/cache`, for this running `yarn install` is a

Re: [Website and many projects] Please check the preview and review

I opened Yarn cached dependencies are not correct for Jenkins build, and there are no instructions on how to update them to more officially ask Zoran for help on this. I can come up with something that makes the jenkins build work, but it

Re: [Website and many projects] Please check the preview and review

I’m afraid Zoran will have to fix this. I’m totally confused by what yarn is doing. - mvn approach: getting back to a git clean state, running mvn clean package appears to be using npm 10 and yarn 1.14 and quickly errors. - yarn approach: david@mbp2 camel-website % yarn --version 2.4.0 Runni

Re: [Website and many projects] Please check the preview and review

Something is dreadfully wrong with the jenkins website build. It looks as if the jenkins build is not using the updated indexer and jenkins extensions. I don’t really understand how the yarn pnp stuff works, and I did not update any of the yarn caches…. I’m a bit scared off by stuff like this

Re: [Website and many projects] Please check the preview and review

Hi The default value is not yet appearing. On Sat, Oct 23, 2021 at 10:03 AM Zoran Regvart wrote: > > Hi David, > everything looks good, thank you for this effort! > > zoran > > > On 22 Oct 2021, at 02:45, David Jencks wrote: > > > > I’ve prepared a website update to the recent incompatible-synt

Re: [Website and many projects] Please check the preview and review

Hi David, everything looks good, thank you for this effort! zoran > On 22 Oct 2021, at 02:45, David Jencks wrote: > > I’ve prepared a website update to the recent incompatible-syntax upgrade of > my indexer and jsonpath Antora extensions that build most of the tables and a > lot of content.

Re: [Website and many projects] Please check the preview and review

Hi David It's massive work you have done, much appreciated. Browsed the pages a bit and looks fine. Go ahead with the merges. For camel-quarkus we should only show for its latest release according to the download page. And then "prerelease" if possible. On Fri, Oct 22, 2021 at 2:45 AM David Je

Re: [Website] Spring-boot errors or mistakes

Done, in my spring boot *-new-syntax branches. I did a full build on main-new-syntax which passed, I can do at least one more branch overnight and while I’m getting ready to create the other 13 (?) PRs. The site preview should be attached to https://github.com/apache/camel-website/pull/648. D

Re: [Website] Spring-boot errors or mistakes

Hi David Yes you are correct, go ahead to remove/fix those tests On Tue, Oct 19, 2021 at 10:54 PM David Jencks wrote: > > Tests in error: > > CamelDebeziumCommonTest.org.apache.camel.itest.springboot.CamelDebeziumCommonTest > » Runtime > org.apache.camel.itest.springboot.CamelHazelcastTest.c

Re: [Website] Spring-boot errors or mistakes

Tests in error: CamelDebeziumCommonTest.org.apache.camel.itest.springboot.CamelDebeziumCommonTest » Runtime org.apache.camel.itest.springboot.CamelHazelcastTest.componentTests(org.apache.camel.itest.springboot.CamelHazelcastTest) Run 1: CamelHazelcastTest>AbstractSpringBootTestSupport.startS

Re: [Website] Spring-boot errors or mistakes

And what integration test failures do you see when they are removed? eg maybe make sure that empty folders are removed etc, as the integration test is some voodoo magic Nicola did that creates a spring boot project per starter to see if it can install and startup spring boot, and for some it also

Re: [Website] Spring-boot errors or mistakes

Hi Yeah these starters are not in use and should be removed camel-debezium-common-starter http-common-starter jetty-common-starter On Mon, Oct 18, 2021 at 8:34 PM David Jencks wrote: > > I can easily remove the empty starter json files, but if e.g. > camel-debezium-common-starter isn’t a star

Re: [Website] Spring-boot errors or mistakes

I can easily remove the empty starter json files, but if e.g. camel-debezium-common-starter isn’t a starter, what is it? Removing the 3 starter projects from camel-spring-boot results in integration test failures. Does some other process install these as dependencies as appropriate? Are they

Re: [Website] Spring-boot errors or mistakes

Hi The -common JARs are not starters, and they should not be listed. On Mon, Oct 18, 2021 at 7:45 AM David Jencks wrote: > > Locally I got the ability to show unused starter json files working, and > fixed the obvious problems: > > avro-rpc was using avro > paho-mqtt5 was using paho > in 3.7.x,

Re: [Website] Spring-boot errors or mistakes

Locally I got the ability to show unused starter json files working, and fixed the obvious problems: avro-rpc was using avro paho-mqtt5 was using paho in 3.7.x, grape and joor were set up wrong. There are still some “starters” i’m not sure about: debezium-common http-common jetty-common In a p

Re: [Website] Spring-boot errors or mistakes

They are part of the camel-core-starter, although it’s hard to find the 2 options per language among the 147 options for the starter. This suggests that, for starters that encompass more than one component, it would be useful to only show the options relevant to that component on the component

Re: [Website] Spring-boot errors or mistakes

There’s at least one problem…. (also asked on zulip) Are camel-core-languages actually part of camel-spring-boot? They are listed in the table in "list of starters" but with an artifactid of "camel-base" which isn't a starter. The current site doesn't have autoconfiguration info for them either

Re: [Website] camel-spring-boot docs

I’ve implemented (3) and (4) on all active camel-spring-boot branches, I think they are pretty much ready to merge. Discussion is on another thread, "[Website] Spring-boot errors or mistakes” I don’t think I have anything else to say on this thread. Thanks David Jencks > On Oct 7, 2021, at 3:

Re: [Website] Spring-boot errors or mistakes

The part of this work I’m ready for now is done, except for some commit-squashing and dealing with check style errors :-) Preview at https://pr-644--camel.netlify.app I seem to only be able to write AsciiDoc by now…. :-) Here’s a list of the differences be

Re: [Website] Spring-boot errors or mistakes

On Mon, Oct 11, 2021 at 8:07 AM David Jencks wrote: > > I’ve been working on generating the spring-boot autoconfig info from the json > files generated during the spring-boot build, and the spring boot “list.adoc” > tables using the indexer extension (like the components tables are generated). >

Re: [Website] Spring-boot errors or mistakes

Hi David, On Mon, Oct 11, 2021 at 8:07 AM David Jencks wrote: [snip] > Does this seem reasonable? Very much. And thank you for this and other efforts you're leading on the docs, I'm a bit preoccupied with other work so apologies for not reviewing/supporting this. zoran -- Zoran Regvart

Re: [Website] camel-spring-boot docs

(1) and (2) are now completely implemented on all active camel-spring-boot branches. I’m working on (3). David Jencks > On Oct 2, 2021, at 6:02 PM, David Jencks wrote: > > I went ahead and implemented the first two of these in main “latest” > branches. Other than removing 324 unreferenced an

Re: Website build problem??? Apparently a transient failure

I tried again and the CI build seems to work, so perhaps this was a transient network problem. David Jencks > On Oct 7, 2021, at 10:46 AM, David Jencks wrote: > > I’m not sure if I caused this problem or not… if I did I have no idea how. > > I apologize for merging my 2 PRs before checking th

Re: [Website] Updating after a release

I’ve written a draft of instructions on how to update the docs/website after a camel/camel-karaf/camel-spring-boot release: https://github.com/apache/camel/pull/6215 I’ve also applied these instructions (retroactively in some cases) to all the active camel-karaf and camel-spring-boot branches:

Re: [Website] Move camel-karaf and camel-spring-boot content into "components" component?

Let’s try again… What I’m proposing here does not move any sources to different repos or change how e.g. the spring-boot tables of components etc are generated. I think it’s completely appropriate for the code generation etc for camel-spring-boot and camel-karat to be in separate repositories,

Re: [Website] Move camel-karaf and camel-spring-boot content into "components" component?

This is another issue, but I’m thinking about it :-) David Jencks > On Oct 5, 2021, at 12:26 AM, Claus Ibsen wrote: > > Hi > > Btw on another note, then we have for camel-spring-boot and > camel-karaf a "catalog" which holds JSon files with information for > every JAR they support. > > https:

Re: [Website] Move camel-karaf and camel-spring-boot content into "components" component?

Hi Btw on another note, then we have for camel-spring-boot and camel-karaf a "catalog" which holds JSon files with information for every JAR they support. https://github.com/apache/camel-spring-boot/tree/main/catalog/camel-catalog-provider-springboot The same for karaf at https://github.com/apac

Re: [Website] Move camel-karaf and camel-spring-boot content into "components" component?

Hi David Can you explain in more detail what you mean by moving "information" to "components". If you refer to that there is a .adoc file that is generating a big table such as https://raw.githubusercontent.com/apache/camel-spring-boot/main/docs/modules/ROOT/pages/list.adoc Then that is generate

Re: [Website] Updating after a release

Thanks Gregor, it is really useful to me to know that these are actually the steps you are following, and that the branch instructions really are missing…. I’m very good at misinterpreting docs! David Jencks > On Oct 4, 2021, at 10:39 PM, Gregor Zurowski wrote: > > I just wanted to confirm th

Re: [Website] Updating after a release

I just wanted to confirm that the release guide (https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc) is not outdated and describes the steps we are following when creating new releases. The step to branch off into a new camel-MAJOR.MINOR.x branch is mis

Re: [Website] Updating after a release

1. I got the camel-quarkus build to work with these PRs: https://github.com/apache/camel/pull/6210 https://github.com/apache/camel-spring-boot/pull/376 both include changes that eventually need to go on other branches, so I don’t want to squash the commits. They also include very substantial chang

Re: [Website] Updating after a release

If you want to work on one for the website it's fine, but you'll fragment the release docs more than the current situation. Fragmentation is bad now. We should try to reduce pages and focus on content. Il lun 4 ott 2021, 22:55 Andrea Cosentino ha scritto: > The release guide there it's not outda

Re: [Website] Updating after a release

The release guide there it's not outdated. It's related only to camel camel-karaf and camel-sb. All the other subprojects have their own release guide. -1 to start from a new page. I would start from what we have, which is exactly the release steps to release plain camel. Il lun 4 ott 2021, 22:47

Re: [Website] Updating after a release

On a quick glance, that looks outdated (vintage camel 2), unaware of most sub-projects, and incomplete (e.g. creating the camel-3.12.x branch before releasing camel-3.12.0 from it). I don’t think I should try to complete and update those instructions. I think a new page on how to deal with the

Re: [Website] Updating after a release

Hi David Yes there is the release guide docs at https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/release-guide.adoc On Mon, Oct 4, 2021 at 6:46 PM David Jencks wrote: > > I believe the Antora build has not yet been updated to include the just > released camel-3.12.x

Re: [Website] camel-spring-boot docs

I went ahead and implemented the first two of these in main “latest” branches. Other than removing 324 unreferenced and inaccessible pages, I don’t see any changes (There’s one slight change to the single reference to one of the removed pages: (diff is new to old) < Also add any component start

Re: [Website] camel-spring-boot docs

I always forget that for Antora terms often have a specific meaning that isn’t that common or obvious :-) > On Oct 2, 2021, at 12:45 AM, Claus Ibsen wrote: > > On Fri, Oct 1, 2021 at 11:30 PM David Jencks wrote: >> >> I looked at camel-spring-boot a little bit and have several questions and

Re: [Website] camel-spring-boot docs

On Fri, Oct 1, 2021 at 11:30 PM David Jencks wrote: > > I looked at camel-spring-boot a little bit and have several questions and > suggestions… if there’s agreement I’ll open some issues and work on them. > > 1. The AsciiDoc pages are only included in the main component/dataformat/… > pages, an

Re: [Website] version link anomalies?

> On Sep 24, 2021, at 12:16 AM, Claus Ibsen wrote: > > On Thu, Sep 23, 2021 at 5:37 PM David Jencks > wrote: >> >> I can do that :-) but it doesn’t answer my question of what the >> camel-quarkus version refers to. Is it arbitrary? Does it refer to a >> qu

Re: [Website] version link anomalies?

On Thu, Sep 23, 2021 at 5:37 PM David Jencks wrote: > > I can do that :-) but it doesn’t answer my question of what the > camel-quarkus version refers to. Is it arbitrary? Does it refer to a quarkus > version? > Yes it refers to the quarkus version. Quarkus just recently bumped from v1 to v2.

Re: [Website] version link anomalies?

I can do that :-) but it doesn’t answer my question of what the camel-quarkus version refers to. Is it arbitrary? Does it refer to a quarkus version? If it refers to a quarkus version then I think the display version for latest ought to be something like 2.3.0 (Pre-release). In any case I susp

Re: [Website] version link anomalies?

Hi Ah camel-quarkus likely haven't updated and removed outdated releases. Its latest release is 2.2.0, which should be there instead of 2.0.0. The 2.0.0 should be removed. On Thu, Sep 23, 2021 at 4:38 AM David Jencks wrote: > > So camel-quarkus latest referring to camel components 3.11.x seems

Re: [Website] version link anomalies?

So camel-quarkus latest referring to camel components 3.11.x seems reasonable. What about camel-quarkus 2.0.0? Now I noticed some more problems…. I can’t figure out what the meaning of the camel-quarkus version is. What does the `2.0.0` in the non-latest version refer to? What about `latest`

  1   2   3   >