[jira] [Created] (CAMEL-17698) Inconsistency in naming parts of camel-google-secrets-manager
David Jencks created CAMEL-17698: Summary: Inconsistency in naming parts of camel-google-secrets-manager Key: CAMEL-17698 URL: https://issues.apache.org/jira/browse/CAMEL-17698 Project: Camel Issue Type: Bug Reporter: David Jencks There's a lot of inconsistency about whether it's google-secret-manager or google-secrets-manager. Right now this has broken the website build because the spring-boot json file is google-secrets-manager.json but the camel components adoc has :camel-spring-boot-name: google-secret-manager Before this gets released I suggest that EVERYTHING be named consistently, either singular or plural but NOT a mixture. >From e.g. ``` import com.google.cloud.secretmanager.v1.SecretManagerServiceClient; ``` it looks like google prefers a singular form, so I'd guess it would be less confusing for camel to adopt the same. I don't have a great deal of time right now but if there's agreement on what to do I can try to come up with a PR. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (CAMEL-17409) commit generated changes on all branches
[ https://issues.apache.org/jira/browse/CAMEL-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed CAMEL-17409. Resolution: Fixed All PRs applied > commit generated changes on all branches > > > Key: CAMEL-17409 > URL: https://issues.apache.org/jira/browse/CAMEL-17409 > Project: Camel > Issue Type: Improvement >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > We should commit generated changes on all branches. On everything except > main and the latest LTS release commits should be rare, so this will not > produce a big load on the CI servers. > It's probably possible to do this by just leaving out the branch in > master-push-build.yml: > ``` > on: > push: > branches: > - camel-3.7.x > ``` > but I don't understand GitHub actions well enough to be confident about this > so I've just set the branch in each branch where it's wrong. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (CAMEL-17434) Update Antora usages
[
https://issues.apache.org/jira/browse/CAMEL-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed CAMEL-17434.
Resolution: Fixed
All PRs applied
> Update Antora usages
>
>
> Key: CAMEL-17434
> URL: https://issues.apache.org/jira/browse/CAMEL-17434
> Project: Camel
> Issue Type: Task
>Reporter: David Jencks
>Assignee: David Jencks
>Priority: Major
>
> With Antora 3 we can:
> - shift from outdated /assets/images to /images
> - shift from `include::{attachmentsdir}...` to `include::attachment$...`
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (CAMEL-17433) Improve xml recognition in tooling JavadocHelper
[ https://issues.apache.org/jira/browse/CAMEL-17433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed CAMEL-17433. Resolution: Fixed All PRs applied. > Improve xml recognition in tooling JavadocHelper > > > Key: CAMEL-17433 > URL: https://issues.apache.org/jira/browse/CAMEL-17433 > Project: Camel > Issue Type: Task > Components: tooling >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > The JavadocHelper has some limitations in processing javadoc and xml: > - < and > characters are removed when not paired > - xml tags are not recognized well, e.g. < this is not a tag > is treated as > a tag and removed > - Already encoded entities are re-encoded, so > becomes > > It turns out that there are hundreds of examples of these problems in > generated code. > I'm going to fix the problems in JavadocHelper and let the regen_bot supply > the corrected generated code. > Thanks to Jeremy Ross for making me aware of this problem. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17434) Update Antora usages
David Jencks created CAMEL-17434:
Summary: Update Antora usages
Key: CAMEL-17434
URL: https://issues.apache.org/jira/browse/CAMEL-17434
Project: Camel
Issue Type: Improvement
Reporter: David Jencks
Assignee: David Jencks
With Antora 3 we can:
- shift from outdated /assets/images to /images
- shift from `include::{attachmentsdir}...` to `include::attachment$...`
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17433) Improve xml recognition in tooling JavadocHelper
[ https://issues.apache.org/jira/browse/CAMEL-17433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated CAMEL-17433: - Description: The JavadocHelper has some limitations in processing javadoc and xml: - < and > characters are removed when not paired - xml tags are not recognized well, e.g. < this is not a tag > is treated as a tag and removed - Already encoded entities are re-encoded, so > becomes > It turns out that there are hundreds of examples of these problems in generated code. I'm going to fix the problems in JavadocHelper and let the regen_bot supply the corrected generated code. Thanks to Jeremy Ross for making me aware of this problem. was: The JavadocHelper has some limitations in processing javadoc and xml: - < and > characters are removed when not paired - xml tags are not recognized well, e.g. < this is not a tag > is treated as a tag and removed - Already encoded entities are re-encoded, so > becomes > It turns out that there are hundreds of examples of these problems in generated code. I'm going to fix these problems and let the regen_bot supply the corrected generated code. Thanks to Jeremy Ross for making me aware of this problem. > Improve xml recognition in tooling JavadocHelper > > > Key: CAMEL-17433 > URL: https://issues.apache.org/jira/browse/CAMEL-17433 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > The JavadocHelper has some limitations in processing javadoc and xml: > - < and > characters are removed when not paired > - xml tags are not recognized well, e.g. < this is not a tag > is treated as > a tag and removed > - Already encoded entities are re-encoded, so > becomes > > It turns out that there are hundreds of examples of these problems in > generated code. > I'm going to fix the problems in JavadocHelper and let the regen_bot supply > the corrected generated code. > Thanks to Jeremy Ross for making me aware of this problem. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17433) Improve xml recognition in tooling JavadocHelper
David Jencks created CAMEL-17433: Summary: Improve xml recognition in tooling JavadocHelper Key: CAMEL-17433 URL: https://issues.apache.org/jira/browse/CAMEL-17433 Project: Camel Issue Type: Improvement Components: tooling Reporter: David Jencks Assignee: David Jencks The JavadocHelper has some limitations in processing javadoc and xml: - < and > characters are removed when not paired - xml tags are not recognized well, e.g. < this is not a tag > is treated as a tag and removed - Already encoded entities are re-encoded, so > becomes > It turns out that there are hundreds of examples of these problems in generated code. I'm going to fix these problems and let the regen_bot supply the corrected generated code. Thanks to Jeremy Ross for making me aware of this problem. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (CAMEL-17404) [Docs][camel-karaf]Generate components table with Antora
[ https://issues.apache.org/jira/browse/CAMEL-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed CAMEL-17404. > [Docs][camel-karaf]Generate components table with Antora > > > Key: CAMEL-17404 > URL: https://issues.apache.org/jira/browse/CAMEL-17404 > Project: Camel > Issue Type: Improvement > Components: camel-karaf >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > I propose removing the java code generating the tables on the components page > and replacing it with Antora generation. This involves: > - generating the .json files for components into the catalog src directory, > and committing them. Generation is fairly easy, but at the moment committing > is a manual process. On main, changes should end up in the auto-generated > PR, but on other branches no such mechanism is in place, resulting in at > least two branches having uncommitted changes after builds (before my > changes). > - removing the mojo to generate the table contents > - adding a little javascript to help with the table entries > - using the indexer extension to generate the tables from the .json files. > In my PRs, I've changed the tables a little bit: > - the feature name is in it's own column, named "feature" rather than being > in parentheses after the extension name (I had no idea what it meant) > - the syntax string is removed. I can't see how it can be useful in the > table, but it if is it's easy enough to add. I would expect that much more > information about the extension would be needed to use it in karaf, just like > in Spring. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17404) [Docs][camel-karaf]Generate components table with Antora
[ https://issues.apache.org/jira/browse/CAMEL-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-17404. -- Resolution: Fixed > [Docs][camel-karaf]Generate components table with Antora > > > Key: CAMEL-17404 > URL: https://issues.apache.org/jira/browse/CAMEL-17404 > Project: Camel > Issue Type: Improvement > Components: camel-karaf >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > I propose removing the java code generating the tables on the components page > and replacing it with Antora generation. This involves: > - generating the .json files for components into the catalog src directory, > and committing them. Generation is fairly easy, but at the moment committing > is a manual process. On main, changes should end up in the auto-generated > PR, but on other branches no such mechanism is in place, resulting in at > least two branches having uncommitted changes after builds (before my > changes). > - removing the mojo to generate the table contents > - adding a little javascript to help with the table entries > - using the indexer extension to generate the tables from the .json files. > In my PRs, I've changed the tables a little bit: > - the feature name is in it's own column, named "feature" rather than being > in parentheses after the extension name (I had no idea what it meant) > - the syntax string is removed. I can't see how it can be useful in the > table, but it if is it's easy enough to add. I would expect that much more > information about the extension would be needed to use it in karaf, just like > in Spring. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17404) [Docs][camel-karaf]Generate components table with Antora
[ https://issues.apache.org/jira/browse/CAMEL-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467767#comment-17467767 ] David Jencks commented on CAMEL-17404: -- All PRs merged, closing. > [Docs][camel-karaf]Generate components table with Antora > > > Key: CAMEL-17404 > URL: https://issues.apache.org/jira/browse/CAMEL-17404 > Project: Camel > Issue Type: Improvement > Components: camel-karaf >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > I propose removing the java code generating the tables on the components page > and replacing it with Antora generation. This involves: > - generating the .json files for components into the catalog src directory, > and committing them. Generation is fairly easy, but at the moment committing > is a manual process. On main, changes should end up in the auto-generated > PR, but on other branches no such mechanism is in place, resulting in at > least two branches having uncommitted changes after builds (before my > changes). > - removing the mojo to generate the table contents > - adding a little javascript to help with the table entries > - using the indexer extension to generate the tables from the .json files. > In my PRs, I've changed the tables a little bit: > - the feature name is in it's own column, named "feature" rather than being > in parentheses after the extension name (I had no idea what it meant) > - the syntax string is removed. I can't see how it can be useful in the > table, but it if is it's easy enough to add. I would expect that much more > information about the extension would be needed to use it in karaf, just like > in Spring. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17409) commit generated changes on all branches
David Jencks created CAMEL-17409: Summary: commit generated changes on all branches Key: CAMEL-17409 URL: https://issues.apache.org/jira/browse/CAMEL-17409 Project: Camel Issue Type: Improvement Reporter: David Jencks Assignee: David Jencks We should commit generated changes on all branches. On everything except main and the latest LTS release commits should be rare, so this will not produce a big load on the CI servers. It's probably possible to do this by just leaving out the branch in master-push-build.yml: ``` on: push: branches: - camel-3.7.x ``` but I don't understand GitHub actions well enough to be confident about this so I've just set the branch in each branch where it's wrong. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17404) [Docs][camel-karaf]Generate components table with Antora
[ https://issues.apache.org/jira/browse/CAMEL-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467562#comment-17467562 ] David Jencks commented on CAMEL-17404: -- https://github.com/apache/camel-website/pull/745 will generate a preview. > [Docs][camel-karaf]Generate components table with Antora > > > Key: CAMEL-17404 > URL: https://issues.apache.org/jira/browse/CAMEL-17404 > Project: Camel > Issue Type: Improvement > Components: camel-karaf >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > I propose removing the java code generating the tables on the components page > and replacing it with Antora generation. This involves: > - generating the .json files for components into the catalog src directory, > and committing them. Generation is fairly easy, but at the moment committing > is a manual process. On main, changes should end up in the auto-generated > PR, but on other branches no such mechanism is in place, resulting in at > least two branches having uncommitted changes after builds (before my > changes). > - removing the mojo to generate the table contents > - adding a little javascript to help with the table entries > - using the indexer extension to generate the tables from the .json files. > In my PRs, I've changed the tables a little bit: > - the feature name is in it's own column, named "feature" rather than being > in parentheses after the extension name (I had no idea what it meant) > - the syntax string is removed. I can't see how it can be useful in the > table, but it if is it's easy enough to add. I would expect that much more > information about the extension would be needed to use it in karaf, just like > in Spring. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17404) [Docs][camel-karaf]Generate components table with Antora
David Jencks created CAMEL-17404: Summary: [Docs][camel-karaf]Generate components table with Antora Key: CAMEL-17404 URL: https://issues.apache.org/jira/browse/CAMEL-17404 Project: Camel Issue Type: Improvement Components: camel-karaf Reporter: David Jencks Assignee: David Jencks I propose removing the java code generating the tables on the components page and replacing it with Antora generation. This involves: - generating the .json files for components into the catalog src directory, and committing them. Generation is fairly easy, but at the moment committing is a manual process. On main, changes should end up in the auto-generated PR, but on other branches no such mechanism is in place, resulting in at least two branches having uncommitted changes after builds (before my changes). - removing the mojo to generate the table contents - adding a little javascript to help with the table entries - using the indexer extension to generate the tables from the .json files. In my PRs, I've changed the tables a little bit: - the feature name is in it's own column, named "feature" rather than being in parentheses after the extension name (I had no idea what it meant) - the syntax string is removed. I can't see how it can be useful in the table, but it if is it's easy enough to add. I would expect that much more information about the extension would be needed to use it in karaf, just like in Spring. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17208) Website release process documentation correction
David Jencks created CAMEL-17208: Summary: Website release process documentation correction Key: CAMEL-17208 URL: https://issues.apache.org/jira/browse/CAMEL-17208 Project: Camel Issue Type: Bug Components: documentation Reporter: David Jencks Assignee: David Jencks The network of subproject version dependencies is more complicated than we previously accounted for in the website release docs. We've recently seen that: - camel-quarkus 2.4.x depends on camel components 3.12.x, so 3.12.x needs to remain in the docs as long as cq 2.4.x - camel-k 1.7.x depends on camel-quarkus 2.4.x, so cq 2.4.x and camel 3.12.x need to remain in the docs as long as camel-k 1.7.x I imagine there are a lot more subproject interdependencies that have not yet been discovered or even properly set up. It would be great to have - each subproject clearly document which other subprojects it depends on with the versions of these other subprojects, as I've suggested in https://github.com/apache/camel-k/issues/2759. - a centralized view of all such dependencies. However, we should at least document that these dependencies generally exist and that removing any version from the documentation needs to check that no other subprojects are referencing it. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17169) Three copies of same-named attribute in generated spring-boot.json file
[
https://issues.apache.org/jira/browse/CAMEL-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443952#comment-17443952
]
David Jencks commented on CAMEL-17169:
--
I'll update my spring boot PRs on top of your work and check the site still
builds with them...
> Three copies of same-named attribute in generated spring-boot.json file
> ---
>
> Key: CAMEL-17169
> URL: https://issues.apache.org/jira/browse/CAMEL-17169
> Project: Camel
> Issue Type: Task
> Components: camel-spring-boot-starters
>Reporter: David Jencks
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.13.0, 3.11.4
>
>
> In main branch:
> This is in generated core/camel-spring-boot/src/main/docs/spring-boot.json:
> ```
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "description": "To turn on or off information about Camel Routes via
> actuator endpoint.",
> "defaultValue": true
> },
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "description": "Whether to enable the camelroutes endpoint.",
> "sourceType":
> "org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpoint",
> "defaultValue": true
> },
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "sourceType":
> "org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpointProperties",
> "defaultValue": false
> },
> ```
> Three versions of the same property doesn't make sense.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17169) Three copies of same-named attribute in generated spring-boot.json file
[
https://issues.apache.org/jira/browse/CAMEL-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443936#comment-17443936
]
David Jencks commented on CAMEL-17169:
--
Thanks for fixing 3.11.x. Since both 3.12.x and 3.7.x are going to leave soon,
is there an actual problem in manually fixing the json files in those two
branches? That would cause a lot fewer problems in the website than trying to
remove one version of camel-spring-boot.
> Three copies of same-named attribute in generated spring-boot.json file
> ---
>
> Key: CAMEL-17169
> URL: https://issues.apache.org/jira/browse/CAMEL-17169
> Project: Camel
> Issue Type: Task
> Components: camel-spring-boot-starters
>Reporter: David Jencks
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.13.0, 3.11.4
>
>
> In main branch:
> This is in generated core/camel-spring-boot/src/main/docs/spring-boot.json:
> ```
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "description": "To turn on or off information about Camel Routes via
> actuator endpoint.",
> "defaultValue": true
> },
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "description": "Whether to enable the camelroutes endpoint.",
> "sourceType":
> "org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpoint",
> "defaultValue": true
> },
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "sourceType":
> "org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpointProperties",
> "defaultValue": false
> },
> ```
> Three versions of the same property doesn't make sense.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17169) Three copies of same-named attribute in generated spring-boot.json file
[
https://issues.apache.org/jira/browse/CAMEL-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443843#comment-17443843
]
David Jencks commented on CAMEL-17169:
--
3.12 can't be removed until after 3.13 is added, giving camel-quarkus and
possibly other projects time to adjust, see
https://github.com/apache/camel/pull/6436.
Will it cause any problems to manually fix the json files in older versions?
Valid json files are needed for page generation to work properly. Having a
generated spring-boot page in only some versions would require listing
camel-spring-boot twice in the Antora playbook, with different start_paths,
something I would really like to avoid.
The PRs listed in https://github.com/apache/camel-website/pull/669 for 3.12.x
and earlier manually fix the json files. I wouldn't expect this possibly to
cause any problems unless someone regenerates the json files, in which case
perhaps we can just fix them again.
> Three copies of same-named attribute in generated spring-boot.json file
> ---
>
> Key: CAMEL-17169
> URL: https://issues.apache.org/jira/browse/CAMEL-17169
> Project: Camel
> Issue Type: Task
> Components: camel-spring-boot-starters
>Reporter: David Jencks
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.13.0
>
>
> In main branch:
> This is in generated core/camel-spring-boot/src/main/docs/spring-boot.json:
> ```
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "description": "To turn on or off information about Camel Routes via
> actuator endpoint.",
> "defaultValue": true
> },
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "description": "Whether to enable the camelroutes endpoint.",
> "sourceType":
> "org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpoint",
> "defaultValue": true
> },
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "sourceType":
> "org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpointProperties",
> "defaultValue": false
> },
> ```
> Three versions of the same property doesn't make sense.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17169) Three copies of same-named attribute in generated spring-boot.json file
[
https://issues.apache.org/jira/browse/CAMEL-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443504#comment-17443504
]
David Jencks commented on CAMEL-17169:
--
The same problem occurs in 3.12, 3.11, and 3.7. Is it safe to apply the same
fix? Alternatively I can just edit the json file to remove duplicates: this
would only cause a problem if the json file was regenerated.
> Three copies of same-named attribute in generated spring-boot.json file
> ---
>
> Key: CAMEL-17169
> URL: https://issues.apache.org/jira/browse/CAMEL-17169
> Project: Camel
> Issue Type: Task
> Components: camel-spring-boot-starters
>Reporter: David Jencks
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.13.0
>
>
> In main branch:
> This is in generated core/camel-spring-boot/src/main/docs/spring-boot.json:
> ```
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "description": "To turn on or off information about Camel Routes via
> actuator endpoint.",
> "defaultValue": true
> },
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "description": "Whether to enable the camelroutes endpoint.",
> "sourceType":
> "org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpoint",
> "defaultValue": true
> },
> {
> "name": "management.endpoint.camelroutes.enabled",
> "type": "java.lang.Boolean",
> "sourceType":
> "org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpointProperties",
> "defaultValue": false
> },
> ```
> Three versions of the same property doesn't make sense.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17169) Three copies of same-named attribute in generated spring-boot.json file
David Jencks created CAMEL-17169:
Summary: Three copies of same-named attribute in generated
spring-boot.json file
Key: CAMEL-17169
URL: https://issues.apache.org/jira/browse/CAMEL-17169
Project: Camel
Issue Type: Bug
Components: camel-spring-boot-starters
Reporter: David Jencks
In main branch:
This is in generated core/camel-spring-boot/src/main/docs/spring-boot.json:
```
{
"name": "management.endpoint.camelroutes.enabled",
"type": "java.lang.Boolean",
"description": "To turn on or off information about Camel Routes via
actuator endpoint.",
"defaultValue": true
},
{
"name": "management.endpoint.camelroutes.enabled",
"type": "java.lang.Boolean",
"description": "Whether to enable the camelroutes endpoint.",
"sourceType":
"org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpoint",
"defaultValue": true
},
{
"name": "management.endpoint.camelroutes.enabled",
"type": "java.lang.Boolean",
"sourceType":
"org.apache.camel.spring.boot.actuate.endpoint.CamelRoutesEndpointProperties",
"defaultValue": false
},
```
Three versions of the same property doesn't make sense.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-17055) Duplication options in hazelcast
David Jencks created CAMEL-17055:
Summary: Duplication options in hazelcast
Key: CAMEL-17055
URL: https://issues.apache.org/jira/browse/CAMEL-17055
Project: Camel
Issue Type: Bug
Components: camel-spring-boot-starters
Affects Versions: 3.12.0
Reporter: David Jencks
The hazelcast spring boot autoconfigure info have two duplicate
options/properties.
In the hazelcast.json file:
```
{
"name":
"camel.component.hazelcast-topic.customizer.hazelcast-instance.enabled",
"type": "java.lang.Boolean",
"description": "Enable or disable the cache-manager customizer.",
"sourceType":
"org.apache.camel.component.hazelcast.instance.springboot.customizer.HazelcastInstanceCustomizerConfiguration",
"defaultValue": true
},
{
"name":
"camel.component.hazelcast-topic.customizer.hazelcast-instance.enabled",
"type": "java.lang.Boolean",
"description": "Enable or disable the cache-manager customizer.",
"sourceType":
"org.apache.camel.component.hazelcast.topic.springboot.customizer.HazelcastInstanceCustomizerConfiguration",
"defaultValue": true
},
{
"name":
"camel.component.hazelcast-topic.customizer.hazelcast-instance.override",
"type": "java.lang.Boolean",
"description": "Configure if the cache manager eventually set on the
component should be overridden by the customizer.",
"sourceType":
"org.apache.camel.component.hazelcast.instance.springboot.customizer.HazelcastInstanceCustomizerConfiguration",
"defaultValue": false
},
{
"name":
"camel.component.hazelcast-topic.customizer.hazelcast-instance.override",
"type": "java.lang.Boolean",
"description": "Configure if the cache manager eventually set on the
component should be overridden by the customizer.",
"sourceType":
"org.apache.camel.component.hazelcast.topic.springboot.customizer.HazelcastInstanceCustomizerConfiguration",
"defaultValue": false
},
```
(lines 755-782)
I haven't located where this is generated from.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16992) [Website] Various version related changes
[
https://issues.apache.org/jira/browse/CAMEL-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated CAMEL-16992:
-
Description:
This includes several version related changes to the website:
* Drop 3.4.x as it is EOL/unmaintained. This involves camel, spring-boot, and
camel-karat.
* Mark the 'latest' camel version as prerelease and set the display-version to
"3.12.0 (Prerelease)"
* Encourage xrefs to go to the correct version by moving the "eip-vc" attribute
to the user-manual component descriptor (the only component it should be used
from) and removing all uses of it and 'latest@component' from the components
component in the main, 3.11.x, and 3.7.x branches of camel.
After the first round of PRs for main, camel-3.11.x, camel-3.7.x, camel-2.x and
camel-website I realized there are still some problems with links to
`latest@component` from the user-manual and 2.x. We should not link to
unreleased doc versions, so these should link to (currently) 3.11.x. Now that
'latest' is marked prerelease, leaving out the version in the xref will result
in this behavior. Since this will make the eip-vc attribute just `components`
I'm going to replace uses of {eip-vc} with its value. This will affect main
user-manual and camel-2.x.
was:
This includes several version related changes to the website:
* Drop 3.4.x as it is EOL/unmaintained. This involves camel, spring-boot, and
camel-karat.
* Mark the 'latest' camel version as prerelease and set the display-version to
"3.12.0 (Prerelease)"
* Encourage xrefs to go to the correct version by moving the "eip-vc" attribute
to the user-manual component descriptor (the only component it should be used
from) and removing all uses of it and 'latest@component' from the components
component in the main, 3.11.x, and 3.7.x branches of camel.
> [Website] Various version related changes
> -
>
> Key: CAMEL-16992
> URL: https://issues.apache.org/jira/browse/CAMEL-16992
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: David Jencks
>Assignee: David Jencks
>Priority: Major
>
> This includes several version related changes to the website:
> * Drop 3.4.x as it is EOL/unmaintained. This involves camel, spring-boot,
> and camel-karat.
> * Mark the 'latest' camel version as prerelease and set the display-version
> to "3.12.0 (Prerelease)"
> * Encourage xrefs to go to the correct version by moving the "eip-vc"
> attribute to the user-manual component descriptor (the only component it
> should be used from) and removing all uses of it and 'latest@component' from
> the components component in the main, 3.11.x, and 3.7.x branches of camel.
>
> After the first round of PRs for main, camel-3.11.x, camel-3.7.x, camel-2.x
> and camel-website I realized there are still some problems with links to
> `latest@component` from the user-manual and 2.x. We should not link to
> unreleased doc versions, so these should link to (currently) 3.11.x. Now
> that 'latest' is marked prerelease, leaving out the version in the xref will
> result in this behavior. Since this will make the eip-vc attribute just
> `components` I'm going to replace uses of {eip-vc} with its value. This will
> affect main user-manual and camel-2.x.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16992) [Website] Various version related changes
David Jencks created CAMEL-16992: Summary: [Website] Various version related changes Key: CAMEL-16992 URL: https://issues.apache.org/jira/browse/CAMEL-16992 Project: Camel Issue Type: Task Components: website Reporter: David Jencks Assignee: David Jencks This includes several version related changes to the website: * Drop 3.4.x as it is EOL/unmaintained. This involves camel, spring-boot, and camel-karat. * Mark the 'latest' camel version as prerelease and set the display-version to "3.12.0 (Prerelease)" * Encourage xrefs to go to the correct version by moving the "eip-vc" attribute to the user-manual component descriptor (the only component it should be used from) and removing all uses of it and 'latest@component' from the components component in the main, 3.11.x, and 3.7.x branches of camel. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16854) Component docs -- generate tables from json during website build
[ https://issues.apache.org/jira/browse/CAMEL-16854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated CAMEL-16854: - Component/s: (was: build system) documentation > Component docs -- generate tables from json during website build > > > Key: CAMEL-16854 > URL: https://issues.apache.org/jira/browse/CAMEL-16854 > Project: Camel > Issue Type: Task > Components: documentation >Affects Versions: 3.11.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > Investigate how to generate the options tables for components from json > during the website build using an Asciidoctor extension. > Also, upgrade to Antora 3 (alpha) and use symlinks rather than copying adoc > files for components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16854) Component docs -- generate tables from json during website build
David Jencks created CAMEL-16854: Summary: Component docs -- generate tables from json during website build Key: CAMEL-16854 URL: https://issues.apache.org/jira/browse/CAMEL-16854 Project: Camel Issue Type: Task Components: build system Affects Versions: 3.11.0 Reporter: David Jencks Assignee: David Jencks Investigate how to generate the options tables for components from json during the website build using an Asciidoctor extension. Also, upgrade to Antora 3 (alpha) and use symlinks rather than copying adoc files for components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16844) component docs - Tables for component vs endpoint options should have more clear titles
[ https://issues.apache.org/jira/browse/CAMEL-16844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394261#comment-17394261 ] David Jencks commented on CAMEL-16844: -- Could you summarize the zulip thread here? I'd like to know what the issue is but I'm not enthusiastic about further expanding my list of passwords. > component docs - Tables for component vs endpoint options should have more > clear titles > --- > > Key: CAMEL-16844 > URL: https://issues.apache.org/jira/browse/CAMEL-16844 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.12.0 > > > https://camel.zulipchat.com/#narrow/stream/257302-camel-quarkus/topic/S3.20prefix.20issue.20with.20Quarkus.201.2E12.20and.20higher/near/248315786 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16499) camel-website - Add documentation how xref links works
[
https://issues.apache.org/jira/browse/CAMEL-16499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17389244#comment-17389244
]
David Jencks commented on CAMEL-16499:
--
I wrote something up on this,
[https://github.com/apache/camel-website/pull/608.] Comments?
> camel-website - Add documentation how xref links works
> --
>
> Key: CAMEL-16499
> URL: https://issues.apache.org/jira/browse/CAMEL-16499
> Project: Camel
> Issue Type: Improvement
> Components: documentation, website
>Reporter: Claus Ibsen
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.x
>
>
> We need a section on camel-website root readme page, that talks about how you
> do links between pages on the website.
> The xref: syntax is confusing and not intuitive how you link between: eips,
> components, user-manual, fag, pages between sub-projects (eg camel ->
> camel-k) and so forth.
> For example in kamelet-eip.adoc as EIP doc, I could not link with
> {code}
> == More details
> - xref:components::kamelet-component.adoc[Kamelet component]
> - xref:manual::route-tepmplate.adoc[Route Template]
> - xref:latest@camel-k:ROOT::kamelets-user.adoc[Kamelets user guide]
> We also provided a small
> https://github.com/apache/camel-examples/tree/master/examples/kamelet[Kamelet
> example].
> {code}
> I tried 10 different things for the last two bullets, and looked other xref
> links, and nothing kinda worked.
> So what you end up doing is NOT to have xref links at all.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16228) Documentation: Fix xref link in old branches
[ https://issues.apache.org/jira/browse/CAMEL-16228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286155#comment-17286155 ] David Jencks commented on CAMEL-16228: -- I would like it if I could write an Asciidoctor extension to validate xrefs according to some rules, but I don't think it will be possible for a long time, until inline nodes are recognized during parsing and before conversion, so they can be examined by a tree processor. I'll keep thinking about it however. > Documentation: Fix xref link in old branches > > > Key: CAMEL-16228 > URL: https://issues.apache.org/jira/browse/CAMEL-16228 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.x > > > Currently in the .adoc of our documentation we are using (for example) > xref:components::kafka-component.adoc[KafkaIdempotentRepository] > This is ok for master branch and latest documentation. > The problem arises when we look at older active branch, all the link to > components in 3.7.x for example are still pointi to latest. We need to change > the docs in the following way > xref:3.7.x@components::kafka-component.adoc[KafkaIdempotentRepository] > We need to do this for 3.8.x, 3.7.x and 3.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16228) Documentation: Fix xref link in old branches
[ https://issues.apache.org/jira/browse/CAMEL-16228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286123#comment-17286123 ] David Jencks commented on CAMEL-16228: -- In general a per component attribute is probably best, but the particular change you pointed to looks wrong to me. Eip is already in the components component, so I’d expect removing the component segment from the xref would be a better change. > Documentation: Fix xref link in old branches > > > Key: CAMEL-16228 > URL: https://issues.apache.org/jira/browse/CAMEL-16228 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.x > > > Currently in the .adoc of our documentation we are using (for example) > xref:components::kafka-component.adoc[KafkaIdempotentRepository] > This is ok for master branch and latest documentation. > The problem arises when we look at older active branch, all the link to > components in 3.7.x for example are still pointi to latest. We need to change > the docs in the following way > xref:3.7.x@components::kafka-component.adoc[KafkaIdempotentRepository] > We need to do this for 3.8.x, 3.7.x and 3.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16228) Documentation: Fix xref link in old branches
[ https://issues.apache.org/jira/browse/CAMEL-16228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286077#comment-17286077 ] David Jencks commented on CAMEL-16228: -- That doesn't make sense to me yet. AFAICT there's only one published version of the user manual, so there's only one possible target for each xref, and it seems quite reasonable to me that the target should be the latest version, as naturally happens when you don't specify the version. Perhaps a really specific example of one existing page with an actual link and explaining what you want the target to be would help. > Documentation: Fix xref link in old branches > > > Key: CAMEL-16228 > URL: https://issues.apache.org/jira/browse/CAMEL-16228 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.x > > > Currently in the .adoc of our documentation we are using (for example) > xref:components::kafka-component.adoc[KafkaIdempotentRepository] > This is ok for master branch and latest documentation. > The problem arises when we look at older active branch, all the link to > components in 3.7.x for example are still pointi to latest. We need to change > the docs in the following way > xref:3.7.x@components::kafka-component.adoc[KafkaIdempotentRepository] > We need to do this for 3.8.x, 3.7.x and 3.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16228) Documentation: Fix xref link in old branches
[
https://issues.apache.org/jira/browse/CAMEL-16228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286048#comment-17286048
]
David Jencks commented on CAMEL-16228:
--
I'm afraid I don't understand the problem yet. A couple of specific examples
would really help.
Meanwhile, some comments
* If Camel (core), Spring Boot and Karaf are released in lockstep, I wonder if
it would be more appropriate to have them all parts of the same distributed
component. Basically, do you want the navigation tree to change when you go
say from a camel component to the spring boot info about it? I'd think it
might possibly be nicer to have the links to spring boot and karaf pages nested
under the link to the component page in the navigation.
* If you need all the links from say camel-quarkus version X to refer to camel
components version Y you can define an attribute in the camel-quarkus version X
antora.yml:
```
asciidoctor:
attributes:
camel-components-version: Y
```
and use that in your xref:
`href:\{camel-components-version}@components:languages:foo.adoc[]`
> Documentation: Fix xref link in old branches
>
>
> Key: CAMEL-16228
> URL: https://issues.apache.org/jira/browse/CAMEL-16228
> Project: Camel
> Issue Type: Task
> Components: documentation, website
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.x
>
>
> Currently in the .adoc of our documentation we are using (for example)
> xref:components::kafka-component.adoc[KafkaIdempotentRepository]
> This is ok for master branch and latest documentation.
> The problem arises when we look at older active branch, all the link to
> components in 3.7.x for example are still pointi to latest. We need to change
> the docs in the following way
> xref:3.7.x@components::kafka-component.adoc[KafkaIdempotentRepository]
> We need to do this for 3.8.x, 3.7.x and 3.4.x
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-15773) (website) Workaround xref-validator bogus errors
[ https://issues.apache.org/jira/browse/CAMEL-15773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-15773. -- Resolution: Fixed > (website) Workaround xref-validator bogus errors > > > Key: CAMEL-15773 > URL: https://issues.apache.org/jira/browse/CAMEL-15773 > Project: Camel > Issue Type: Task > Components: came-core >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > The recent change to the Antora xref-validator to validate nav files is > useful but bogus as it reclassifies nav files as pages, breaking the index > extension used to generate tables. > We can work around this by explicitly excluding nav files from the indexTable > macro. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15774) [Website] suppress warnings for unimplemented camel-quarkus components; upgrade to Antora 3.0.0-alpha.1
David Jencks created CAMEL-15774: Summary: [Website] suppress warnings for unimplemented camel-quarkus components; upgrade to Antora 3.0.0-alpha.1 Key: CAMEL-15774 URL: https://issues.apache.org/jira/browse/CAMEL-15774 Project: Camel Issue Type: Bug Reporter: David Jencks Assignee: David Jencks With Antora 3.0.0-alpha.1, include:: instructions can suppress "asciidoctor: ERROR: atlasmap-component.adoc: line 11: include target not found: ..." errors by including [opts=optional]. This modifies tooling to include this in the generated includes for cq bits, updates the generated files correspondingly, and upgrades the Antora version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15773) (website) Workaround xref-validator bogus errors
David Jencks created CAMEL-15773: Summary: (website) Workaround xref-validator bogus errors Key: CAMEL-15773 URL: https://issues.apache.org/jira/browse/CAMEL-15773 Project: Camel Issue Type: Task Components: came-core Reporter: David Jencks Assignee: David Jencks The recent change to the Antora xref-validator to validate nav files is useful but bogus as it reclassifies nav files as pages, breaking the index extension used to generate tables. We can work around this by explicitly excluding nav files from the indexTable macro. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15249) Utilize yarn workspaces
[
https://issues.apache.org/jira/browse/CAMEL-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147113#comment-17147113
]
David Jencks commented on CAMEL-15249:
--
I wasn't intending to suggest that we use npm, just that I could get this
working with npm and not with yarn. I assume someone more familiar with yarn
could get it working with yarn.
However, I'm coming to the conclusion that perhaps a yarn workspace is a good
idea, since it's possible to depend on a UI bundle and access it through
require. This would make the antora build explicitly depend on the UI bundle
in package.json.
> Utilize yarn workspaces
> ---
>
> Key: CAMEL-15249
> URL: https://issues.apache.org/jira/browse/CAMEL-15249
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
>
> To make the build simpler, i.e. that we just need to run {{yarn}} followed by
> {{yarn build}} we can utilize [Yarn
> workspaces|https://classic.yarnpkg.com/en/docs/workspaces/]. By using
> workspaces we would not need to change into {{antora-ui-camel}} and build
> there, but the Antora UI would be built as a dependency/module of the
> workspace.
> Perhaps we can even make it so that we only need to run {{yarn}} (not so sure
> this is a good idea) or we only need to run {{yarn build}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15249) Utilize yarn workspaces
[
https://issues.apache.org/jira/browse/CAMEL-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147107#comment-17147107
]
David Jencks commented on CAMEL-15249:
--
yarn workspaces seem like using a bulldozer where a teaspoon would do.
I suggest adding some more scripts to package.json. I can't get this to work
with yarn, but with npm the following works:
-- add the gulp dependencies from antora-ui-camel/package.json to package.json
-- add these scripts to package.json:
```
"build:install": "npm i --cache=.cache/npm",
"build:antora-ui": "gulp --cwd antora-ui-camel",
```
npm run build:install and npm run build:antora-ui both do what one expects.
> Utilize yarn workspaces
> ---
>
> Key: CAMEL-15249
> URL: https://issues.apache.org/jira/browse/CAMEL-15249
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
>
> To make the build simpler, i.e. that we just need to run {{yarn}} followed by
> {{yarn build}} we can utilize [Yarn
> workspaces|https://classic.yarnpkg.com/en/docs/workspaces/]. By using
> workspaces we would not need to change into {{antora-ui-camel}} and build
> there, but the Antora UI would be built as a dependency/module of the
> workspace.
> Perhaps we can even make it so that we only need to run {{yarn}} (not so sure
> this is a good idea) or we only need to run {{yarn build}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-15182) [Website] generate component summary index lists
[ https://issues.apache.org/jira/browse/CAMEL-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-15182. -- Fix Version/s: 3.4.0 Resolution: Fixed PRs applied > [Website] generate component summary index lists > > > Key: CAMEL-15182 > URL: https://issues.apache.org/jira/browse/CAMEL-15182 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.3.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.4.0 > > > We can generate the lists of components on component summary pages and > standardize the layout a bit. > > e.g aws-summary. > > This needs some .adoc updates and a version bump in the website package.json. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15182) [Website] generate component summary index lists
[ https://issues.apache.org/jira/browse/CAMEL-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134501#comment-17134501 ] David Jencks commented on CAMEL-15182: -- camel-website pr: [https://github.com/apache/camel-website/pull/395 (apply first!)|https://github.com/apache/camel-website/pull/395] camel master pr: https://github.com/apache/camel/pull/3910 > [Website] generate component summary index lists > > > Key: CAMEL-15182 > URL: https://issues.apache.org/jira/browse/CAMEL-15182 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.3.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > We can generate the lists of components on component summary pages and > standardize the layout a bit. > > e.g aws-summary. > > This needs some .adoc updates and a version bump in the website package.json. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15182) [Website] generate component summary index lists
David Jencks created CAMEL-15182: Summary: [Website] generate component summary index lists Key: CAMEL-15182 URL: https://issues.apache.org/jira/browse/CAMEL-15182 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.3.0 Reporter: David Jencks Assignee: David Jencks We can generate the lists of components on component summary pages and standardize the layout a bit. e.g aws-summary. This needs some .adoc updates and a version bump in the website package.json. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14910) Decide if component summary pages are a good idea
[ https://issues.apache.org/jira/browse/CAMEL-14910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116913#comment-17116913 ] David Jencks commented on CAMEL-14910: -- This issue is closed, lets discuss on the PR. > Decide if component summary pages are a good idea > - > > Key: CAMEL-14910 > URL: https://issues.apache.org/jira/browse/CAMEL-14910 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Priority: Major > Attachments: aws2.png, getting-started.png > > > I discovered some component summary pages while working on CAMEL-14874 > and included them in the nav pane and index table. Claus suggested that the > Spring one was useful and the others should be dropped. The Kubernetes > summary page is heavily linked back and forth to the individual Kubernetes > components. > > In general, due to the extremely long components list, I'm inclined to think > that any possible kind of grouping is a good idea. If there are going to be > summary pages, then they should all be similar in some way. > * Should there be summary pages for groups of related components? > * What should their structure and appearance be? > * Should the nav pane indent the components in a group? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14904) Nav pane does not show current page
[ https://issues.apache.org/jira/browse/CAMEL-14904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116853#comment-17116853 ] David Jencks commented on CAMEL-14904: -- In general the Camel UI bundle is much worse in many respects than the current Antora default UI, this is only one of the most blatant. I think it would be a fairly large but worthwhile project to "rebase" the camel UI on the current Antora default. I've found this "rebasing" to be far more difficult than I'd like and I have some experiments to make it easier: separating out the UI builder code to a separate reusable project, and making this builder able to assemble a UI from several UI projects, "additively". Normally you start with the default UI and change things in one or more "downstream" projects. I'm not sure if this would be appropriate for camel at this point. https://gitlab.com/djencks/antora-ui-builder, with a bunch of examples used in https://gitlab.com/djencks/antora-extension-examples. > Nav pane does not show current page > --- > > Key: CAMEL-14904 > URL: https://issues.apache.org/jira/browse/CAMEL-14904 > Project: Camel > Issue Type: Task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Priority: Major > > The Antora default UI highlights and makes sure the nav list item for the > current page remains visible. The Camel components list does not do this, > always scrolling to the top when you click on an item. This makes it very > hard to use. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14910) Decide if component summary pages are a good idea
[ https://issues.apache.org/jira/browse/CAMEL-14910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116846#comment-17116846 ] David Jencks commented on CAMEL-14910: -- This nav list is generated. I was hoping to generate it in Antora with the index extension that generates the summary tables, but the needed change didn't get into Antora 2.3.1. One way to provide the information necessary to generate the nested list would be to put the nesting depth in the page as an attribute: normally depth 1 but for the pages in a summary depth 2. It would be best if this could be calculated as the attributes are being inserted, but I haven't thought of a way to do that. Does anyone else have an idea how to provide the information needed to calculate the nesting? > Decide if component summary pages are a good idea > - > > Key: CAMEL-14910 > URL: https://issues.apache.org/jira/browse/CAMEL-14910 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Priority: Major > Attachments: aws2.png, getting-started.png > > > I discovered some component summary pages while working on CAMEL-14874 > and included them in the nav pane and index table. Claus suggested that the > Spring one was useful and the others should be dropped. The Kubernetes > summary page is heavily linked back and forth to the individual Kubernetes > components. > > In general, due to the extremely long components list, I'm inclined to think > that any possible kind of grouping is a good idea. If there are going to be > summary pages, then they should all be similar in some way. > * Should there be summary pages for groups of related components? > * What should their structure and appearance be? > * Should the nav pane indent the components in a group? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15033) Create index.adoc tables using indexer in 2.x branch
[ https://issues.apache.org/jira/browse/CAMEL-15033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-15033. -- Resolution: Fixed xrefs fixed with 2nd PR > Create index.adoc tables using indexer in 2.x branch > > > Key: CAMEL-15033 > URL: https://issues.apache.org/jira/browse/CAMEL-15033 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > Use antora indexer extension to generate the index tables in the 2.x branch, > similar to the latest and 3.2.x branches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15033) Create index.adoc tables using indexer in 2.x branch
[ https://issues.apache.org/jira/browse/CAMEL-15033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-15033. -- Fix Version/s: 3.3.0 Resolution: Fixed PR applied. > Create index.adoc tables using indexer in 2.x branch > > > Key: CAMEL-15033 > URL: https://issues.apache.org/jira/browse/CAMEL-15033 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > Use antora indexer extension to generate the index tables in the 2.x branch, > similar to the latest and 3.2.x branches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15033) Create index.adoc tables using indexer in 2.x branch
David Jencks created CAMEL-15033: Summary: Create index.adoc tables using indexer in 2.x branch Key: CAMEL-15033 URL: https://issues.apache.org/jira/browse/CAMEL-15033 Project: Camel Issue Type: Improvement Components: website Reporter: David Jencks Assignee: David Jencks Use antora indexer extension to generate the index tables in the 2.x branch, similar to the latest and 3.2.x branches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-14771) Consider using the master branch tooling for 2.x and 3.0.x catalog construction
[ https://issues.apache.org/jira/browse/CAMEL-14771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed CAMEL-14771. Assignee: David Jencks Resolution: Won't Fix I'm taking a different approach to generating tables in 2.x > Consider using the master branch tooling for 2.x and 3.0.x catalog > construction > --- > > Key: CAMEL-14771 > URL: https://issues.apache.org/jira/browse/CAMEL-14771 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.x > > Time Spent: 10m > Remaining Estimate: 0h > > The 3.0.x branch includes the tooling needed to construct the components > component index pages, but the 2.x branch does not. Some slight modification > and configuration of the master branch tooling allow it to be used for the > 2.x index pages. The modifications are roughly: > * excluding some json files that are not intended for the catalog > * changing some parameter names that are shared across mojos but have > different meanings, so that they may be configured. > I don't know if this is a good idea or not. I only changed the one name that > conflicts, but if we decide to do this changing some more would be a good > idea. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14995) [CAMEL-K] Not all traits pages are being generated
[ https://issues.apache.org/jira/browse/CAMEL-14995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14995. -- Fix Version/s: 3.3.0 Resolution: Fixed I found how to generate the 2 missing pages that still exist, https://github.com/apache/camel-k/pull/1441. I will leave fixing the build so this is less likely to occur again to others. > [CAMEL-K] Not all traits pages are being generated > -- > > Key: CAMEL-14995 > URL: https://issues.apache.org/jira/browse/CAMEL-14995 > Project: Camel > Issue Type: Task > Components: camel-k, website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > While working on https://issues.apache.org/jira/browse/CAMEL-14993 I noticed > that these pages are not actually generated: > delete mode 100755 docs/modules/ROOT/pages/traits/3scale.adoc > delete mode 100755 docs/modules/ROOT/pages/traits/debug.adoc > delete mode 100755 docs/modules/ROOT/pages/traits/master.adoc > I also see: > MacBook-Pro-2:camel-k david$ ./script/gen_doc.sh > Generating traits documentation... > W0430 09:59:35.227985 60469 parse.go:246] Ignoring child directory > addons/master: unable to import "addons/master": package addons/master is not > in GOROOT (/usr/local/Cellar/go/1.14.2_1/libexec/src/addons/master) > W0430 09:59:35.329228 60469 parse.go:246] Ignoring child directory > addons/threescale: unable to import "addons/threescale": package > addons/threescale is not in GOROOT > (/usr/local/Cellar/go/1.14.2_1/libexec/src/addons/threescale) > I didn't see any instructions on how to generate the documentation, so I > tried things until something happened. > I think there are two problems: > - some pages aren't getting generated > - this isn't blindingly obvious. > I suggest that to partly fix the second problem, the go doc generation for > traits start by removing all the traits pages except the index page, > traits.adoc. At least git status will then indicate a change. I don't know > how to do this in go. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14995) [CAMEL-K] Not all traits pages are being generated
[ https://issues.apache.org/jira/browse/CAMEL-14995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned CAMEL-14995: Assignee: David Jencks > [CAMEL-K] Not all traits pages are being generated > -- > > Key: CAMEL-14995 > URL: https://issues.apache.org/jira/browse/CAMEL-14995 > Project: Camel > Issue Type: Task > Components: camel-k, website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > While working on https://issues.apache.org/jira/browse/CAMEL-14993 I noticed > that these pages are not actually generated: > delete mode 100755 docs/modules/ROOT/pages/traits/3scale.adoc > delete mode 100755 docs/modules/ROOT/pages/traits/debug.adoc > delete mode 100755 docs/modules/ROOT/pages/traits/master.adoc > I also see: > MacBook-Pro-2:camel-k david$ ./script/gen_doc.sh > Generating traits documentation... > W0430 09:59:35.227985 60469 parse.go:246] Ignoring child directory > addons/master: unable to import "addons/master": package addons/master is not > in GOROOT (/usr/local/Cellar/go/1.14.2_1/libexec/src/addons/master) > W0430 09:59:35.329228 60469 parse.go:246] Ignoring child directory > addons/threescale: unable to import "addons/threescale": package > addons/threescale is not in GOROOT > (/usr/local/Cellar/go/1.14.2_1/libexec/src/addons/threescale) > I didn't see any instructions on how to generate the documentation, so I > tried things until something happened. > I think there are two problems: > - some pages aren't getting generated > - this isn't blindingly obvious. > I suggest that to partly fix the second problem, the go doc generation for > traits start by removing all the traits pages except the index page, > traits.adoc. At least git status will then indicate a change. I don't know > how to do this in go. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14993) [CAMEL-K] generate traits table using Antora
[ https://issues.apache.org/jira/browse/CAMEL-14993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17096786#comment-17096786 ] David Jencks commented on CAMEL-14993: -- As a follow up, are there any attributes of the traits that would be useful displayed in an index table? Perhaps planning for the future, "since". > [CAMEL-K] generate traits table using Antora > > > Key: CAMEL-14993 > URL: https://issues.apache.org/jira/browse/CAMEL-14993 > Project: Camel > Issue Type: Improvement > Components: camel-k, website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > I propose moving traits to a 'traits' module and generating the list of > traits on 'traits.adoc' using antora rather than go. > I believe there is a problem with traits doc generation; the pages for > threescale and main are not generated locally. I'll open a separate issue to > discuss this -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14995) [CAMEL-K] Not all traits pages are being generated
David Jencks created CAMEL-14995: Summary: [CAMEL-K] Not all traits pages are being generated Key: CAMEL-14995 URL: https://issues.apache.org/jira/browse/CAMEL-14995 Project: Camel Issue Type: Bug Components: camel-k, website Affects Versions: 3.2.0 Reporter: David Jencks While working on https://issues.apache.org/jira/browse/CAMEL-14993 I noticed that these pages are not actually generated: delete mode 100755 docs/modules/ROOT/pages/traits/3scale.adoc delete mode 100755 docs/modules/ROOT/pages/traits/debug.adoc delete mode 100755 docs/modules/ROOT/pages/traits/master.adoc I also see: MacBook-Pro-2:camel-k david$ ./script/gen_doc.sh Generating traits documentation... W0430 09:59:35.227985 60469 parse.go:246] Ignoring child directory addons/master: unable to import "addons/master": package addons/master is not in GOROOT (/usr/local/Cellar/go/1.14.2_1/libexec/src/addons/master) W0430 09:59:35.329228 60469 parse.go:246] Ignoring child directory addons/threescale: unable to import "addons/threescale": package addons/threescale is not in GOROOT (/usr/local/Cellar/go/1.14.2_1/libexec/src/addons/threescale) I didn't see any instructions on how to generate the documentation, so I tried things until something happened. I think there are two problems: - some pages aren't getting generated - this isn't blindingly obvious. I suggest that to partly fix the second problem, the go doc generation for traits start by removing all the traits pages except the index page, traits.adoc. At least git status will then indicate a change. I don't know how to do this in go. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14993) [CAMEL-K] generate traits table using Antora
David Jencks created CAMEL-14993: Summary: [CAMEL-K] generate traits table using Antora Key: CAMEL-14993 URL: https://issues.apache.org/jira/browse/CAMEL-14993 Project: Camel Issue Type: Improvement Components: camel-k, website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks I propose moving traits to a 'traits' module and generating the list of traits on 'traits.adoc' using antora rather than go. I believe there is a problem with traits doc generation; the pages for threescale and main are not generated locally. I'll open a separate issue to discuss this -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14975) Move camel-k languages documentation to camel-k-runtime repository
[ https://issues.apache.org/jira/browse/CAMEL-14975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14975. -- Fix Version/s: 3.3.0 Resolution: Fixed PRs applied Fix version is for website. > Move camel-k languages documentation to camel-k-runtime repository > -- > > Key: CAMEL-14975 > URL: https://issues.apache.org/jira/browse/CAMEL-14975 > Project: Camel > Issue Type: Improvement > Components: camel-k >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > Luca suggested it would make sense to move the camel-k languages > documentation, currently here: > [https://github.com/apache/camel-k/tree/master/docs/modules/ROOT/pages/languages] > to the camel-k-runtime repo where these are implemented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14975) Move camel-k languages documentation to camel-k-runtime repository
[ https://issues.apache.org/jira/browse/CAMEL-14975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094146#comment-17094146 ] David Jencks edited comment on CAMEL-14975 at 4/28/20, 4:41 AM: I suggest also modifying camel-k to match what I did in camel-k-runtime: * removing the antora-playbook-dev.yml and using HEAD as the branch in antora-playbook.yml. There's no good reason to build a tiny part of the site using the local copy of the git repo rather than the worktree. * Removing the "dev" script and have the "preview" script build and run the server. * Document the "checks" script together with its limitations. - Use the standard Antora layout of building the site into "build/site". was (Author: djencks): I suggest also modifying camel-k to match what I did in camel-k-runtime: * removing the antora-playbook-dev.yml and using HEAD as the branch in antora-playbook.yml. There's no good reason to build a tiny part of the site using the local copy of the git repo rather than the worktree. * Removing the "dev" script and have the "preview" script build and run the server. * Document the "checks" script together with its limitations. > Move camel-k languages documentation to camel-k-runtime repository > -- > > Key: CAMEL-14975 > URL: https://issues.apache.org/jira/browse/CAMEL-14975 > Project: Camel > Issue Type: Improvement > Components: camel-k >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > Luca suggested it would make sense to move the camel-k languages > documentation, currently here: > [https://github.com/apache/camel-k/tree/master/docs/modules/ROOT/pages/languages] > to the camel-k-runtime repo where these are implemented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14975) Move camel-k languages documentation to camel-k-runtime repository
[ https://issues.apache.org/jira/browse/CAMEL-14975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094146#comment-17094146 ] David Jencks commented on CAMEL-14975: -- I suggest also modifying camel-k to match what I did in camel-k-runtime: * removing the antora-playbook-dev.yml and using HEAD as the branch in antora-playbook.yml. There's no good reason to build a tiny part of the site using the local copy of the git repo rather than the worktree. * Removing the "dev" script and have the "preview" script build and run the server. * Document the "checks" script together with its limitations. > Move camel-k languages documentation to camel-k-runtime repository > -- > > Key: CAMEL-14975 > URL: https://issues.apache.org/jira/browse/CAMEL-14975 > Project: Camel > Issue Type: Improvement > Components: camel-k >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > Luca suggested it would make sense to move the camel-k languages > documentation, currently here: > [https://github.com/apache/camel-k/tree/master/docs/modules/ROOT/pages/languages] > to the camel-k-runtime repo where these are implemented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14975) Move camel-k languages documentation to camel-k-runtime repository
David Jencks created CAMEL-14975: Summary: Move camel-k languages documentation to camel-k-runtime repository Key: CAMEL-14975 URL: https://issues.apache.org/jira/browse/CAMEL-14975 Project: Camel Issue Type: Improvement Components: camel-k Reporter: David Jencks Assignee: David Jencks Luca suggested it would make sense to move the camel-k languages documentation, currently here: [https://github.com/apache/camel-k/tree/master/docs/modules/ROOT/pages/languages] to the camel-k-runtime repo where these are implemented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14967) Update webstie build to antora 2.3.0; camel-quarks version not needed
[ https://issues.apache.org/jira/browse/CAMEL-14967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14967. -- Resolution: Fixed PR merged > Update webstie build to antora 2.3.0; camel-quarks version not needed > - > > Key: CAMEL-14967 > URL: https://issues.apache.org/jira/browse/CAMEL-14967 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > Antora 2.3.0 released, simpler xref-check dependencies possible, don't need > camel-quarks version in playbook any more. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14967) Update webstie build to antora 2.3.0; camel-quarks version not needed
David Jencks created CAMEL-14967: Summary: Update webstie build to antora 2.3.0; camel-quarks version not needed Key: CAMEL-14967 URL: https://issues.apache.org/jira/browse/CAMEL-14967 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 Antora 2.3.0 released, simpler xref-check dependencies possible, don't need camel-quarks version in playbook any more. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14945) [Camel-quarkus, website] Move camel-quarkus-last-release attribute to component descriptor
[ https://issues.apache.org/jira/browse/CAMEL-14945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14945. -- Fix Version/s: 3.3.0 Resolution: Fixed PR applied. Will remove from camel-website playbook soon in a separate PR with an upgrade to Antora 2.3.0 > [Camel-quarkus, website] Move camel-quarkus-last-release attribute to > component descriptor > -- > > Key: CAMEL-14945 > URL: https://issues.apache.org/jira/browse/CAMEL-14945 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > Recent versions of Antora allow you to specify asciidoc attributes in the > component descriptor, not just the playbook. Since > 'camel-quarkus-last-release' is only used in camel-quarks, it can be defined > in the c-q antora.yml component descriptor, avoiding duplication and the need > to update the main playbook on every release. > I'll submit a PR in a day or two when Antora 2.3.0 is released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14945) [Camel-quarkus, website] Move camel-quarkus-last-release attribute to component descriptor
David Jencks created CAMEL-14945: Summary: [Camel-quarkus, website] Move camel-quarkus-last-release attribute to component descriptor Key: CAMEL-14945 URL: https://issues.apache.org/jira/browse/CAMEL-14945 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Recent versions of Antora allow you to specify asciidoc attributes in the component descriptor, not just the playbook. Since 'camel-quarkus-last-release' is only used in camel-quarks, it can be defined in the c-q antora.yml component descriptor, avoiding duplication and the need to update the main playbook on every release. I'll submit a PR in a day or two when Antora 2.3.0 is released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14942) Add EIP to playbook for 3.2.x branch
[ https://issues.apache.org/jira/browse/CAMEL-14942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14942. -- Resolution: Fixed See https://github.com/apache/camel-website/pull/350 > Add EIP to playbook for 3.2.x branch > > > Key: CAMEL-14942 > URL: https://issues.apache.org/jira/browse/CAMEL-14942 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > The playbook also needs to mention the eip part of the components component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14940) Backport 'latest' component table generation to 3.2.x branch
[ https://issues.apache.org/jira/browse/CAMEL-14940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14940. -- Resolution: Fixed > Backport 'latest' component table generation to 3.2.x branch > > > Key: CAMEL-14940 > URL: https://issues.apache.org/jira/browse/CAMEL-14940 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > * Backport generation of index tables for component modules index pages from > 'latest' > * Since supportLevel is not available, have a 'deprecated' column instead. > * Add the EIPs to components and nav as they are now versioned along with > components. > * Fix the broken user manual faq xrefs so the maven build can succeed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14941) back port index table fixes to 3.2.x branch (source fixes)
[ https://issues.apache.org/jira/browse/CAMEL-14941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14941. -- Resolution: Fixed https://github.com/apache/camel/pull/3764 > back port index table fixes to 3.2.x branch (source fixes) > -- > > Key: CAMEL-14941 > URL: https://issues.apache.org/jira/browse/CAMEL-14941 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > This is the camel-3.2.x @camel docs fixes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14940) Backport 'latest' component table generation to 3.2.x branch
[ https://issues.apache.org/jira/browse/CAMEL-14940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088843#comment-17088843 ] David Jencks commented on CAMEL-14940: -- It might not be critical, but I think it's a bit nice to have until the LTS release, and I already made the PRs. > Backport 'latest' component table generation to 3.2.x branch > > > Key: CAMEL-14940 > URL: https://issues.apache.org/jira/browse/CAMEL-14940 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > * Backport generation of index tables for component modules index pages from > 'latest' > * Since supportLevel is not available, have a 'deprecated' column instead. > * Add the EIPs to components and nav as they are now versioned along with > components. > * Fix the broken user manual faq xrefs so the maven build can succeed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14942) Add EIP to playbook for 3.2.x branch
David Jencks created CAMEL-14942: Summary: Add EIP to playbook for 3.2.x branch Key: CAMEL-14942 URL: https://issues.apache.org/jira/browse/CAMEL-14942 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 The playbook also needs to mention the eip part of the components component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14941) back port index table fixes to 3.2.x branch (source fixes)
David Jencks created CAMEL-14941: Summary: back port index table fixes to 3.2.x branch (source fixes) Key: CAMEL-14941 URL: https://issues.apache.org/jira/browse/CAMEL-14941 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 This is the camel-3.2.x @camel docs fixes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14940) Backport 'latest' component table generation to 3.2.x branch
David Jencks created CAMEL-14940: Summary: Backport 'latest' component table generation to 3.2.x branch Key: CAMEL-14940 URL: https://issues.apache.org/jira/browse/CAMEL-14940 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 * Backport generation of index tables for component modules index pages from 'latest' * Since supportLevel is not available, have a 'deprecated' column instead. * Add the EIPs to components and nav as they are now versioned along with components. * Fix the broken user manual faq xrefs so the maven build can succeed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14907) Consider separating core and non-core components in the components index page
[ https://issues.apache.org/jira/browse/CAMEL-14907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14907. -- Resolution: Fixed PR merged > Consider separating core and non-core components in the components index page > - > > Key: CAMEL-14907 > URL: https://issues.apache.org/jira/browse/CAMEL-14907 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The user manual index page list of components (which should not be there, see > https://issues.apache.org/jira/browse/CAMEL-14906) separates core and > non-core components. Should the components index page and/or the components > nav pane also separate them in this way? The index page would be easy to do, > I'd rather wait on the nav pane until the nav list can be generated in the > same way as the table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14906) user manual index page should not list entire contents of another component.
[ https://issues.apache.org/jira/browse/CAMEL-14906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14906. -- Assignee: David Jencks Resolution: Fixed PR merged > user manual index page should not list entire contents of another component. > > > Key: CAMEL-14906 > URL: https://issues.apache.org/jira/browse/CAMEL-14906 > Project: Camel > Issue Type: Bug > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The index page for the user manual is unusable and semantically wrong. It > should not list contents of another component. It might be reasonable to have > a single link to the components component, but even that seems unnecessary to > me since there are already lots of links in the nav pane and component > explorer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14866) camel website - Show on component table the supportLevel
[ https://issues.apache.org/jira/browse/CAMEL-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083785#comment-17083785 ] David Jencks commented on CAMEL-14866: -- With CAMEL-14874 the support level is shown in a column in text on the component index pages. (for master/latest, so far). It's combined with the deprecated state. If someone comes up with some icons I can do the work to use them or indicate what needs to happen. > camel website - Show on component table the supportLevel > > > Key: CAMEL-14866 > URL: https://issues.apache.org/jira/browse/CAMEL-14866 > Project: Camel > Issue Type: New Feature > Components: website >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.3.0 > > Attachments: Screenshot 2020-04-08 at 11.46.06.png > > > We now have in the camel-catalog a supportLevel that can be > - Experimental > - Preview > - Stable > We should find a way to show this in the component table. For example could > be something like they do at quarkus with a square box for Preview and > Experimental and a tool tip. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14910) Decide if component summary pages are a good idea
David Jencks created CAMEL-14910: Summary: Decide if component summary pages are a good idea Key: CAMEL-14910 URL: https://issues.apache.org/jira/browse/CAMEL-14910 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.2.0 Reporter: David Jencks I discovered some component summary pages while working on CAMEL-14874 and included them in the nav pane and index table. Claus suggested that the Spring one was useful and the others should be dropped. The Kubernetes summary page is heavily linked back and forth to the individual Kubernetes components. In general, due to the extremely long components list, I'm inclined to think that any possible kind of grouping is a good idea. If there are going to be summary pages, then they should all be similar in some way. * Should there be summary pages for groups of related components? * What should their structure and appearance be? * Should the nav pane indent the components in a group? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14909) Decide what to do with bindy component(s) doc page(s)
David Jencks created CAMEL-14909: Summary: Decide what to do with bindy component(s) doc page(s) Key: CAMEL-14909 URL: https://issues.apache.org/jira/browse/CAMEL-14909 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.2.0 Reporter: David Jencks CAMEL-14874 turned the 3 bindy links to the exact same page into only one. Here are some possible actions: * do nothing. Is the current state unclear or unuseful in any way? * Put a small TOC at the top of the bindy page pointing to the sections specific to each "component" * Create 3 actual pages using some include magic so the actual material relevant to each form of the component is featured. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14908) Consider generating component index tables with Antora in 3.2.x branch and possibly 2.x branch.
David Jencks created CAMEL-14908: Summary: Consider generating component index tables with Antora in 3.2.x branch and possibly 2.x branch. Key: CAMEL-14908 URL: https://issues.apache.org/jira/browse/CAMEL-14908 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.2.0 Reporter: David Jencks I think it might be worth replicating CAMEL-14874 in the 3.2.x branch, as it is still almost the same as master. Doing something similar in the 2.x branch is possible but would presumably be more work. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14907) Consider separating core and non-core components in the components index page
David Jencks created CAMEL-14907: Summary: Consider separating core and non-core components in the components index page Key: CAMEL-14907 URL: https://issues.apache.org/jira/browse/CAMEL-14907 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.2.0 Reporter: David Jencks The user manual index page list of components (which should not be there, see https://issues.apache.org/jira/browse/CAMEL-14906) separates core and non-core components. Should the components index page and/or the components nav pane also separate them in this way? The index page would be easy to do, I'd rather wait on the nav pane until the nav list can be generated in the same way as the table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14906) user manual index page should not list entire contents of another component.
David Jencks created CAMEL-14906: Summary: user manual index page should not list entire contents of another component. Key: CAMEL-14906 URL: https://issues.apache.org/jira/browse/CAMEL-14906 Project: Camel Issue Type: Bug Components: website Affects Versions: 3.2.0 Reporter: David Jencks The index page for the user manual is unusable and semantically wrong. It should not list contents of another component. It might be reasonable to have a single link to the components component, but even that seems unnecessary to me since there are already lots of links in the nav pane and component explorer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14905) "responsive" table settings make it impossible to set reasonable column sizes.
David Jencks created CAMEL-14905: Summary: "responsive" table settings make it impossible to set reasonable column sizes. Key: CAMEL-14905 URL: https://issues.apache.org/jira/browse/CAMEL-14905 Project: Camel Issue Type: Bug Components: website Affects Versions: 3.2.0 Reporter: David Jencks I noticed that the column sizes for the new indexer generated tables on the various components component module index pages did not respond to my specifications of column size. Disabling the first two extensions in the playbook allowed me to specify reasonable sizes. The auto generated sizes were pretty ugly, and all these tables need to have the same layout as they are all related. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14904) Nav pane does not show current page
David Jencks created CAMEL-14904: Summary: Nav pane does not show current page Key: CAMEL-14904 URL: https://issues.apache.org/jira/browse/CAMEL-14904 Project: Camel Issue Type: Bug Components: website Affects Versions: 3.2.0 Reporter: David Jencks The Antora default UI highlights and makes sure the nav list item for the current page remains visible. The Camel components list does not do this, always scrolling to the top when you click on an item. This makes it very hard to use. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14881) Add comment 'autogenerated' to the docs/components adoc files
[ https://issues.apache.org/jira/browse/CAMEL-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083739#comment-17083739 ] David Jencks commented on CAMEL-14881: -- This didn't quite fit in CAMEL-14874 but I had the changes ready so made some PRs. What do you think? Rewording would be pretty easy. > Add comment 'autogenerated' to the docs/components adoc files > -- > > Key: CAMEL-14881 > URL: https://issues.apache.org/jira/browse/CAMEL-14881 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Dmitry Volodin >Assignee: David Jencks >Priority: Minor > Labels: help-wanted > > Adding following comment on the top of the all auto-generated adoc files > inside docs/components to notate users don't edit this files > // AUTOGENERATED, PLEASE DON'T EDIT THIS FILE!!! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14903) 2.x branch
David Jencks created CAMEL-14903: Summary: 2.x branch Key: CAMEL-14903 URL: https://issues.apache.org/jira/browse/CAMEL-14903 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14902) 3.2.x branch
David Jencks created CAMEL-14902: Summary: 3.2.x branch Key: CAMEL-14902 URL: https://issues.apache.org/jira/browse/CAMEL-14902 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14901) latest/master branch
David Jencks created CAMEL-14901: Summary: latest/master branch Key: CAMEL-14901 URL: https://issues.apache.org/jira/browse/CAMEL-14901 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14881) Add comment 'autogenerated' to the docs/components adoc files
[ https://issues.apache.org/jira/browse/CAMEL-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned CAMEL-14881: Assignee: David Jencks > Add comment 'autogenerated' to the docs/components adoc files > -- > > Key: CAMEL-14881 > URL: https://issues.apache.org/jira/browse/CAMEL-14881 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Dmitry Volodin >Assignee: David Jencks >Priority: Minor > Labels: help-wanted > > Adding following comment on the top of the all auto-generated adoc files > inside docs/components to notate users don't edit this files > // AUTOGENERATED, PLEASE DON'T EDIT THIS FILE!!! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14897) CAMEL-14874 camel master
[ https://issues.apache.org/jira/browse/CAMEL-14897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14897. -- Resolution: Fixed > CAMEL-14874 camel master > > > Key: CAMEL-14897 > URL: https://issues.apache.org/jira/browse/CAMEL-14897 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > > camel master -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14874) Generate component index page tables with Antora
[ https://issues.apache.org/jira/browse/CAMEL-14874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14874. -- Resolution: Fixed > Generate component index page tables with Antora > > > Key: CAMEL-14874 > URL: https://issues.apache.org/jira/browse/CAMEL-14874 > Project: Camel > Issue Type: Task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > > The idea is to use an Antora asciidoctor extension to query the pages in the > Antora content catalog and use that to construct the tables of components, > dataformats, and languages. In order to get all the necessary information, > some attributes will need to be added to the partially generated component > .adoc pages. > In addition I'll move the miscellaneous components to their own module and > index page. > I expect to also implement CAMEL-14866. > Eventually we should be able to use a similar technique to generate the nav > file lists but this requires a change in Antora to allow asciidoctor > extensions during nav file generation, which is unlikely to be available > before Antora 3.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14896) CAMEL-14874 camel-website
[ https://issues.apache.org/jira/browse/CAMEL-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14896. -- Resolution: Fixed > CAMEL-14874 camel-website > - > > Key: CAMEL-14896 > URL: https://issues.apache.org/jira/browse/CAMEL-14896 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > > camel website PR -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14899) CAMEL-14874 camel 2.x
[ https://issues.apache.org/jira/browse/CAMEL-14899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14899. -- Resolution: Fixed > CAMEL-14874 camel 2.x > - > > Key: CAMEL-14899 > URL: https://issues.apache.org/jira/browse/CAMEL-14899 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > > came 2.x PR -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14898) CAMEL-14874 camel 3.2.x
[ https://issues.apache.org/jira/browse/CAMEL-14898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14898. -- Resolution: Fixed > CAMEL-14874 camel 3.2.x > --- > > Key: CAMEL-14898 > URL: https://issues.apache.org/jira/browse/CAMEL-14898 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > > camel 3.2.x PR -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14900) CAMEL-14874 camel-karaf
[ https://issues.apache.org/jira/browse/CAMEL-14900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14900. -- Resolution: Fixed > CAMEL-14874 camel-karaf > --- > > Key: CAMEL-14900 > URL: https://issues.apache.org/jira/browse/CAMEL-14900 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > > camel-karaf PR (I don't know if this project is actually at 3.2/3.3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14900) CAMEL-14874 camel-karaf
David Jencks created CAMEL-14900: Summary: CAMEL-14874 camel-karaf Key: CAMEL-14900 URL: https://issues.apache.org/jira/browse/CAMEL-14900 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 camel-karaf PR (I don't know if this project is actually at 3.2/3.3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14898) CAMEL-14874 camel 3.2.x
David Jencks created CAMEL-14898: Summary: CAMEL-14874 camel 3.2.x Key: CAMEL-14898 URL: https://issues.apache.org/jira/browse/CAMEL-14898 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 camel 3.2.x PR -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14899) CAMEL-14874 camel 2.x
David Jencks created CAMEL-14899: Summary: CAMEL-14874 camel 2.x Key: CAMEL-14899 URL: https://issues.apache.org/jira/browse/CAMEL-14899 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 came 2.x PR -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14897) CAMEL-14874 camel master
David Jencks created CAMEL-14897: Summary: CAMEL-14874 camel master Key: CAMEL-14897 URL: https://issues.apache.org/jira/browse/CAMEL-14897 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 camel master -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14896) CAMEL-14874 camel-website
David Jencks created CAMEL-14896: Summary: CAMEL-14874 camel-website Key: CAMEL-14896 URL: https://issues.apache.org/jira/browse/CAMEL-14896 Project: Camel Issue Type: Sub-task Components: website Affects Versions: 3.2.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.3.0 camel website PR -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14895) Camel-Website: Build is broken
[
https://issues.apache.org/jira/browse/CAMEL-14895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083556#comment-17083556
]
David Jencks commented on CAMEL-14895:
--
BTW, I get "NPE" exceptions from xref-validator unless I modify the code, I
wonder why you don't.
I had to change lines 9-11 in generate-report.js to
if (originData.editUrlPattern) {
origin = [
`worktree: ${originData.editUrlPattern.slice(7,
originData.editUrlPattern.length - 3)}`,
which is wrong but works.
> Camel-Website: Build is broken
> ---
>
> Key: CAMEL-14895
> URL: https://issues.apache.org/jira/browse/CAMEL-14895
> Project: Camel
> Issue Type: Bug
> Components: website
>Reporter: Andrea Cosentino
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.3.0
>
>
> error: antora.yml not found in [https://github.com/apache/camel.git] [ref:
> remotes/origin/master]
> [https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.website/job/master/72/console]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14895) Camel-Website: Build is broken
[ https://issues.apache.org/jira/browse/CAMEL-14895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14895. -- Resolution: Fixed > Camel-Website: Build is broken > --- > > Key: CAMEL-14895 > URL: https://issues.apache.org/jira/browse/CAMEL-14895 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Andrea Cosentino >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.3.0 > > > error: antora.yml not found in [https://github.com/apache/camel.git] [ref: > remotes/origin/master] > [https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.website/job/master/72/console] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14895) Camel-Website: Build is broken
[ https://issues.apache.org/jira/browse/CAMEL-14895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083553#comment-17083553 ] David Jencks commented on CAMEL-14895: -- Great, thanks! > Camel-Website: Build is broken > --- > > Key: CAMEL-14895 > URL: https://issues.apache.org/jira/browse/CAMEL-14895 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Andrea Cosentino >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.3.0 > > > error: antora.yml not found in [https://github.com/apache/camel.git] [ref: > remotes/origin/master] > [https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.website/job/master/72/console] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (CAMEL-14895) Camel-Website: Build is broken
[ https://issues.apache.org/jira/browse/CAMEL-14895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reopened CAMEL-14895: -- Please indicate what the change is. > Camel-Website: Build is broken > --- > > Key: CAMEL-14895 > URL: https://issues.apache.org/jira/browse/CAMEL-14895 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Andrea Cosentino >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.3.0 > > > error: antora.yml not found in [https://github.com/apache/camel.git] [ref: > remotes/origin/master] > [https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.website/job/master/72/console] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14895) Camel-Website: Build is broken
[ https://issues.apache.org/jira/browse/CAMEL-14895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083548#comment-17083548 ] David Jencks commented on CAMEL-14895: -- How? Where's the link to the change? > Camel-Website: Build is broken > --- > > Key: CAMEL-14895 > URL: https://issues.apache.org/jira/browse/CAMEL-14895 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Andrea Cosentino >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.3.0 > > > error: antora.yml not found in [https://github.com/apache/camel.git] [ref: > remotes/origin/master] > [https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.website/job/master/72/console] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14895) Camel-Website: Build is broken
[ https://issues.apache.org/jira/browse/CAMEL-14895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083376#comment-17083376 ] David Jencks commented on CAMEL-14895: -- This is caused by the xref processor not understanding recent playbook syntax. Dan did something to make the xref processor relate better to recent Antora code, but it's not working for me, or apparently, the automated build. There are other problems with the xref processor as well, hopefully I can get this straightened out quickly. > Camel-Website: Build is broken > --- > > Key: CAMEL-14895 > URL: https://issues.apache.org/jira/browse/CAMEL-14895 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Andrea Cosentino >Assignee: David Jencks >Priority: Major > Fix For: 3.3.0 > > > error: antora.yml not found in [https://github.com/apache/camel.git] [ref: > remotes/origin/master] > [https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.website/job/master/72/console] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14890) Consider changes to properties-component location or documentation location.
David Jencks created CAMEL-14890: Summary: Consider changes to properties-component location or documentation location. Key: CAMEL-14890 URL: https://issues.apache.org/jira/browse/CAMEL-14890 Project: Camel Issue Type: Bug Components: camel-properties Reporter: David Jencks The properties component is highly anomalous among camel components. - is it really only present since camel 2.3? - Does the code need to be in core or could it actually be moved into components? - The description indicates it isn't really a component. What is it? Data format? Language? Miscellaneous? Lets move the main page to the correct category and, if appropriate, add a stub page in the current location indicating it's moved. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14889) camel-elytron component needs attention
David Jencks created CAMEL-14889: Summary: camel-elytron component needs attention Key: CAMEL-14889 URL: https://issues.apache.org/jira/browse/CAMEL-14889 Project: Camel Issue Type: Bug Components: documentation Reporter: David Jencks I believe the camel-elytron component needs some attention. It appears to be actually a component, but the java source has no annotations, there is no json file describing it, and none of the .adoc file is generated. The text also appears somewhat self contradictory to me. If all is correct about the current documentation, perhaps a note should be included indicating that it does not participate in normal component documentation generation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14881) Add comment 'autogenerated' to the docs/components adoc files
[
https://issues.apache.org/jira/browse/CAMEL-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082381#comment-17082381
]
David Jencks commented on CAMEL-14881:
--
Ah, so you're proposing to do something like modifying this code in gulpfile.js?
```
function insertSourceAttribute() {
return replace(/^= .+/m, function(match) {
return `${match}\n//THIS FILE IS COPIED: EDIT THE SOURCE
FILE:\n:page-source: ${path.relative('..', this.file.path)}`;
});
}
```
I'm OK with that.
> Add comment 'autogenerated' to the docs/components adoc files
> --
>
> Key: CAMEL-14881
> URL: https://issues.apache.org/jira/browse/CAMEL-14881
> Project: Camel
> Issue Type: Improvement
> Components: documentation
>Reporter: Dmitry Volodin
>Priority: Minor
> Labels: help-wanted
>
> Adding following comment on the top of the all auto-generated adoc files
> inside docs/components to notate users don't edit this files
> // AUTOGENERATED, PLEASE DON'T EDIT THIS FILE!!!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
