[jira] [Commented] (CAMEL-14567) camel-website - Sidebar menu tidy up names
[ https://issues.apache.org/jira/browse/CAMEL-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072098#comment-17072098 ] Rimsha Chaudhry commented on CAMEL-14567: - Thankyou [~zregvart] > camel-website - Sidebar menu tidy up names > -- > > Key: CAMEL-14567 > URL: https://issues.apache.org/jira/browse/CAMEL-14567 > Project: Camel > Issue Type: Test >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted, website > Attachments: Screenshot_2020-03-23 Apache Camel user manual - Apache > Camel.png > > > Apache Camel extensions for Quarkus > Apache Camel K > Apache Camel Kafka Connector > Camel Spring Boot Starters > Component reference > User manual > Make this into > Camel Components > Camel Kafka Connectors > Camel Quarkus Extensions > Camel Spring Boot Starters > User manual -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14687) Cannot build camel behind firewall
[
https://issues.apache.org/jira/browse/CAMEL-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-14687.
-
Resolution: Fixed
> Cannot build camel behind firewall
> --
>
> Key: CAMEL-14687
> URL: https://issues.apache.org/jira/browse/CAMEL-14687
> Project: Camel
> Issue Type: Improvement
> Components: build system
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: 3.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I'm having issues building camel behind a firewall because of
> camel-javadoc-plugin. It seems to be mostly copied from
> maven-javadoc-plugin 3.1.0 or 3.1.1, which stripped out proxy_user/password
> support https://issues.apache.org/jira/browse/MJAVADOC-565 - it's an issue
> because of the , and I end up with an error when javadoc tries to
> fetch them :
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:jar (attach-javadocs) on
> project camel-util: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - Error fetching URL:
> http://download.oracle.com/javase/7/docs/api/
> [ERROR] javadoc: error - Error fetching URL:
> http://download.oracle.com/javaee/7/api/
>
> I'd like to contribute a patch to set
> ${camel.javadoc.isOffline} in the
> maven/camel-javadoc-plugin, so that camel can be built behind a firewall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14687) Cannot build camel behind firewall
[
https://issues.apache.org/jira/browse/CAMEL-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14687:
Fix Version/s: (was: 3.x)
3.2.0
> Cannot build camel behind firewall
> --
>
> Key: CAMEL-14687
> URL: https://issues.apache.org/jira/browse/CAMEL-14687
> Project: Camel
> Issue Type: Improvement
> Components: build system
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: 3.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I'm having issues building camel behind a firewall because of
> camel-javadoc-plugin. It seems to be mostly copied from
> maven-javadoc-plugin 3.1.0 or 3.1.1, which stripped out proxy_user/password
> support https://issues.apache.org/jira/browse/MJAVADOC-565 - it's an issue
> because of the , and I end up with an error when javadoc tries to
> fetch them :
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:jar (attach-javadocs) on
> project camel-util: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - Error fetching URL:
> http://download.oracle.com/javase/7/docs/api/
> [ERROR] javadoc: error - Error fetching URL:
> http://download.oracle.com/javaee/7/api/
>
> I'd like to contribute a patch to set
> ${camel.javadoc.isOffline} in the
> maven/camel-javadoc-plugin, so that camel can be built behind a firewall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (CAMEL-14687) Cannot build camel behind firewall
[
https://issues.apache.org/jira/browse/CAMEL-14687?focusedWorklogId=413464=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-413464
]
ASF GitHub Bot logged work on CAMEL-14687:
--
Author: ASF GitHub Bot
Created on: 31/Mar/20 19:05
Start Date: 31/Mar/20 19:05
Worklog Time Spent: 10m
Work Description: davsclaus commented on pull request #3700: CAMEL-14687
Add camel.javadoc.offline
URL: https://github.com/apache/camel/pull/3700
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 413464)
Time Spent: 20m (was: 10m)
> Cannot build camel behind firewall
> --
>
> Key: CAMEL-14687
> URL: https://issues.apache.org/jira/browse/CAMEL-14687
> Project: Camel
> Issue Type: Improvement
> Components: build system
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: 3.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I'm having issues building camel behind a firewall because of
> camel-javadoc-plugin. It seems to be mostly copied from
> maven-javadoc-plugin 3.1.0 or 3.1.1, which stripped out proxy_user/password
> support https://issues.apache.org/jira/browse/MJAVADOC-565 - it's an issue
> because of the , and I end up with an error when javadoc tries to
> fetch them :
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:jar (attach-javadocs) on
> project camel-util: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - Error fetching URL:
> http://download.oracle.com/javase/7/docs/api/
> [ERROR] javadoc: error - Error fetching URL:
> http://download.oracle.com/javaee/7/api/
>
> I'd like to contribute a patch to set
> ${camel.javadoc.isOffline} in the
> maven/camel-javadoc-plugin, so that camel can be built behind a firewall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14817) Revisit table alignement using deprecated attributes
[
https://issues.apache.org/jira/browse/CAMEL-14817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072029#comment-17072029
]
Shreya Agarwal commented on CAMEL-14817:
[~zregvart] can I take this issue? and according to what I understood, I need
to remove "align" Attribute from all tags, and update table alignment
using CSS property?
> Revisit table alignement using deprecated attributes
>
>
> Key: CAMEL-14817
> URL: https://issues.apache.org/jira/browse/CAMEL-14817
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
>
> With [PR #290|https://github.com/apache/camel-website/pull/290] we changed
> alignment of tables using markdown syntax which results in the use of
> deprecated attributes. The build fails with:
> {code}
> Attribute "align" is deprecated on element no-deprecated-attr
> {code}
> We need to find a better way of defining table content alignment that doesn't
> render using deprecated attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071960#comment-17071960 ] Aashna Jena edited comment on CAMEL-13780 at 3/31/20, 5:38 PM: --- Pull request is [here|https://github.com/apache/camel/pull/3699]. I put this in the master branch, do I need to do the same for other branches? was (Author: aashnajena): Pull request is [here|https://github.com/apache/camel/pull/3699] > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071960#comment-17071960 ] Aashna Jena commented on CAMEL-13780: - Pull request is [here|https://github.com/apache/camel/pull/3699] > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14813) Remove CachingServiceDiscovery
[ https://issues.apache.org/jira/browse/CAMEL-14813?focusedWorklogId=413341=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-413341 ] ASF GitHub Bot logged work on CAMEL-14813: -- Author: ASF GitHub Bot Created on: 31/Mar/20 16:41 Start Date: 31/Mar/20 16:41 Worklog Time Spent: 10m Work Description: lburgazzoli commented on pull request #37: CAMEL-14813: Remove CachingServiceDiscovery (spring-boot) URL: https://github.com/apache/camel-spring-boot/pull/37 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 413341) Time Spent: 0.5h (was: 20m) > Remove CachingServiceDiscovery > -- > > Key: CAMEL-14813 > URL: https://issues.apache.org/jira/browse/CAMEL-14813 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Major > Fix For: 3.2.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The CachingServiceDiscovery does not make much sense so it need to eb removed > which also allow to remove dependency on caffeine -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14687) Cannot build camel behind firewall
[
https://issues.apache.org/jira/browse/CAMEL-14687?focusedWorklogId=413309=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-413309
]
ASF GitHub Bot logged work on CAMEL-14687:
--
Author: ASF GitHub Bot
Created on: 31/Mar/20 16:03
Start Date: 31/Mar/20 16:03
Worklog Time Spent: 10m
Work Description: cunningt commented on pull request #3700: CAMEL-14687
Add camel.javadoc.offline
URL: https://github.com/apache/camel/pull/3700
Added a camel.javadoc.offline to support building camel behind a firewall.
[x ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change
(usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue,
without pulling in other changes.
[ x] Each commit in the pull request should have a meaningful subject line
and body.
[ x] If you're unsure, you can format the pull request title like
`[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX`
with the appropriate JIRA issue.
[x ] Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
[ x] Run `mvn clean install -Psourcecheck` in your module with source check
enabled to make sure basic checks pass and there are no checkstyle violations.
A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 413309)
Remaining Estimate: 0h
Time Spent: 10m
> Cannot build camel behind firewall
> --
>
> Key: CAMEL-14687
> URL: https://issues.apache.org/jira/browse/CAMEL-14687
> Project: Camel
> Issue Type: Improvement
> Components: build system
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: 3.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I'm having issues building camel behind a firewall because of
> camel-javadoc-plugin. It seems to be mostly copied from
> maven-javadoc-plugin 3.1.0 or 3.1.1, which stripped out proxy_user/password
> support https://issues.apache.org/jira/browse/MJAVADOC-565 - it's an issue
> because of the , and I end up with an error when javadoc tries to
> fetch them :
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:jar (attach-javadocs) on
> project camel-util: MavenReportException: Error while generating Javadoc:
> [ERROR] Exit code: 1 - javadoc: error - Error fetching URL:
> http://download.oracle.com/javase/7/docs/api/
> [ERROR] javadoc: error - Error fetching URL:
> http://download.oracle.com/javaee/7/api/
>
> I'd like to contribute a patch to set
> ${camel.javadoc.isOffline} in the
> maven/camel-javadoc-plugin, so that camel can be built behind a firewall.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14626) api maven plugin - Cannot load class
[ https://issues.apache.org/jira/browse/CAMEL-14626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071863#comment-17071863 ] Kirill Yankov commented on CAMEL-14626: --- [~amfirnas22] did you already start? I have done some progress here, I can leave it for you, and maybe help, in case you have already started. > api maven plugin - Cannot load class > > > Key: CAMEL-14626 > URL: https://issues.apache.org/jira/browse/CAMEL-14626 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > > Lets improve this maven plugin to skip classes that are just type ids, eg T > etc. We can check that the length of the class must be 2+ at least > [WARNING] Ignoring type parameters for argument type, unable to load > parametric type argument T > java.lang.ClassNotFoundException: java.lang.T > at java.net.URLClassLoader.findClass (URLClassLoader.java:471) > at java.lang.ClassLoader.loadClass (ClassLoader.java:588) > at java.lang.ClassLoader.loadClass (ClassLoader.java:521) > at org.apache.camel.maven.AbstractApiMethodGeneratorMojo.getCanonicalName > (AbstractApiMethodGeneratorMojo.java:345) > at jdk.internal.reflect.GeneratedMethodAccessor226.invoke (Unknown Source) > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:566) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke > (UberspectImpl.java:556) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke > (UberspectImpl.java:539) > at org.apache.velocity.runtime.parser.node.ASTMethod.execute > (ASTMethod.java:214) > at org.apache.velocity.runtime.parser.node.ASTReference.execute > (ASTReference.java:324) > at org.apache.velocity.runtime.parser.node.ASTReference.value > (ASTReference.java:637) > at org.apache.velocity.runtime.parser.node.ASTExpression.value > (ASTExpression.java:72) > at org.apache.velocity.runtime.parser.node.ASTSetDirective.render > (ASTSetDirective.java:235) > at org.apache.velocity.runtime.parser.node.ASTBlock.render > (ASTBlock.java:144) > at org.apache.velocity.runtime.directive.Foreach.renderBlock > (Foreach.java:306) > at org.apache.velocity.runtime.directive.Foreach.render (Foreach.java:276) > at org.apache.velocity.runtime.parser.node.ASTDirective.render > (ASTDirective.java:295) > at org.apache.velocity.runtime.parser.node.SimpleNode.render > (SimpleNode.java:423) > at org.apache.velocity.Template.merge (Template.java:357) > at org.apache.velocity.Template.merge (Template.java:262) > at org.apache.camel.maven.AbstractGeneratorMojo.mergeTemplate > (AbstractGeneratorMojo.java:161) > at org.apache.camel.maven.AbstractApiMethodGeneratorMojo.executeInternal > (AbstractApiMethodGeneratorMojo.java:83) > at org.apache.camel.maven.ApiComponentGeneratorMojo.executeInternal > (ApiComponentGeneratorMojo.java:87) > at org.apache.camel.maven.AbstractGeneratorMojo.execute > (AbstractGeneratorMojo.java:103) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14626) api maven plugin - Cannot load class
[ https://issues.apache.org/jira/browse/CAMEL-14626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071862#comment-17071862 ] Kirill Yankov commented on CAMEL-14626: --- type parameter can be also encountered in a list of argTypes, for example Map, just ignoring it will make the generated code not compilable. Should we better substitute it with Object? > api maven plugin - Cannot load class > > > Key: CAMEL-14626 > URL: https://issues.apache.org/jira/browse/CAMEL-14626 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > > Lets improve this maven plugin to skip classes that are just type ids, eg T > etc. We can check that the length of the class must be 2+ at least > [WARNING] Ignoring type parameters for argument type, unable to load > parametric type argument T > java.lang.ClassNotFoundException: java.lang.T > at java.net.URLClassLoader.findClass (URLClassLoader.java:471) > at java.lang.ClassLoader.loadClass (ClassLoader.java:588) > at java.lang.ClassLoader.loadClass (ClassLoader.java:521) > at org.apache.camel.maven.AbstractApiMethodGeneratorMojo.getCanonicalName > (AbstractApiMethodGeneratorMojo.java:345) > at jdk.internal.reflect.GeneratedMethodAccessor226.invoke (Unknown Source) > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:566) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke > (UberspectImpl.java:556) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke > (UberspectImpl.java:539) > at org.apache.velocity.runtime.parser.node.ASTMethod.execute > (ASTMethod.java:214) > at org.apache.velocity.runtime.parser.node.ASTReference.execute > (ASTReference.java:324) > at org.apache.velocity.runtime.parser.node.ASTReference.value > (ASTReference.java:637) > at org.apache.velocity.runtime.parser.node.ASTExpression.value > (ASTExpression.java:72) > at org.apache.velocity.runtime.parser.node.ASTSetDirective.render > (ASTSetDirective.java:235) > at org.apache.velocity.runtime.parser.node.ASTBlock.render > (ASTBlock.java:144) > at org.apache.velocity.runtime.directive.Foreach.renderBlock > (Foreach.java:306) > at org.apache.velocity.runtime.directive.Foreach.render (Foreach.java:276) > at org.apache.velocity.runtime.parser.node.ASTDirective.render > (ASTDirective.java:295) > at org.apache.velocity.runtime.parser.node.SimpleNode.render > (SimpleNode.java:423) > at org.apache.velocity.Template.merge (Template.java:357) > at org.apache.velocity.Template.merge (Template.java:262) > at org.apache.camel.maven.AbstractGeneratorMojo.mergeTemplate > (AbstractGeneratorMojo.java:161) > at org.apache.camel.maven.AbstractApiMethodGeneratorMojo.executeInternal > (AbstractApiMethodGeneratorMojo.java:83) > at org.apache.camel.maven.ApiComponentGeneratorMojo.executeInternal > (ApiComponentGeneratorMojo.java:87) > at org.apache.camel.maven.AbstractGeneratorMojo.execute > (AbstractGeneratorMojo.java:103) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14816) Introduce supportLevel and compileTarget in the Catalog
[
https://issues.apache.org/jira/browse/CAMEL-14816?focusedWorklogId=413179=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-413179
]
ASF GitHub Bot logged work on CAMEL-14816:
--
Author: ASF GitHub Bot
Created on: 31/Mar/20 14:16
Start Date: 31/Mar/20 14:16
Worklog Time Spent: 10m
Work Description: ppalaga commented on pull request #3698: CAMEL-14816
Introduce supportLevel and compileTarget in the Catalog
URL: https://github.com/apache/camel/pull/3698
https://issues.apache.org/jira/browse/CAMEL-14816
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 413179)
Remaining Estimate: 0h
Time Spent: 10m
> Introduce supportLevel and compileTarget in the Catalog
> ---
>
> Key: CAMEL-14816
> URL: https://issues.apache.org/jira/browse/CAMEL-14816
> Project: Camel
> Issue Type: New Feature
>Reporter: Peter Palaga
>Assignee: Peter Palaga
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Both new attributes are meant for components, dataformats, etc.
> Possible values of {{supportLevel}}: {{preview}} and {{stable}} (default)
> Possible values of {{compileTarget}}: {{JVM}} (default) and {{Native}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071793#comment-17071793 ] Aashna Jena commented on CAMEL-13780: - thanks :) I will make the necessary changes in `user-manual/modules/ROOT/nav.adoc`. > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14818) Incorrect phase for camel-package-maven-plugin in upgrade guide
[ https://issues.apache.org/jira/browse/CAMEL-14818?focusedWorklogId=413152=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-413152 ] ASF GitHub Bot logged work on CAMEL-14818: -- Author: ASF GitHub Bot Created on: 31/Mar/20 13:16 Start Date: 31/Mar/20 13:16 Worklog Time Spent: 10m Work Description: jimothyGator commented on pull request #3697: [CAMEL-14818] fixes documentation for Camel Package Maven plugin URL: https://github.com/apache/camel/pull/3697 sources for type converter loaders were generated too late in the Maven build cycle. The result is that the source would be generated after the compile, test compile, and test phases, so they would not be available to unit tests. The fix is to run the maven plugin in the `pre-compile` phase rather than `process-classes`. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 413152) Remaining Estimate: 0h Time Spent: 10m > Incorrect phase for camel-package-maven-plugin in upgrade guide > --- > > Key: CAMEL-14818 > URL: https://issues.apache.org/jira/browse/CAMEL-14818 > Project: Camel > Issue Type: Bug > Components: documentation >Affects Versions: 3.1.0 >Reporter: Jim Cushing >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > [https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html] > As documented, the generated sources for type converter loaders will be > created *after* compiling. This means that the type converter loaders will > not be available to unit tests, etc. > This will go unnoticed if you (or your IDE) previously compiled the source > code, thus run the generator. But in a CI environment, the problem is > obvious, particularly if you have unit tests that use type converters. > You can also test with `rm -rf src/generated; mvn install`. > The solution is to change the phase from `process-classes` to `pre-compile`. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14818) Incorrect phase for camel-package-maven-plugin in upgrade guide
Jim Cushing created CAMEL-14818: --- Summary: Incorrect phase for camel-package-maven-plugin in upgrade guide Key: CAMEL-14818 URL: https://issues.apache.org/jira/browse/CAMEL-14818 Project: Camel Issue Type: Bug Components: documentation Affects Versions: 3.1.0 Reporter: Jim Cushing [https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html] As documented, the generated sources for type converter loaders will be created *after* compiling. This means that the type converter loaders will not be available to unit tests, etc. This will go unnoticed if you (or your IDE) previously compiled the source code, thus run the generator. But in a CI environment, the problem is obvious, particularly if you have unit tests that use type converters. You can also test with `rm -rf src/generated; mvn install`. The solution is to change the phase from `process-classes` to `pre-compile`. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14584) camel-elytron - Only use the JARs really needed
[ https://issues.apache.org/jira/browse/CAMEL-14584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14584. - Fix Version/s: (was: 3.3.0) 3.2.0 Resolution: Fixed > camel-elytron - Only use the JARs really needed > --- > > Key: CAMEL-14584 > URL: https://issues.apache.org/jira/browse/CAMEL-14584 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Its massive dependency set, and we only need a smaller set for camel-elytron > [INFO] +- org.wildfly.security:wildfly-elytron:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-asn1:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-audit:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-sasl:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-base:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-client:jar:1.11.2.Final:compile > [INFO] | | +- > org.wildfly.security:wildfly-elytron-credential-source-impl:jar:1.11.2.Final:compile > [INFO] | | \- > org.wildfly.security:wildfly-elytron-provider-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential-source-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential-store:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-basic:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-bearer:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-cert:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-form:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-spnego:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-sso:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-jacc:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-jaspi:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-json-util:jar:1.11.2.Final:compile > [INFO] | +- org.wildfly.security:wildfly-elytron-jwt:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-keystore:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-gssapi:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-oauth2:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-scram:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-password-impl:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-permission:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-realm:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-realm-jdbc:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-realm-ldap:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-realm-token:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-sasl:jar:1.11.2.Final:compile > [INFO] | +- >
[jira] [Work logged] (CAMEL-14584) camel-elytron - Only use the JARs really needed
[ https://issues.apache.org/jira/browse/CAMEL-14584?focusedWorklogId=413142=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-413142 ] ASF GitHub Bot logged work on CAMEL-14584: -- Author: ASF GitHub Bot Created on: 31/Mar/20 12:49 Start Date: 31/Mar/20 12:49 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3696: CAMEL-14584 camel-elytron - Only use the JARs really needed URL: https://github.com/apache/camel/pull/3696 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 413142) Time Spent: 20m (was: 10m) > camel-elytron - Only use the JARs really needed > --- > > Key: CAMEL-14584 > URL: https://issues.apache.org/jira/browse/CAMEL-14584 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Its massive dependency set, and we only need a smaller set for camel-elytron > [INFO] +- org.wildfly.security:wildfly-elytron:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-asn1:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-audit:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-sasl:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-base:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-client:jar:1.11.2.Final:compile > [INFO] | | +- > org.wildfly.security:wildfly-elytron-credential-source-impl:jar:1.11.2.Final:compile > [INFO] | | \- > org.wildfly.security:wildfly-elytron-provider-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential-source-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential-store:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-basic:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-bearer:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-cert:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-form:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-spnego:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-sso:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-jacc:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-jaspi:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-json-util:jar:1.11.2.Final:compile > [INFO] | +- org.wildfly.security:wildfly-elytron-jwt:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-keystore:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-gssapi:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-oauth2:jar:1.11.2.Final:compile > [INFO] | +- >
[jira] [Resolved] (CAMEL-14814) Introduce ArtifactModel as an abstraction over Component, Language, Dataformat and Other models
[ https://issues.apache.org/jira/browse/CAMEL-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-14814. -- Resolution: Fixed > Introduce ArtifactModel as an abstraction over Component, Language, > Dataformat and Other models > --- > > Key: CAMEL-14814 > URL: https://issues.apache.org/jira/browse/CAMEL-14814 > Project: Camel > Issue Type: Improvement > Components: camel-catalog >Reporter: Peter Palaga >Assignee: Peter Palaga >Priority: Major > Fix For: 3.2.0 > > > All of ComponentModel, LanguageModel, DataformatModel and OtherModel > currently have their own Maven coordinate fields groupId, artifactId and > version. This e.g. makes it hard to find all models coming from a given > artifact. Having a common parent for the four classes hosting the GAV fields > would make such a filtering much easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14817) Revisit table alignement using deprecated attributes
Zoran Regvart created CAMEL-14817:
-
Summary: Revisit table alignement using deprecated attributes
Key: CAMEL-14817
URL: https://issues.apache.org/jira/browse/CAMEL-14817
Project: Camel
Issue Type: Task
Components: website
Reporter: Zoran Regvart
With [PR #290|https://github.com/apache/camel-website/pull/290] we changed
alignment of tables using markdown syntax which results in the use of
deprecated attributes. The build fails with:
{code}
Attribute "align" is deprecated on element no-deprecated-attr
{code}
We need to find a better way of defining table content alignment that doesn't
render using deprecated attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (CAMEL-14584) camel-elytron - Only use the JARs really needed
[ https://issues.apache.org/jira/browse/CAMEL-14584?focusedWorklogId=413103=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-413103 ] ASF GitHub Bot logged work on CAMEL-14584: -- Author: ASF GitHub Bot Created on: 31/Mar/20 11:47 Start Date: 31/Mar/20 11:47 Worklog Time Spent: 10m Work Description: JiriOndrusek commented on pull request #3696: CAMEL-14584 camel-elytron - Only use the JARs really needed URL: https://github.com/apache/camel/pull/3696 Issue: https://issues.apache.org/jira/browse/CAMEL-14584 Transitive dependencies were removed from this project pom. Doc and upgrade doc is updated. [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful subject line and body. [ ] If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue. [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. [ ] Run `mvn clean install -Psourcecheck` in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically. Below are the contribution guidelines: https://github.com/apache/camel/blob/master/CONTRIBUTING.md This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 413103) Remaining Estimate: 0h Time Spent: 10m > camel-elytron - Only use the JARs really needed > --- > > Key: CAMEL-14584 > URL: https://issues.apache.org/jira/browse/CAMEL-14584 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.3.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Its massive dependency set, and we only need a smaller set for camel-elytron > [INFO] +- org.wildfly.security:wildfly-elytron:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-asn1:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-audit:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-sasl:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-base:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-client:jar:1.11.2.Final:compile > [INFO] | | +- > org.wildfly.security:wildfly-elytron-credential-source-impl:jar:1.11.2.Final:compile > [INFO] | | \- > org.wildfly.security:wildfly-elytron-provider-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential-source-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential-store:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-basic:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-bearer:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-cert:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-form:jar:1.11.2.Final:compile > [INFO] | +-
[jira] [Updated] (CAMEL-14814) Introduce ArtifactModel as an abstraction over Component, Language, Dataformat and Other models
[ https://issues.apache.org/jira/browse/CAMEL-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14814: Fix Version/s: 3.2.0 > Introduce ArtifactModel as an abstraction over Component, Language, > Dataformat and Other models > --- > > Key: CAMEL-14814 > URL: https://issues.apache.org/jira/browse/CAMEL-14814 > Project: Camel > Issue Type: Improvement >Reporter: Peter Palaga >Assignee: Peter Palaga >Priority: Major > Fix For: 3.2.0 > > > All of ComponentModel, LanguageModel, DataformatModel and OtherModel > currently have their own Maven coordinate fields groupId, artifactId and > version. This e.g. makes it hard to find all models coming from a given > artifact. Having a common parent for the four classes hosting the GAV fields > would make such a filtering much easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14815) ComponentModel.name not set by generate-endpoint-schema mojo
[ https://issues.apache.org/jira/browse/CAMEL-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14815. - Fix Version/s: 3.2.0 Resolution: Fixed > ComponentModel.name not set by generate-endpoint-schema mojo > > > Key: CAMEL-14815 > URL: https://issues.apache.org/jira/browse/CAMEL-14815 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: Peter Palaga >Assignee: Peter Palaga >Priority: Major > Fix For: 3.2.0 > > > This is related to CAMEL-14814: when iterating over a union of all > components, languages, dataformats and others in camel catalog, it is a bit > annoying that components require a special handling (getScheme() instead of > getName()) because getName() returns null for them. > The current proposal is to set the scheme value also on the name field for > components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14814) Introduce ArtifactModel as an abstraction over Component, Language, Dataformat and Other models
[ https://issues.apache.org/jira/browse/CAMEL-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14814: Component/s: camel-catalog > Introduce ArtifactModel as an abstraction over Component, Language, > Dataformat and Other models > --- > > Key: CAMEL-14814 > URL: https://issues.apache.org/jira/browse/CAMEL-14814 > Project: Camel > Issue Type: Improvement > Components: camel-catalog >Reporter: Peter Palaga >Assignee: Peter Palaga >Priority: Major > Fix For: 3.2.0 > > > All of ComponentModel, LanguageModel, DataformatModel and OtherModel > currently have their own Maven coordinate fields groupId, artifactId and > version. This e.g. makes it hard to find all models coming from a given > artifact. Having a common parent for the four classes hosting the GAV fields > would make such a filtering much easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14815) ComponentModel.name not set by generate-endpoint-schema mojo
[ https://issues.apache.org/jira/browse/CAMEL-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14815: Component/s: (was: tooling) camel-catalog > ComponentModel.name not set by generate-endpoint-schema mojo > > > Key: CAMEL-14815 > URL: https://issues.apache.org/jira/browse/CAMEL-14815 > Project: Camel > Issue Type: Improvement > Components: camel-catalog >Reporter: Peter Palaga >Assignee: Peter Palaga >Priority: Major > Fix For: 3.2.0 > > > This is related to CAMEL-14814: when iterating over a union of all > components, languages, dataformats and others in camel catalog, it is a bit > annoying that components require a special handling (getScheme() instead of > getName()) because getName() returns null for them. > The current proposal is to set the scheme value also on the name field for > components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14815) ComponentModel.name not set by generate-endpoint-schema mojo
[ https://issues.apache.org/jira/browse/CAMEL-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14815: Issue Type: Improvement (was: Bug) > ComponentModel.name not set by generate-endpoint-schema mojo > > > Key: CAMEL-14815 > URL: https://issues.apache.org/jira/browse/CAMEL-14815 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: Peter Palaga >Assignee: Peter Palaga >Priority: Major > > This is related to CAMEL-14814: when iterating over a union of all > components, languages, dataformats and others in camel catalog, it is a bit > annoying that components require a special handling (getScheme() instead of > getName()) because getName() returns null for them. > The current proposal is to set the scheme value also on the name field for > components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-13462) camel-azure - Allow a header to specify the blob name
[ https://issues.apache.org/jira/browse/CAMEL-13462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13462. - Fix Version/s: (was: 3.x) 3.2.0 Resolution: Fixed > camel-azure - Allow a header to specify the blob name > - > > Key: CAMEL-13462 > URL: https://issues.apache.org/jira/browse/CAMEL-13462 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently the blob name is hardcoded from the endpoint uri. But if you want a > bit more dynamic then you cannot do this, and would need to use toD etc. > Ah yeah using toD can help resolve this, but mind if you have many unique > file names, you end up creating many endpoints. > We should also allow to specify a header with the blob name, then we can use > the same endpoint but let the header override the blob name. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-13462) camel-azure - Allow a header to specify the blob name
[ https://issues.apache.org/jira/browse/CAMEL-13462?focusedWorklogId=413023=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-413023 ] ASF GitHub Bot logged work on CAMEL-13462: -- Author: ASF GitHub Bot Created on: 31/Mar/20 10:27 Start Date: 31/Mar/20 10:27 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3682: [CAMEL-13462] - Override blob name using header implementation. URL: https://github.com/apache/camel/pull/3682 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 413023) Time Spent: 20m (was: 10m) > camel-azure - Allow a header to specify the blob name > - > > Key: CAMEL-13462 > URL: https://issues.apache.org/jira/browse/CAMEL-13462 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > Time Spent: 20m > Remaining Estimate: 0h > > Currently the blob name is hardcoded from the endpoint uri. But if you want a > bit more dynamic then you cannot do this, and would need to use toD etc. > Ah yeah using toD can help resolve this, but mind if you have many unique > file names, you end up creating many endpoints. > We should also allow to specify a header with the blob name, then we can use > the same endpoint but let the header override the blob name. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14816) Introduce supportLevel and compileTarget in the Catalog
Peter Palaga created CAMEL-14816:
Summary: Introduce supportLevel and compileTarget in the Catalog
Key: CAMEL-14816
URL: https://issues.apache.org/jira/browse/CAMEL-14816
Project: Camel
Issue Type: New Feature
Reporter: Peter Palaga
Assignee: Peter Palaga
Both new attributes are meant for components, dataformats, etc.
Possible values of {{supportLevel}}: {{preview}} and {{stable}} (default)
Possible values of {{compileTarget}}: {{JVM}} (default) and {{Native}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (CAMEL-14813) Remove CachingServiceDiscovery
[ https://issues.apache.org/jira/browse/CAMEL-14813?focusedWorklogId=413004=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-413004 ] ASF GitHub Bot logged work on CAMEL-14813: -- Author: ASF GitHub Bot Created on: 31/Mar/20 09:59 Start Date: 31/Mar/20 09:59 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3694: CAMEL-14813: Remove CachingServiceDiscovery URL: https://github.com/apache/camel/pull/3694 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 413004) Time Spent: 20m (was: 10m) > Remove CachingServiceDiscovery > -- > > Key: CAMEL-14813 > URL: https://issues.apache.org/jira/browse/CAMEL-14813 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The CachingServiceDiscovery does not make much sense so it need to eb removed > which also allow to remove dependency on caffeine -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14813) Remove CachingServiceDiscovery
[ https://issues.apache.org/jira/browse/CAMEL-14813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14813. - Resolution: Fixed > Remove CachingServiceDiscovery > -- > > Key: CAMEL-14813 > URL: https://issues.apache.org/jira/browse/CAMEL-14813 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The CachingServiceDiscovery does not make much sense so it need to eb removed > which also allow to remove dependency on caffeine -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14815) ComponentModel.name not set by generate-endpoint-schema mojo
Peter Palaga created CAMEL-14815: Summary: ComponentModel.name not set by generate-endpoint-schema mojo Key: CAMEL-14815 URL: https://issues.apache.org/jira/browse/CAMEL-14815 Project: Camel Issue Type: Bug Components: tooling Reporter: Peter Palaga Assignee: Peter Palaga This is related to CAMEL-14814: when iterating over a union of all components, languages, dataformats and others in camel catalog, it is a bit annoying that components require a special handling (getScheme() instead of getName()) because getName() returns null for them. The current proposal is to set the scheme value also on the name field for components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14814) Introduce ArtifactModel as an abstraction over Component, Language, Dataformat and Other models
Peter Palaga created CAMEL-14814: Summary: Introduce ArtifactModel as an abstraction over Component, Language, Dataformat and Other models Key: CAMEL-14814 URL: https://issues.apache.org/jira/browse/CAMEL-14814 Project: Camel Issue Type: Improvement Reporter: Peter Palaga Assignee: Peter Palaga All of ComponentModel, LanguageModel, DataformatModel and OtherModel currently have their own Maven coordinate fields groupId, artifactId and version. This e.g. makes it hard to find all models coming from a given artifact. Having a common parent for the four classes hosting the GAV fields would make such a filtering much easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14742. - Resolution: Fixed > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14813) Remove CachingServiceDiscovery
[ https://issues.apache.org/jira/browse/CAMEL-14813?focusedWorklogId=412974=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412974 ] ASF GitHub Bot logged work on CAMEL-14813: -- Author: ASF GitHub Bot Created on: 31/Mar/20 09:26 Start Date: 31/Mar/20 09:26 Worklog Time Spent: 10m Work Description: lburgazzoli commented on pull request #3694: CAMEL-14813: Remove CachingServiceDiscovery URL: https://github.com/apache/camel/pull/3694 [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful subject line and body. [ ] If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue. [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. [ ] Run `mvn clean install -Psourcecheck` in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically. Below are the contribution guidelines: https://github.com/apache/camel/blob/master/CONTRIBUTING.md This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412974) Remaining Estimate: 0h Time Spent: 10m > Remove CachingServiceDiscovery > -- > > Key: CAMEL-14813 > URL: https://issues.apache.org/jira/browse/CAMEL-14813 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Major > Fix For: 3.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The CachingServiceDiscovery does not make much sense so it need to eb removed > which also allow to remove dependency on caffeine -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14742: Fix Version/s: (was: 2.25.1) > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071612#comment-17071612 ] Colm O hEigeartaigh commented on CAMEL-14742: - OK will do, thanks. > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.25.1, 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14813) Remove CachingServiceDiscovery
Luca Burgazzoli created CAMEL-14813: --- Summary: Remove CachingServiceDiscovery Key: CAMEL-14813 URL: https://issues.apache.org/jira/browse/CAMEL-14813 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Luca Burgazzoli Assignee: Luca Burgazzoli Fix For: 3.2.0 The CachingServiceDiscovery does not make much sense so it need to eb removed which also allow to remove dependency on caffeine -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14565) camel-spring-boot - Some auto configuration options has no descriptions
[ https://issues.apache.org/jira/browse/CAMEL-14565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14565: Fix Version/s: (was: 3.2.0) 3.3.0 > camel-spring-boot - Some auto configuration options has no descriptions > --- > > Key: CAMEL-14565 > URL: https://issues.apache.org/jira/browse/CAMEL-14565 > Project: Camel > Issue Type: Task > Components: camel-spring-boot-starters >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > [WARNING] Option camel.component.consul.cluster.service.acl-token has no > description > [WARNING] Option camel.component.consul.cluster.service.block-seconds has no > description > [WARNING] Option > camel.component.consul.cluster.service.connect-timeout-millis has no > description > [WARNING] Option camel.component.consul.cluster.service.consistency-mode has > no description > [WARNING] Option camel.component.consul.cluster.service.datacenter has no > description > [WARNING] Option camel.component.consul.cluster.service.first-index has no > description > [WARNING] Option camel.component.consul.cluster.service.near-node has no > description > [WARNING] Option camel.component.consul.cluster.service.node-meta has no > description > [WARNING] Option camel.component.consul.cluster.service.password has no > description > [WARNING] Option camel.component.consul.cluster.service.ping-instance has no > description > [WARNING] Option camel.component.consul.cluster.service.read-timeout-millis > has no description > [WARNING] Option camel.component.consul.cluster.service.recursive has no > description > [WARNING] Option camel.component.consul.cluster.service.root-path has no > description > [WARNING] Option camel.component.consul.cluster.service.session-lock-delay > has no description > [WARNING] Option > camel.component.consul.cluster.service.session-refresh-interval has no > description > [WARNING] Option camel.component.consul.cluster.service.session-ttl has no > description > [WARNING] Option > camel.component.consul.cluster.service.ssl-context-parameters has no > description > [WARNING] Option camel.component.consul.cluster.service.tags has no > description > [WARNING] Option camel.component.consul.cluster.service.url has no description > [WARNING] Option camel.component.consul.cluster.service.user-name has no > description > [WARNING] Option camel.component.consul.cluster.service.write-timeout-millis > has no description > [WARNING] Option camel.component.consul.health.check.repository.enabled has > no description > [WARNING] Option > camel.component.consul.health.check.repository.failure-threshold has no > description > [WARNING] Option camel.component.consul.health.check.repository.interval has > no description > [WARNING] Option camel.component.consul.service-registry.acl-token has no > description > [WARNING] Option camel.component.consul.service-registry.block-seconds has no > description > [WARNING] Option camel.component.consul.service-registry.check-interval has > no description > [WARNING] Option camel.component.consul.service-registry.check-ttl has no > description > [WARNING] Option > camel.component.consul.service-registry.connect-timeout-millis has no > description > [WARNING] Option camel.component.consul.service-registry.consistency-mode has > no description > [WARNING] Option camel.component.consul.service-registry.datacenter has no > description > [WARNING] Option camel.component.consul.service-registry.deregister-after has > no description > [WARNING] Option > camel.component.consul.service-registry.deregister-services-on-stop has no > description > [WARNING] Option camel.component.consul.service-registry.first-index has no > description > [WARNING] Option camel.component.consul.service-registry.near-node has no > description > [WARNING] Option camel.component.consul.service-registry.node-meta has no > description > [WARNING] Option > camel.component.consul.service-registry.override-service-host has no > description > [WARNING] Option camel.component.consul.service-registry.password has no > description > [WARNING] Option camel.component.consul.service-registry.ping-instance has no > description > [WARNING] Option camel.component.consul.service-registry.read-timeout-millis > has no description > [WARNING] Option camel.component.consul.service-registry.recursive has no > description > [WARNING] Option camel.component.consul.service-registry.service-host has no > description > [WARNING] Option > camel.component.consul.service-registry.ssl-context-parameters has no > description > [WARNING] Option camel.component.consul.service-registry.tags has no > description > [WARNING] Option
[jira] [Updated] (CAMEL-14565) camel-spring-boot - Some auto configuration options has no descriptions
[ https://issues.apache.org/jira/browse/CAMEL-14565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14565: Description: [WARNING] Option camel.component.consul.cluster.service.acl-token has no description [WARNING] Option camel.component.consul.cluster.service.block-seconds has no description [WARNING] Option camel.component.consul.cluster.service.connect-timeout-millis has no description [WARNING] Option camel.component.consul.cluster.service.consistency-mode has no description [WARNING] Option camel.component.consul.cluster.service.datacenter has no description [WARNING] Option camel.component.consul.cluster.service.first-index has no description [WARNING] Option camel.component.consul.cluster.service.near-node has no description [WARNING] Option camel.component.consul.cluster.service.node-meta has no description [WARNING] Option camel.component.consul.cluster.service.password has no description [WARNING] Option camel.component.consul.cluster.service.ping-instance has no description [WARNING] Option camel.component.consul.cluster.service.read-timeout-millis has no description [WARNING] Option camel.component.consul.cluster.service.recursive has no description [WARNING] Option camel.component.consul.cluster.service.root-path has no description [WARNING] Option camel.component.consul.cluster.service.session-lock-delay has no description [WARNING] Option camel.component.consul.cluster.service.session-refresh-interval has no description [WARNING] Option camel.component.consul.cluster.service.session-ttl has no description [WARNING] Option camel.component.consul.cluster.service.ssl-context-parameters has no description [WARNING] Option camel.component.consul.cluster.service.tags has no description [WARNING] Option camel.component.consul.cluster.service.url has no description [WARNING] Option camel.component.consul.cluster.service.user-name has no description [WARNING] Option camel.component.consul.cluster.service.write-timeout-millis has no description [WARNING] Option camel.component.consul.health.check.repository.enabled has no description [WARNING] Option camel.component.consul.health.check.repository.failure-threshold has no description [WARNING] Option camel.component.consul.health.check.repository.interval has no description [WARNING] Option camel.component.consul.service-registry.acl-token has no description [WARNING] Option camel.component.consul.service-registry.block-seconds has no description [WARNING] Option camel.component.consul.service-registry.check-interval has no description [WARNING] Option camel.component.consul.service-registry.check-ttl has no description [WARNING] Option camel.component.consul.service-registry.connect-timeout-millis has no description [WARNING] Option camel.component.consul.service-registry.consistency-mode has no description [WARNING] Option camel.component.consul.service-registry.datacenter has no description [WARNING] Option camel.component.consul.service-registry.deregister-after has no description [WARNING] Option camel.component.consul.service-registry.deregister-services-on-stop has no description [WARNING] Option camel.component.consul.service-registry.first-index has no description [WARNING] Option camel.component.consul.service-registry.near-node has no description [WARNING] Option camel.component.consul.service-registry.node-meta has no description [WARNING] Option camel.component.consul.service-registry.override-service-host has no description [WARNING] Option camel.component.consul.service-registry.password has no description [WARNING] Option camel.component.consul.service-registry.ping-instance has no description [WARNING] Option camel.component.consul.service-registry.read-timeout-millis has no description [WARNING] Option camel.component.consul.service-registry.recursive has no description [WARNING] Option camel.component.consul.service-registry.service-host has no description [WARNING] Option camel.component.consul.service-registry.ssl-context-parameters has no description [WARNING] Option camel.component.consul.service-registry.tags has no description [WARNING] Option camel.component.consul.service-registry.url has no description [WARNING] Option camel.component.consul.service-registry.user-name has no description [WARNING] Option camel.component.consul.service-registry.write-timeout-millis has no description [WARNING] The POM for org.apache.yetus:audience-annotations:jar:0.11.0 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [WARNING] Invalid POM for org.apache.yetus:audience-annotations:jar:0.11.0, transitive dependencies (if any) will not be available, enable debug logging for more details [WARNING] Option camel.component.zookeeper.cluster.service.auth-info-list has no description [WARNING] Option camel.component.zookeeper.cluster.service.base-path
[jira] [Commented] (CAMEL-14790) camel-undertow: remove spring-boot starter after refactor of elytron component
[ https://issues.apache.org/jira/browse/CAMEL-14790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071593#comment-17071593 ] Jiri Ondrusek commented on CAMEL-14790: --- Starter was removed in https://github.com/apache/camel-spring-boot/commit/bed913177bb27b470a0a17728d092502e956eff5 > camel-undertow: remove spring-boot starter after refactor of elytron component > -- > > Key: CAMEL-14790 > URL: https://issues.apache.org/jira/browse/CAMEL-14790 > Project: Camel > Issue Type: Task > Components: camel-undertow >Affects Versions: 3.2.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > Fix of https://issues.apache.org/jira/browse/CAMEL-14743 removes > elytron-component (but functionality is kept as plugin into camel-undertow) > If fix is approved, elytron starter has to be removed to prevent compilation > problems -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14790) camel-undertow: remove spring-boot starter after refactor of elytron component
[ https://issues.apache.org/jira/browse/CAMEL-14790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Ondrusek resolved CAMEL-14790. --- Fix Version/s: 3.2.0 Resolution: Fixed > camel-undertow: remove spring-boot starter after refactor of elytron component > -- > > Key: CAMEL-14790 > URL: https://issues.apache.org/jira/browse/CAMEL-14790 > Project: Camel > Issue Type: Task > Components: camel-undertow >Affects Versions: 3.2.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.2.0 > > > Fix of https://issues.apache.org/jira/browse/CAMEL-14743 removes > elytron-component (but functionality is kept as plugin into camel-undertow) > If fix is approved, elytron starter has to be removed to prevent compilation > problems -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071583#comment-17071583 ] Claus Ibsen commented on CAMEL-14742: - Colm can you add a section to the 3.1 -> 3.2 upgrade guide at https://github.com/apache/camel/blob/master/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc#upgrading-camel-31-to-32 About this being removed, thanks. > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.25.1, 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071578#comment-17071578 ] Claus Ibsen commented on CAMEL-14742: - I would caution against that, as that sun package is maybe not on OSGi. This is also a fringe feature that nobody really uses. Instead just mark it as deprecated and add a note recommend not to use. This is a patch release on 2.25.x so we should keep it stable. IMHO. > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.25.1, 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14809) Clear icon in the search box in navbar to clear the inner contents
[ https://issues.apache.org/jira/browse/CAMEL-14809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071572#comment-17071572 ] Zoran Regvart commented on CAMEL-14809: --- [~psingh1999587] makes sense to me. > Clear icon in the search box in navbar to clear the inner contents > --- > > Key: CAMEL-14809 > URL: https://issues.apache.org/jira/browse/CAMEL-14809 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Prerna Singh >Priority: Minor > > I think we can do something like this: > A clear button is displayed upon entering input in the search bar's text > field. Clicking on the clear button will erase the text field. > We can even do this for QuickLook up search bar. I think it will slightly > increase UX. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071570#comment-17071570 ] Colm O hEigeartaigh commented on CAMEL-14742: - I could merge this fix for 2.25.x? https://github.com/apache/camel/pull/3651 > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.25.1, 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14512) Allow reference to custom ClientInterceptor or Producer to customize authentication
[
https://issues.apache.org/jira/browse/CAMEL-14512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin updated CAMEL-14512:
---
Fix Version/s: 3.3.0
> Allow reference to custom ClientInterceptor or Producer to customize
> authentication
> ---
>
> Key: CAMEL-14512
> URL: https://issues.apache.org/jira/browse/CAMEL-14512
> Project: Camel
> Issue Type: Wish
> Components: camel-grpc
> Environment: * Java 11
> * SpringBoot 2.1.5.RELEASE
> * Camel 3.0.0-M2
> * Camel-Grpc-Starter 3.0.0-M2
>Reporter: Philipp
>Assignee: Dmitry Volodin
>Priority: Minor
> Fix For: 3.3.0
>
>
> The [GRPC
> component|https://github.com/apache/camel/blob/master/components/camel-grpc/src/main/docs/grpc-component.adoc]
> does currently not offer the possibility to intercept the connection
> establishment against the gRPC server out of the box.
> This prevents to add custom authentication to the channel/connection setup.
> And since the gRPC component does not offer this custom implementation out of
> the box, the currently only solution is:
> * Implement a custom {{GrpcComponent}}
> * Implement a custom {{GrpcEndpoint}}
> * Implement a custom {{GrpcProducer}} or {{DefaultAsyncProducer}}
> ** Override the {{doStart()}} method
> ** Instantiate the {{Channel}}
> ** Add a custom {{ClientInterceptor}} and override the {{interceptCall()}}
> method
> ** Add headers to the metadata of the prepared call
> Even though there are the properties {{authenticationType=JWT}},
> {{jwtSecret}}, {{jwtIssuer}} and so on, these arguments only allow constant
> strings. Therefore, no retrieval of OAuth tokens (for example) during the
> runtime is possible, but everything would have to be hard-coded.
> The [AHC-WS
> component|https://github.com/apache/camel/blob/master/components/camel-ahc-ws/src/main/docs/ahc-ws-component.adoc]
> in contrast, offers this possibility by implementing a custom
> {{AsyncHttpClient}} and pointing to it via the
> {{camel.component.ahc-ws.client}} property in the {{application.yml}}. Like
> this, the connection setup of the websocket can easily be intercepted by
> overriding {{DefaultAsyncHttpClient.prepareGet()}} where OAuth tokens (for
> example) can be passed and added to the handshake.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071569#comment-17071569 ] Zoran Regvart commented on CAMEL-13780: --- [~aashnajena] I think every page should be accessible from the menu. > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13530) Upgrade Milo to 0.3.8
[ https://issues.apache.org/jira/browse/CAMEL-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-13530: --- Fix Version/s: (was: 3.2.0) 3.3.0 > Upgrade Milo to 0.3.8 > - > > Key: CAMEL-13530 > URL: https://issues.apache.org/jira/browse/CAMEL-13530 > Project: Camel > Issue Type: Task > Components: camel-milo >Reporter: Andrea Cosentino >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.3.0 > > > Some breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13530) Upgrade Milo to 0.3.8
[ https://issues.apache.org/jira/browse/CAMEL-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071568#comment-17071568 ] Dmitry Volodin commented on CAMEL-13530: Claus, i will move to 3.3.0 > Upgrade Milo to 0.3.8 > - > > Key: CAMEL-13530 > URL: https://issues.apache.org/jira/browse/CAMEL-13530 > Project: Camel > Issue Type: Task > Components: camel-milo >Reporter: Andrea Cosentino >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.2.0 > > > Some breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14467) camel-jcache - Dynamically bypass the cache for lookups
[ https://issues.apache.org/jira/browse/CAMEL-14467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin updated CAMEL-14467: --- Fix Version/s: 3.x > camel-jcache - Dynamically bypass the cache for lookups > --- > > Key: CAMEL-14467 > URL: https://issues.apache.org/jira/browse/CAMEL-14467 > Project: Camel > Issue Type: New Feature > Components: camel-jcache >Affects Versions: 3.0.1 >Reporter: Jens Kleine-Herzbruch >Assignee: Dmitry Volodin >Priority: Major > Fix For: 3.x > > Attachments: bypass.diff > > > Currently, the JCachePolicy can only enabled or disable the cache completely > at startup. > > It would be useful to be able to enable or disable caching per request, > though. This change adds a new property "bypassExpression". If this > expression is set and returns true, the cache is ignored for lookup, the > underlying route is executed as normal, and the returned value is inserted in > the cache for future lookups. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071567#comment-17071567 ] Claus Ibsen commented on CAMEL-14742: - The older 3.x branches are EOL. For 2.25.x I think you should mark these options as deprecated (they are not in use by default anyway so no risk out of the box). > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.25.1, 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14634) documentation - Add page about endpoint-dsl and component-dsl to user guide
[ https://issues.apache.org/jira/browse/CAMEL-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14634: Fix Version/s: (was: 3.2.0) 3.3.0 > documentation - Add page about endpoint-dsl and component-dsl to user guide > --- > > Key: CAMEL-14634 > URL: https://issues.apache.org/jira/browse/CAMEL-14634 > Project: Camel > Issue Type: Improvement > Components: documentation, website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > We need to document the cool new features of endpoint-dsl and component-dsl > better. We should have a page for each of them, and added to the user guide > [https://camel.apache.org/manual/latest/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14742: Fix Version/s: (was: 3.1.1) (was: 3.0.2) > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.25.1, 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13530) Upgrade Milo to 0.3.8
[ https://issues.apache.org/jira/browse/CAMEL-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071564#comment-17071564 ] Claus Ibsen commented on CAMEL-13530: - Dmitry can you get this done soon or move to 3.3.0 > Upgrade Milo to 0.3.8 > - > > Key: CAMEL-13530 > URL: https://issues.apache.org/jira/browse/CAMEL-13530 > Project: Camel > Issue Type: Task > Components: camel-milo >Reporter: Andrea Cosentino >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 3.2.0 > > > Some breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14700) Improve colour contrast
[ https://issues.apache.org/jira/browse/CAMEL-14700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-14700. --- Resolution: Fixed We received a number of pull requests for this. It's better to have smaller targeted issues than one never ending issue. Resolving this, for any outstanding work create new issues with the description of the problem and outline of the solution. > Improve colour contrast > --- > > Key: CAMEL-14700 > URL: https://issues.apache.org/jira/browse/CAMEL-14700 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: Camel_website.png, camel_webpage.JPG, > image-2020-03-13-22-51-53-783.png > > Time Spent: 20m > Remaining Estimate: 0h > > We could get better usability for visually impaired folk by increasing the > colour contrast on the website. I've run some tools (Accessibility inspector > in Firefox) and there were some issues identified colour contrast of 2.69 > which doesn't meet the WACG standards as explained > [here|https://developer.mozilla.org/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable/Color_contrast]. > [~aashnajena] also shared some ideas in [a comment > here|https://issues.apache.org/jira/browse/CAMEL-14581?focusedCommentId=17057194=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17057194]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14658) Provide a simpler way to connect to a local s3 instance
[ https://issues.apache.org/jira/browse/CAMEL-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14658: Fix Version/s: (was: 3.2.0) 3.3.0 > Provide a simpler way to connect to a local s3 instance > --- > > Key: CAMEL-14658 > URL: https://issues.apache.org/jira/browse/CAMEL-14658 > Project: Camel > Issue Type: Improvement > Components: camel-aws-s3 >Reporter: Nicola Ferraro >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.3.0 > > > I've done this to workaround: > https://github.com/openshift-integration/camel-k-example-api/blob/master/test/MinioConfigurer.java > But it's technically enough to add a endpoint property to the component > options and other flags to have it configured via properties. > I don't know if this applies also to other aws endpoints, but it seems easy > for S3, cc: [~acosentino]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14587) AWS Components To Support useIAMCredentials
[ https://issues.apache.org/jira/browse/CAMEL-14587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14587: Fix Version/s: (was: 3.2.0) 3.3.0 > AWS Components To Support useIAMCredentials > > > Key: CAMEL-14587 > URL: https://issues.apache.org/jira/browse/CAMEL-14587 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Affects Versions: 3.0.0 >Reporter: Bojan Zekanovic >Assignee: Andrea Cosentino >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > It would be great if we could use useIAMCredentials with other AWS Camel > Components like you guys have it available with S3 Component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14618) Camel-aws-s3: Add an option to consumer to be able to move the consumed files to another bucket
[ https://issues.apache.org/jira/browse/CAMEL-14618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14618: Fix Version/s: (was: 3.2.0) 3.3.0 > Camel-aws-s3: Add an option to consumer to be able to move the consumed files > to another bucket > --- > > Key: CAMEL-14618 > URL: https://issues.apache.org/jira/browse/CAMEL-14618 > Project: Camel > Issue Type: Improvement > Components: camel-aws-s3 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.3.0 > > > Like deleteAfterRead but with a different bucket as target. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14584) camel-elytron - Only use the JARs really needed
[ https://issues.apache.org/jira/browse/CAMEL-14584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14584: Fix Version/s: (was: 3.2.0) 3.3.0 > camel-elytron - Only use the JARs really needed > --- > > Key: CAMEL-14584 > URL: https://issues.apache.org/jira/browse/CAMEL-14584 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.3.0 > > > Its massive dependency set, and we only need a smaller set for camel-elytron > [INFO] +- org.wildfly.security:wildfly-elytron:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-asn1:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-audit:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-server-sasl:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-auth-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-base:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-client:jar:1.11.2.Final:compile > [INFO] | | +- > org.wildfly.security:wildfly-elytron-credential-source-impl:jar:1.11.2.Final:compile > [INFO] | | \- > org.wildfly.security:wildfly-elytron-provider-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential-source-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-credential-store:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-basic:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-bearer:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-cert:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-deprecated:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-form:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-spnego:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-sso:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-http-util:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-jacc:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-jaspi:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-json-util:jar:1.11.2.Final:compile > [INFO] | +- org.wildfly.security:wildfly-elytron-jwt:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-keystore:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-digest:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-gssapi:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-http:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-oauth2:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-mechanism-scram:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-password-impl:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-permission:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-realm:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-realm-jdbc:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-realm-ldap:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-realm-token:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-sasl:jar:1.11.2.Final:compile > [INFO] | +- > org.wildfly.security:wildfly-elytron-sasl-anonymous:jar:1.11.2.Final:compile > [INFO] | +- >
[jira] [Updated] (CAMEL-14386) camel-aws - S3 get with include body = false reports a stream error WARN
[ https://issues.apache.org/jira/browse/CAMEL-14386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14386: Fix Version/s: (was: 3.2.0) 3.3.0 > camel-aws - S3 get with include body = false reports a stream error WARN > > > Key: CAMEL-14386 > URL: https://issues.apache.org/jira/browse/CAMEL-14386 > Project: Camel > Issue Type: Bug > Components: camel-aws >Affects Versions: 2.22.0 >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.3.0 > > > We should take a look at this > https://stackoverflow.com/questions/59650142/camel-aws-s3-not-all-bytes-were-read-from-the-s3objectinputstream-aborting-ht?noredirect=1#comment105490591_59650142 > And if its still a problem on 3.x, then try to fix it by doing that GET range > or whatever is needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13780: Fix Version/s: (was: 3.2.0) 3.3.0 > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14740) spring-boot - Error binding property in servlet-starter
[
https://issues.apache.org/jira/browse/CAMEL-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-14740.
-
Resolution: Fixed
> spring-boot - Error binding property in servlet-starter
> ---
>
> Key: CAMEL-14740
> URL: https://issues.apache.org/jira/browse/CAMEL-14740
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Reporter: Efanov Alexey
>Priority: Major
> Labels: starter
> Fix For: 3.2.0
>
>
> Hi,
> I have this dependencies
> {code:java}
> // Camel
> implementation 'org.apache.camel.springboot:camel-spring-boot-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jackson-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-jacksonxml-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-activemq-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-servlet-starter:3.1.0'
> implementation 'org.apache.camel.springboot:camel-rest-starter:3.1.0' {code}
> My application.properties
> {code:java}
> camel.component.servlet.mapping.enabled=true
> camel.component.servlet.mapping.context-path=/rest/*
> camel.rest.component=servlet
> camel.rest.binding-mode=json{code}
> When i run application i see this stacktrace
> {code:java}
> Exception in thread "CamelMainRunController" java.lang.RuntimeException:
> org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:90)
> at
> org.apache.camel.spring.boot.CamelMainRunController$DaemonTask.run(CamelMainRunController.java:53)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.apache.camel.PropertyBindingException: Error binding property
> (camel.component.servlet.mapping.enabled=true) with name: mapping.enabled on
> bean: org.apache.camel.component.servlet.ServletComponent@62562970 with
> value: true
> at
> org.apache.camel.main.BaseMainSupport.setPropertiesOnTarget(BaseMainSupport.java:176)
> at
> org.apache.camel.main.BaseMainSupport.autoConfigurationFromProperties(BaseMainSupport.java:993)
> at
> org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:545)
> at
> org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:587)
> at
> org.apache.camel.main.BaseMainSupport.initCamelContext(BaseMainSupport.java:423)
> at org.apache.camel.main.Main.doInit(Main.java:109)
> at
> org.apache.camel.support.service.ServiceSupport.init(ServiceSupport.java:83)
> at
> org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:112)
> at org.apache.camel.main.MainSupport.run(MainSupport.java:82)
> at
> org.apache.camel.spring.boot.CamelSpringBootApplicationController.run(CamelSpringBootApplicationController.java:85)
> ... 2 more
> {code}
> It always throw error on any first servlet property in configuration but all
> servlet properties binds correctly and works.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14715) Move karaf/osgi to separate git repository
[ https://issues.apache.org/jira/browse/CAMEL-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14715. - Resolution: Fixed > Move karaf/osgi to separate git repository > -- > > Key: CAMEL-14715 > URL: https://issues.apache.org/jira/browse/CAMEL-14715 > Project: Camel > Issue Type: Improvement > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.2.0 > > > See > https://camel.465427.n5.nabble.com/Moving-Karaf-OSGi-code-into-a-Camel-sub-project-td5859320.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14703) Salesforce report consumer throws IllegalArgumentException
[
https://issues.apache.org/jira/browse/CAMEL-14703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14703:
Fix Version/s: (was: 3.2.0)
3.3.0
> Salesforce report consumer throws IllegalArgumentException
> --
>
> Key: CAMEL-14703
> URL: https://issues.apache.org/jira/browse/CAMEL-14703
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.0.1
>Reporter: Jeff Peterson
>Priority: Minor
> Fix For: 3.3.0
>
> Attachments: error_in_breakpoint.PNG, stacktrace.txt,
> workbench_report_results.PNG
>
>
> When synchronously running a report and returning the results, an
> {{IllegalArgumentException}} is thrown due to a dataCell containing an
> {{escapedValue}} as a key. In the {{SummaryValue.class}} in the \{{setAny}}
> method the name of the key is checked and throws an error if its other than
> {{value}}.
> I'm assuming instead of throwing an error this should bypass any key with
> name other than {{value}}.
> Attached is a screenshot of a breakpoint where the error is thrown, the
> report's key:value pair run through workbench, and the stacktrace.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14805: Fix Version/s: (was: 3.2.0) 3.3.0 > Component - Use doInit for wiring instead of doStart > > > Key: CAMEL-14805 > URL: https://issues.apache.org/jira/browse/CAMEL-14805 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.3.0 > > > We should move logic from start to init for wiring and other similar things > that can be setup as early as possible for lightweight camel. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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 ] Claus Ibsen updated CAMEL-14771: Fix Version/s: (was: 3.2.0) 3.3.0 > 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 >Priority: Major > Fix For: 3.3.0 > > 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] [Commented] (CAMEL-14654) Create camel-azure-storage-blob component based on SDKv12
[ https://issues.apache.org/jira/browse/CAMEL-14654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071563#comment-17071563 ] Omar Al-Safi commented on CAMEL-14654: -- Actively working on this, the plan was to push it in 3.2.0. However, let's see how far I can accomplish this week, hoping to send the PR sometimes week if possible > Create camel-azure-storage-blob component based on SDKv12 > - > > Key: CAMEL-14654 > URL: https://issues.apache.org/jira/browse/CAMEL-14654 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.1.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Minor > Fix For: 3.3.0 > > > Per title -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-14654) Create camel-azure-storage-blob component based on SDKv12
[ https://issues.apache.org/jira/browse/CAMEL-14654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-14654 started by Omar Al-Safi. > Create camel-azure-storage-blob component based on SDKv12 > - > > Key: CAMEL-14654 > URL: https://issues.apache.org/jira/browse/CAMEL-14654 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.1.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Minor > Fix For: 3.3.0 > > > Per title -- This message was sent by Atlassian Jira (v8.3.4#803005)
