[GitHub] nicolaferraro closed issue #287: Support for runtime traits
nicolaferraro closed issue #287: Support for runtime traits URL: https://github.com/apache/camel-k/issues/287 This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[GitHub] nicolaferraro closed pull request #290: Runtime enhacements
nicolaferraro closed pull request #290: Runtime enhacements
URL: https://github.com/apache/camel-k/pull/290
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/runtime/camel-k-runtime-core/pom.xml
b/runtime/camel-k-runtime-core/pom.xml
new file mode 100644
index ..35774928
--- /dev/null
+++ b/runtime/camel-k-runtime-core/pom.xml
@@ -0,0 +1,82 @@
+
+
+http://maven.apache.org/POM/4.0.0;
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+
+org.apache.camel.k
+camel-k-runtime-parent
+0.1.1-SNAPSHOT
+
+4.0.0
+
+camel-k-runtime-core
+
+
+
+
+
+
+
+
+
+
+org.apache.camel
+camel-core
+
+
+org.slf4j
+slf4j-api
+${slf4j.version}
+
+
+org.apache.commons
+commons-lang3
+${commons-lang.version}
+
+
+
+
+
+
+
+
+
+org.junit.jupiter
+junit-jupiter-api
+${junit-jupiter.version}
+test
+
+
+org.junit.jupiter
+junit-jupiter-engine
+${junit-jupiter.version}
+test
+
+
+
+org.assertj
+assertj-core
+${assertj.version}
+test
+
+
+
+
diff --git a/runtime/jvm/src/main/java/org/apache/camel/k/jvm/Constants.java
b/runtime/camel-k-runtime-core/src/main/java/org/apache/camel/k/Constants.java
similarity index 80%
rename from runtime/jvm/src/main/java/org/apache/camel/k/jvm/Constants.java
rename to
runtime/camel-k-runtime-core/src/main/java/org/apache/camel/k/Constants.java
index d3cb4b7b..e00fed49 100644
--- a/runtime/jvm/src/main/java/org/apache/camel/k/jvm/Constants.java
+++
b/runtime/camel-k-runtime-core/src/main/java/org/apache/camel/k/Constants.java
@@ -14,16 +14,19 @@
* See the License for the specific language governing permissions and
* limitations under the License.
*/
-package org.apache.camel.k.jvm;
+package org.apache.camel.k;
public final class Constants {
public static final String ENV_CAMEL_K_ROUTES = "CAMEL_K_ROUTES";
public static final String ENV_CAMEL_K_CONF = "CAMEL_K_CONF";
public static final String ENV_CAMEL_K_CONF_D = "CAMEL_K_CONF_D";
+public static final String ENV_CAMEL_K_TRAITS = "CAMEL_K_TRAITS";
public static final String SCHEME_CLASSPATH = "classpath:";
public static final String SCHEME_FILE = "file:";
public static final String SCHEME_ENV = "env:";
public static final String LOGGING_LEVEL_PREFIX = "logging.level.";
+public static final String ROUTES_LOADER_RESOURCE_PATH =
"META-INF/services/org/apache/camel/k/loader/";
+public static final String RUNTIME_TRAIT_RESOURCE_PATH =
"META-INF/services/org/apache/camel/k/trait/";
private Constants() {
}
diff --git a/runtime/jvm/src/main/java/org/apache/camel/k/jvm/Language.java
b/runtime/camel-k-runtime-core/src/main/java/org/apache/camel/k/Language.java
similarity index 86%
rename from runtime/jvm/src/main/java/org/apache/camel/k/jvm/Language.java
rename to
runtime/camel-k-runtime-core/src/main/java/org/apache/camel/k/Language.java
index d041faa0..c338bd60 100644
--- a/runtime/jvm/src/main/java/org/apache/camel/k/jvm/Language.java
+++
b/runtime/camel-k-runtime-core/src/main/java/org/apache/camel/k/Language.java
@@ -14,45 +14,59 @@
* See the License for the specific language governing permissions and
* limitations under the License.
*/
-package org.apache.camel.k.jvm;
+package org.apache.camel.k;
import java.util.Arrays;
import java.util.Collections;
import java.util.List;
+import org.apache.camel.util.ObjectHelper;
import org.apache.commons.lang3.StringUtils;
public enum Language {
Unknown(
+"unknown",
Collections.emptyList(),
Collections.emptyList()),
JavaClass(
+"java-class",
Collections.singletonList("class"),
Collections.singletonList("class")),
JavaSource(
+"java-source",
Collections.singletonList("java"),
Collections.singletonList("java")),
JavaScript(
+"js",
Arrays.asList("js", "javascript"),
Collections.singletonList("js")),
Groovy(
+"groovy",
Collections.singletonList("groovy"),
Collections.singletonList("groovy")),
Xml(
+"xml",
Collections.singletonList("xml"),
Collections.singletonList("xml")),
Kotlin(
+"kotlin",
Re: Create an Apache Camel Twitter Account
So @cameltweet is only for dev, right? +1 for acquiring @ApacheCamel. On Fri, Dec 14, 2018 at 7:24 AM Onder SEZGIN wrote: > +1 > > On Thu, Dec 13, 2018 at 8:26 PM wrote: > > > +1. A twitter account and especially that account name would be nice. > > Am 13. Dez. 2018, 15:49 +0100 schrieb Willem Jiang < > willem.ji...@gmail.com > > >: > > > +1. > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Thu, Dec 13, 2018 at 9:22 PM Zoran Regvart > wrote: > > > > > > > > +1 > > > > > > > > Seems that @ApacheCamel on Twitter was abandoned, perhaps it's also > > > > inactive[1] and I don't mean to be rude or aggressive but it seems > > > > that this individual is also squatting[2] and/or violating the > > > > trademark policy[3]. > > > > > > > > If everyone is on board with this I think it should be a simple as > > > > reporting a trademark violation to Twitter[4] to gain access to that > > > > Twitter handle. > > > > > > > > zoran > > > > > > > > [1] > > https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts > > > > [2] > > > https://help.twitter.com/en/rules-and-policies/twitter-username-squatting > > > > [3] > > https://help.twitter.com/en/rules-and-policies/twitter-trademark-policy > > > > [4] https://help.twitter.com/forms/trademark > > > > On Thu, Dec 13, 2018 at 1:14 PM Andrea Cosentino > > > > wrote: > > > > > > > > > > What do you think about this? It could be useful to share news, > > posts etc. > > > > > > > > > > Feedback welcome. > > > > > > > > > > -- > > > > > Andrea Cosentino > > > > > -- > > > > > Apache Camel PMC Chair > > > > > Apache Karaf Committer > > > > > Apache Servicemix PMC Member > > > > > Email: ancosen1...@yahoo.com > > > > > Twitter: @oscerd2 > > > > > Github: oscerd > > > > > > > > > > > > > > > > -- > > > > Zoran Regvart > > >
Re: [CAMEL 3] Moving sandbox/camel-3.x to master
I think for the average the enterprise JDK user they may still use JDK 8 for a long time. If we start the Camel 3.x, we still need to maintain the Camel 2.x branch for a while. It could be great, if we can provide a roadmap of JDK8 support time, BTW, Spring has good backward compatibility for JDK 6,7,8[1] It could be useful if we can still provide the backward compatibility in Camel 3.x and if we cannot do that we need to drop a line for it. [1]https://spring.io/blog/2015/04/03/how-spring-achieves-compatibility-with-java-6-7-and-8 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Dec 13, 2018 at 3:19 PM Andrea Cosentino wrote: > > You're right, but if we always think about how much effort is needed to > switch to a new and different JDK, we will never move from JDK 8. > > I'd like to have other feedback on this by the way. > > For the compatibility matrix we need to it to the documentation too. > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Thursday, December 13, 2018, 8:14:04 AM GMT+1, Onder SEZGIN > wrote: > > > > > > Almost +1, (as points below affects the idea of where to using any camel > versions and even contributing because for example; > if you use (let's say JDK 8) and have come across a problem and solved in > your local branch 2.X and submitted and if Camel 3.X would require JDK 10 as > the base minimum version, it will create a regression effort, in terms of > building and executing on JDK 10. would it slow down the contribution > efforts? ) > > Can we also discuss the matters of compatibility matrix? Maybe having one > like in starters guide or in some other document. > I know we have pages [1] [2] > > [1] http://camel.apache.org/what-are-the-dependencies.html > [2] > https://github.com/apache/camel/blob/master/docs/user-manual/en/camel-jar-dependencies.adoc > > Having such matrix considering other integration platforms would be helpful > IMHO. > Such as Spring Boot, Karaf, CDI etcs... > > > > > On Wed, Dec 12, 2018 at 3:12 PM Claus Ibsen wrote: > > On Wed, Dec 12, 2018 at 1:11 PM Andrea Cosentino > > wrote: > >> > >> It makes sense to set a date. > >> > >> Once we checked the documentation and resolved doubts, > >> I propose Wed 19th Dec in the morning. > >> > >> Does it work for all? > >> > > > > +1 > > > >> Thanks. > >> > >> -- > >> Andrea Cosentino > >> -- > >> Apache Camel PMC Chair > >> Apache Karaf Committer > >> Apache Servicemix PMC Member > >> Email: ancosen1...@yahoo.com > >> Twitter: @oscerd2 > >> Github: oscerd > >> > >> > >> On Wednesday, December 12, 2018, 1:09:05 PM GMT+1, Claus Ibsen > >> wrote: > >> > >> > >> On Wed, Dec 12, 2018 at 12:14 PM Guillaume Nodet wrote: > >> > > >> > Sounds good to me. > >> > > >> > Fwiw, I've been working on the camel build those past days, trying to > >> > improve things a bit. I'll report when I have something in a correct > >> > shape. > >> > > >> > >> What if we set a date when we make the change? For example Friday 14th > >> December or Monday 17th eg? > >> > >> And we would need to update the contributing document > >> with a section about that Camel 2.x is now located in the 2.x branch, > >> and that master is for 3.x. > >> > >> I wonder if this change will affect the current release procedure of > >> Camel 2.x? For example when we need to do next round of patch releases > >> for 2.x and also the new 2.24.0 release, > >> is there something we need to update our release guides at > >> http://camel.apache.org/release-guide.html > >> > >> Gregor if you are listening, is there something on-top-of your head > >> you can think of? > >> > >> > >> > >> > >> > >> > Guillaume > >> > > >> > Le mer. 12 déc. 2018 à 11:54, Andrea Cosentino > >> > a écrit : > >> > > >> > > Hello, > >> > > > >> > > Since we started work of some cleanup about Camel 3 and it's already > >> > > aligned with master, I'd like to ask what do you think about switching > >> > > the > >> > > master to 3.x and create a 2.x branch for the activities on Camel 2.x.. > >> > > > >> > > What do you think about this? > >> > > > >> > > Thanks > >> > > > >> > > -- > >> > > Andrea Cosentino > >> > > -- > >> > > Apache Camel PMC Chair > >> > > Apache Karaf Committer > >> > > Apache Servicemix PMC Member > >> > > Email: ancosen1...@yahoo.com > >> > > Twitter: @oscerd2 > >> > > Github: oscerd > >> > > > >> > > >> > > >> > -- > >> > > >> > Guillaume Nodet > >> > >> > >> > >> > >> -- > >> Claus Ibsen > >> - > >> http://davsclaus.com @davsclaus > >> Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > -- > > Claus Ibsen > > - > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > >
GitHub user we can use on Jenkins
Hi Cameleers, I'd like to enable pull request builds for the camel-website git repository via GitHub. As the Jenkins at builds.apache.org is constantly over the API limit I needed to create a GitHub user[1]. I named the user `camelesi`, which according to a Welsh-English[2] is a she-camel (a female camel) in Welsh. I also find it quite funny. Reach out if you need a GitHub account or personal access token for it, I envision that this user will only be used to access the public (read-only) APIs and allow us to bypass the API limits. Though in future it might be useful to also interact with PRs. I've mistakenly created the wrong kind of credential, and I can't delete it, so I've created an INFRA[3] issue to have it deleted, hopefully that will happen soon, and then I can switch the website build from GitBox to GitHub. zoran [1] https://issues.apache.org/jira/browse/INFRA-16473?focusedCommentId=16515957=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16515957 [2] https://geiriaduracademi.org/?lang=en [3] https://issues.apache.org/jira/browse/INFRA-17438 -- Zoran Regvart
Re: [CAMEL 3] Moving sandbox/camel-3.x to master
Logged it https://issues.apache.org/jira/browse/CAMEL-13000 On Thu, 13 Dec 2018, 10:19 Andrea Cosentino You're right, but if we always think about how much effort is needed to > switch to a new and different JDK, we will never move from JDK 8. > > I'd like to have other feedback on this by the way. > > For the compatibility matrix we need to it to the documentation too. > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Thursday, December 13, 2018, 8:14:04 AM GMT+1, Onder SEZGIN < > ond...@apache.org> wrote: > > > > > > Almost +1, (as points below affects the idea of where to using any camel > versions and even contributing because for example; > if you use (let's say JDK 8) and have come across a problem and solved in > your local branch 2.X and submitted and if Camel 3.X would require JDK 10 > as the base minimum version, it will create a regression effort, in terms > of building and executing on JDK 10. would it slow down the contribution > efforts? ) > > Can we also discuss the matters of compatibility matrix? Maybe having one > like in starters guide or in some other document. > I know we have pages [1] [2] > > [1] http://camel.apache.org/what-are-the-dependencies.html > [2] > https://github.com/apache/camel/blob/master/docs/user-manual/en/camel-jar-dependencies.adoc > > Having such matrix considering other integration platforms would be > helpful IMHO. > Such as Spring Boot, Karaf, CDI etcs... > > > > > On Wed, Dec 12, 2018 at 3:12 PM Claus Ibsen wrote: > > On Wed, Dec 12, 2018 at 1:11 PM Andrea Cosentino > wrote: > >> > >> It makes sense to set a date. > >> > >> Once we checked the documentation and resolved doubts, > >> I propose Wed 19th Dec in the morning. > >> > >> Does it work for all? > >> > > > > +1 > > > >> Thanks. > >> > >> -- > >> Andrea Cosentino > >> -- > >> Apache Camel PMC Chair > >> Apache Karaf Committer > >> Apache Servicemix PMC Member > >> Email: ancosen1...@yahoo.com > >> Twitter: @oscerd2 > >> Github: oscerd > >> > >> > >> On Wednesday, December 12, 2018, 1:09:05 PM GMT+1, Claus Ibsen < > claus.ib...@gmail.com> wrote: > >> > >> > >> On Wed, Dec 12, 2018 at 12:14 PM Guillaume Nodet > wrote: > >> > > >> > Sounds good to me. > >> > > >> > Fwiw, I've been working on the camel build those past days, trying to > >> > improve things a bit. I'll report when I have something in a correct > shape. > >> > > >> > >> What if we set a date when we make the change? For example Friday 14th > >> December or Monday 17th eg? > >> > >> And we would need to update the contributing document > >> with a section about that Camel 2.x is now located in the 2.x branch, > >> and that master is for 3.x. > >> > >> I wonder if this change will affect the current release procedure of > >> Camel 2.x? For example when we need to do next round of patch releases > >> for 2.x and also the new 2.24.0 release, > >> is there something we need to update our release guides at > >> http://camel.apache.org/release-guide.html > >> > >> Gregor if you are listening, is there something on-top-of your head > >> you can think of? > >> > >> > >> > >> > >> > >> > Guillaume > >> > > >> > Le mer. 12 déc. 2018 à 11:54, Andrea Cosentino > >> > a écrit : > >> > > >> > > Hello, > >> > > > >> > > Since we started work of some cleanup about Camel 3 and it's already > >> > > aligned with master, I'd like to ask what do you think about > switching the > >> > > master to 3.x and create a 2.x branch for the activities on Camel > 2.x.. > >> > > > >> > > What do you think about this? > >> > > > >> > > Thanks > >> > > > >> > > -- > >> > > Andrea Cosentino > >> > > -- > >> > > Apache Camel PMC Chair > >> > > Apache Karaf Committer > >> > > Apache Servicemix PMC Member > >> > > Email: ancosen1...@yahoo.com > >> > > Twitter: @oscerd2 > >> > > Github: oscerd > >> > > > >> > > >> > > >> > -- > >> > > >> > Guillaume Nodet > >> > >> > >> > >> > >> -- > >> Claus Ibsen > >> - > >> http://davsclaus.com @davsclaus > >> Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > -- > > Claus Ibsen > > - > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > >
Re: Create an Apache Camel Twitter Account
+1 On Thu, Dec 13, 2018 at 8:26 PM wrote: > +1. A twitter account and especially that account name would be nice. > Am 13. Dez. 2018, 15:49 +0100 schrieb Willem Jiang >: > > +1. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Dec 13, 2018 at 9:22 PM Zoran Regvart wrote: > > > > > > +1 > > > > > > Seems that @ApacheCamel on Twitter was abandoned, perhaps it's also > > > inactive[1] and I don't mean to be rude or aggressive but it seems > > > that this individual is also squatting[2] and/or violating the > > > trademark policy[3]. > > > > > > If everyone is on board with this I think it should be a simple as > > > reporting a trademark violation to Twitter[4] to gain access to that > > > Twitter handle. > > > > > > zoran > > > > > > [1] > https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts > > > [2] > https://help.twitter.com/en/rules-and-policies/twitter-username-squatting > > > [3] > https://help.twitter.com/en/rules-and-policies/twitter-trademark-policy > > > [4] https://help.twitter.com/forms/trademark > > > On Thu, Dec 13, 2018 at 1:14 PM Andrea Cosentino > > > wrote: > > > > > > > > What do you think about this? It could be useful to share news, > posts etc. > > > > > > > > Feedback welcome. > > > > > > > > -- > > > > Andrea Cosentino > > > > -- > > > > Apache Camel PMC Chair > > > > Apache Karaf Committer > > > > Apache Servicemix PMC Member > > > > Email: ancosen1...@yahoo.com > > > > Twitter: @oscerd2 > > > > Github: oscerd > > > > > > > > > > > > -- > > > Zoran Regvart >
Re: Camel website
I forgot to say awesome! Comments inline. Sent from my iPhone > On Dec 13, 2018, at 1:27 AM, Zoran Regvart wrote: > > Hi David, > thanks for the feedback, I really appreciate it! > >> On Wed, Dec 12, 2018 at 7:25 PM David Jencks >> wrote: >> I don’t quite understand why, how, or where you are setting up symlinks for >> the components. Is there some reason not to put the expected antora >> directory structure inside each components expected maven directory >> structure and assemble them using antora? >> >> e.g. >> >> camel-*/src/main/doc/modules/component/pages/*.adoc > > Yeah I've thought about it, that moves the complexity from having a > single module with ~400 pages of component documentation to having > ~400 individual modules. We could evaluate that approach but on first > hand it seems even more complicated with little to gain. > I didn’t quite realize how many components there are. We’d have to automate keeping the list of components in site.yml synchronized with the actual components. While it would be easy enough to add more symlinks, it might also make it easier to add other resources (pictures, downloads) in using antora conventions. >> I haven’t set up anything nearly this complicated with antora so I could >> easily be missing something obvious :-) > > Neither have I, so keep the feedback coming, I could be missing a lot > of details here :) > >> If this doesn’t work I’d be tempted to try to patch antora to work with >> maven directory structure, do you know if this is impractical? > > I'm not sure that's the way we'd like to go -- it would make us > maintainers of a fork, doing symlinks looks like a pragmatic approach > to me. It's not that much to maintain I think[1]. That is certainly little code to maintain, thanks for pointing it out. I was thinking that supporting maven layout in antora would make antora much more usable directly for java projects so a contribution of such support might be welcome so we wouldn’t have to maintain it. However, I don’t know how open antora devs are to outside contributions. Thanks! David Jencks > > zoran > > [1] > https://github.com/apache/camel/blob/e5523701ca10458cc21f82bc0933f97009f8438f/docs/gulpfile.js#L8-L19 > -- > Zoran Regvart
Re: Create an Apache Camel Twitter Account
+1. A twitter account and especially that account name would be nice. Am 13. Dez. 2018, 15:49 +0100 schrieb Willem Jiang : > +1. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, Dec 13, 2018 at 9:22 PM Zoran Regvart wrote: > > > > +1 > > > > Seems that @ApacheCamel on Twitter was abandoned, perhaps it's also > > inactive[1] and I don't mean to be rude or aggressive but it seems > > that this individual is also squatting[2] and/or violating the > > trademark policy[3]. > > > > If everyone is on board with this I think it should be a simple as > > reporting a trademark violation to Twitter[4] to gain access to that > > Twitter handle. > > > > zoran > > > > [1] https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts > > [2] > > https://help.twitter.com/en/rules-and-policies/twitter-username-squatting > > [3] https://help.twitter.com/en/rules-and-policies/twitter-trademark-policy > > [4] https://help.twitter.com/forms/trademark > > On Thu, Dec 13, 2018 at 1:14 PM Andrea Cosentino > > wrote: > > > > > > What do you think about this? It could be useful to share news, posts etc. > > > > > > Feedback welcome. > > > > > > -- > > > Andrea Cosentino > > > -- > > > Apache Camel PMC Chair > > > Apache Karaf Committer > > > Apache Servicemix PMC Member > > > Email: ancosen1...@yahoo.com > > > Twitter: @oscerd2 > > > Github: oscerd > > > > > > > > -- > > Zoran Regvart
[GitHub] lburgazzoli opened a new pull request #291: refactor: consistent env var management in traits
lburgazzoli opened a new pull request #291: refactor: consistent env var management in traits URL: https://github.com/apache/camel-k/pull/291 With this PR I've tried to have a single way for setting env vars inside traits as we have Environment::EnvVar (not a nice name identifier) but it is limited as it does not support setting env vars using the downward API. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[GitHub] zregvart closed pull request #1: Add Camel K to staging website
zregvart closed pull request #1: Add Camel K to staging website URL: https://github.com/apache/camel-website/pull/1 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/.gitignore b/.gitignore index c911a3c..f174892 100644 --- a/.gitignore +++ b/.gitignore @@ -2,3 +2,8 @@ node_modules public static +.idea +*.iml +.project +.classpath +.metadata \ No newline at end of file diff --git a/config.toml b/config.toml index c0b1406..9f379e2 100644 --- a/config.toml +++ b/config.toml @@ -27,3 +27,10 @@ relativeURLs = true weight = 2 identifier = "components" url = "/manual/latest/" + +[[menu.main]] +name = "Camel K" +parent = "docs" +weight = 3 +identifier = "camel-k" +url = "/camel-k/latest/" diff --git a/site.yml b/site.yml index ba7d462..1c4a1e2 100644 --- a/site.yml +++ b/site.yml @@ -11,6 +11,9 @@ content: - url: https://gitbox.apache.org/repos/asf/camel.git branches: website start_path: docs/components + - url: g...@github.com:apache/camel-k.git +branches: antora +start_path: docs ui: bundle: This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[GitHub] nicolaferraro opened a new pull request #1: Add Camel K to staging website
nicolaferraro opened a new pull request #1: Add Camel K to staging website URL: https://github.com/apache/camel-website/pull/1 @zregvart this should automatically add the Camel K section built from the `antora` branch. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
Re: Camel website
On Thu, Dec 13, 2018 at 2:48 PM Nicola Ferraro wrote: > > Really cool! We have now a good starting point. > > How is the build triggered? Is it manual or we can setup some > automatic/PR-based builds (we have multiple repos)? Any branch or commit to `master` on `camel-website` git repostory triggers the build, which reminds me that pushing to staging should only happen from `master` branch. I need to add triggering of the website build from the Camel build on changes to the documentation. zoran -- Zoran Regvart
Re: Create an Apache Camel Twitter Account
+1. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Dec 13, 2018 at 9:22 PM Zoran Regvart wrote: > > +1 > > Seems that @ApacheCamel on Twitter was abandoned, perhaps it's also > inactive[1] and I don't mean to be rude or aggressive but it seems > that this individual is also squatting[2] and/or violating the > trademark policy[3]. > > If everyone is on board with this I think it should be a simple as > reporting a trademark violation to Twitter[4] to gain access to that > Twitter handle. > > zoran > > [1] https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts > [2] https://help.twitter.com/en/rules-and-policies/twitter-username-squatting > [3] https://help.twitter.com/en/rules-and-policies/twitter-trademark-policy > [4] https://help.twitter.com/forms/trademark > On Thu, Dec 13, 2018 at 1:14 PM Andrea Cosentino > wrote: > > > > What do you think about this? It could be useful to share news, posts etc. > > > > Feedback welcome. > > > > -- > > Andrea Cosentino > > -- > > Apache Camel PMC Chair > > Apache Karaf Committer > > Apache Servicemix PMC Member > > Email: ancosen1...@yahoo.com > > Twitter: @oscerd2 > > Github: oscerd > > > > -- > Zoran Regvart
Re: camel-example-cxf-blueprint documentation update request
Hi
Yeah sure we take PRs, that is also the preferred way. This allows us
better to review and collborate on the code.
On Thu, Dec 13, 2018 at 3:20 PM Miroslav Beranič
wrote:
>
> Hi Claus,
>
> I've just created JIRA at: https://issues.apache.org/jira/browse/CAMEL-12999
>
> I was asking if you take GitHub PR, I've created fork and pushed to it. I
> will and make PR now.
>
> Kind Regards,
> Miroslav
>
>
>
> V V čet., 13. dec. 2018 ob 15:15 je oseba Claus Ibsen
> napisala:
>
> > Hi
> >
> > Well spotted, so yeah you are as Andrea already said welcome to log a JIRA.
> > And we also love contributions, so a github PR to fix this is welcome.
> > https://github.com/apache/camel/blob/master/CONTRIBUTING.md
> > On Thu, Dec 13, 2018 at 2:37 PM Miroslav Beranič
> > wrote:
> > >
> > > Hi all,
> > >
> > > I am trying out CXF examples from Camel project. Version 2.23.0-SNAPSHOT
> > (
> > > build from GitHub, today ).
> > >
> > > When I follow along guidelines from:
> > > /camel/examples/camel-example-cxf-blueprint/README.md
> > >
> > > There is a step, to install bundle:
> > >
> > > install -s mvn:org.apache.camel/camel-example-cxf-blueprint/${version}
> > >
> > > It looks like, bundle package has changed from org.apache.camel to
> > > org.apache.camel.example, so correct line would be:
> > >
> > > install -s
> > > mvn:org.apache.camel.example/camel-example-cxf-blueprint/${version}
> > >
> > > With this change all works as documented.
> > >
> > > Quick search finds 21 matches in other example projects, that would have
> > to
> > > be updated.
> > >
> > > Kind Regards,
> > > Miroslav
> > >
> > >
> > > --
> > > Miroslav Beranič
> > > MIBESIS
> > > +386(0)40/814-843
> > > miroslav.bera...@mibesis.si
> > > http://www.mibesis.si
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Miroslav Beranič
> MIBESIS
> +386(0)40/814-843
> miroslav.bera...@mibesis.si
> http://www.mibesis.si
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: camel-example-cxf-blueprint documentation update request
Created GitHub PR at:
https://github.com/apache/camel/pull/2672
V V čet., 13. dec. 2018 ob 15:20 je oseba Miroslav Beranič <
miroslav.bera...@mibesis.si> napisala:
> Hi Claus,
>
> I've just created JIRA at:
> https://issues.apache.org/jira/browse/CAMEL-12999
>
> I was asking if you take GitHub PR, I've created fork and pushed to it. I
> will and make PR now.
>
> Kind Regards,
> Miroslav
>
>
>
> V V čet., 13. dec. 2018 ob 15:15 je oseba Claus Ibsen <
> claus.ib...@gmail.com> napisala:
>
>> Hi
>>
>> Well spotted, so yeah you are as Andrea already said welcome to log a
>> JIRA.
>> And we also love contributions, so a github PR to fix this is welcome.
>> https://github.com/apache/camel/blob/master/CONTRIBUTING.md
>> On Thu, Dec 13, 2018 at 2:37 PM Miroslav Beranič
>> wrote:
>> >
>> > Hi all,
>> >
>> > I am trying out CXF examples from Camel project. Version
>> 2.23.0-SNAPSHOT (
>> > build from GitHub, today ).
>> >
>> > When I follow along guidelines from:
>> > /camel/examples/camel-example-cxf-blueprint/README.md
>> >
>> > There is a step, to install bundle:
>> >
>> > install -s mvn:org.apache.camel/camel-example-cxf-blueprint/${version}
>> >
>> > It looks like, bundle package has changed from org.apache.camel to
>> > org.apache.camel.example, so correct line would be:
>> >
>> > install -s
>> > mvn:org.apache.camel.example/camel-example-cxf-blueprint/${version}
>> >
>> > With this change all works as documented.
>> >
>> > Quick search finds 21 matches in other example projects, that would
>> have to
>> > be updated.
>> >
>> > Kind Regards,
>> > Miroslav
>> >
>> >
>> > --
>> > Miroslav Beranič
>> > MIBESIS
>> > +386(0)40/814-843
>> > miroslav.bera...@mibesis.si
>> > http://www.mibesis.si
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>
>
> --
> Miroslav Beranič
> MIBESIS
> +386(0)40/814-843
> miroslav.bera...@mibesis.si
> http://www.mibesis.si
>
--
Miroslav Beranič
MIBESIS
+386(0)40/814-843
miroslav.bera...@mibesis.si
http://www.mibesis.si
Re: camel-example-cxf-blueprint documentation update request
Hi Claus,
I've just created JIRA at: https://issues.apache.org/jira/browse/CAMEL-12999
I was asking if you take GitHub PR, I've created fork and pushed to it. I
will and make PR now.
Kind Regards,
Miroslav
V V čet., 13. dec. 2018 ob 15:15 je oseba Claus Ibsen
napisala:
> Hi
>
> Well spotted, so yeah you are as Andrea already said welcome to log a JIRA.
> And we also love contributions, so a github PR to fix this is welcome.
> https://github.com/apache/camel/blob/master/CONTRIBUTING.md
> On Thu, Dec 13, 2018 at 2:37 PM Miroslav Beranič
> wrote:
> >
> > Hi all,
> >
> > I am trying out CXF examples from Camel project. Version 2.23.0-SNAPSHOT
> (
> > build from GitHub, today ).
> >
> > When I follow along guidelines from:
> > /camel/examples/camel-example-cxf-blueprint/README.md
> >
> > There is a step, to install bundle:
> >
> > install -s mvn:org.apache.camel/camel-example-cxf-blueprint/${version}
> >
> > It looks like, bundle package has changed from org.apache.camel to
> > org.apache.camel.example, so correct line would be:
> >
> > install -s
> > mvn:org.apache.camel.example/camel-example-cxf-blueprint/${version}
> >
> > With this change all works as documented.
> >
> > Quick search finds 21 matches in other example projects, that would have
> to
> > be updated.
> >
> > Kind Regards,
> > Miroslav
> >
> >
> > --
> > Miroslav Beranič
> > MIBESIS
> > +386(0)40/814-843
> > miroslav.bera...@mibesis.si
> > http://www.mibesis.si
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
--
Miroslav Beranič
MIBESIS
+386(0)40/814-843
miroslav.bera...@mibesis.si
http://www.mibesis.si
Re: camel-example-cxf-blueprint documentation update request
Hi
Well spotted, so yeah you are as Andrea already said welcome to log a JIRA.
And we also love contributions, so a github PR to fix this is welcome.
https://github.com/apache/camel/blob/master/CONTRIBUTING.md
On Thu, Dec 13, 2018 at 2:37 PM Miroslav Beranič
wrote:
>
> Hi all,
>
> I am trying out CXF examples from Camel project. Version 2.23.0-SNAPSHOT (
> build from GitHub, today ).
>
> When I follow along guidelines from:
> /camel/examples/camel-example-cxf-blueprint/README.md
>
> There is a step, to install bundle:
>
> install -s mvn:org.apache.camel/camel-example-cxf-blueprint/${version}
>
> It looks like, bundle package has changed from org.apache.camel to
> org.apache.camel.example, so correct line would be:
>
> install -s
> mvn:org.apache.camel.example/camel-example-cxf-blueprint/${version}
>
> With this change all works as documented.
>
> Quick search finds 21 matches in other example projects, that would have to
> be updated.
>
> Kind Regards,
> Miroslav
>
>
> --
> Miroslav Beranič
> MIBESIS
> +386(0)40/814-843
> miroslav.bera...@mibesis.si
> http://www.mibesis.si
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Create an Apache Camel Twitter Account
+1 Regards JB On 13/12/2018 15:13, Claus Ibsen wrote: On Thu, Dec 13, 2018 at 2:22 PM Zoran Regvart wrote: +1 Seems that @ApacheCamel on Twitter was abandoned, perhaps it's also inactive[1] and I don't mean to be rude or aggressive but it seems that this individual is also squatting[2] and/or violating the trademark policy[3]. If everyone is on board with this I think it should be a simple as reporting a trademark violation to Twitter[4] to gain access to that Twitter handle. +1 zoran [1] https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts [2] https://help.twitter.com/en/rules-and-policies/twitter-username-squatting [3] https://help.twitter.com/en/rules-and-policies/twitter-trademark-policy [4] https://help.twitter.com/forms/trademark On Thu, Dec 13, 2018 at 1:14 PM Andrea Cosentino wrote: What do you think about this? It could be useful to share news, posts etc. Feedback welcome. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd -- Zoran Regvart
Re: Create an Apache Camel Twitter Account
On Thu, Dec 13, 2018 at 2:22 PM Zoran Regvart wrote: > > +1 > > Seems that @ApacheCamel on Twitter was abandoned, perhaps it's also > inactive[1] and I don't mean to be rude or aggressive but it seems > that this individual is also squatting[2] and/or violating the > trademark policy[3]. > > If everyone is on board with this I think it should be a simple as > reporting a trademark violation to Twitter[4] to gain access to that > Twitter handle. > +1 > zoran > > [1] https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts > [2] https://help.twitter.com/en/rules-and-policies/twitter-username-squatting > [3] https://help.twitter.com/en/rules-and-policies/twitter-trademark-policy > [4] https://help.twitter.com/forms/trademark > On Thu, Dec 13, 2018 at 1:14 PM Andrea Cosentino > wrote: > > > > What do you think about this? It could be useful to share news, posts etc. > > > > Feedback welcome. > > > > -- > > Andrea Cosentino > > -- > > Apache Camel PMC Chair > > Apache Karaf Committer > > Apache Servicemix PMC Member > > Email: ancosen1...@yahoo.com > > Twitter: @oscerd2 > > Github: oscerd > > > > -- > Zoran Regvart -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Olingo4 ... sorry another one!
Hey Andrea, Happy to lodge JIRA issues once they are confirmed as bugs. I would like to think I have a handle on the problems but would still prefer some confirmation first. Cheers PGR On 13/12/2018 13:43, Andrea Cosentino wrote: > Hello, > > Can we please track everything on JIRA issues? > > This way we can have better vision of what has to be done :-) > > Thanks. > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Thursday, December 13, 2018, 2:41:26 PM GMT+1, phantomjinx > wrote: > > > > > > Hi Dmitry, > > Wonder if you would mind looking at this issue as well, please. Again, I may > been misunderstanding > something but I just cannot make headway. > > So have come up with a test[1] that demonstrates the problem. > > Essentially, after replacing the component in the context to bypass the null > serviceUri issue, the > route moves on to initialising the Olingo4Consumer. The latter tests the > 'read' method to ensure all > properties have been set [2]. However, this fails due to the properties 'edm' > and 'responseHandler' > being missing. > > These properties are not documented (since they appear to be output > properties). However, they are > added into the property names collection of the endpoint [3]. This collection > is compared against > the method signatures in the Olingo4AppEndpointConfiguration and neither > s/getEdm or > s/getResponseHandler exist hence the exception thrown. > > If you want any help in trying to solve either of the issues I've raised then > let me know as I've > had my head in them for a couple of days now. > > Thanks and regards > > Paul > > [1] > https://gist.github.com/phantomjinx/90ee08a989ddff4366d792cc621b36a9#file-properties-issue-java > [2] > https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/util/component/ApiConsumerHelper.java#L55 > [3] > https://github.com/apache/camel/blob/master/components/camel-olingo4/camel-olingo4-component/src/main/java/org/apache/camel/component/olingo4/Olingo4Endpoint.java#L150
Re: Olingo4 ... sorry another one!
Hello, Can we please track everything on JIRA issues? This way we can have better vision of what has to be done :-) Thanks. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, December 13, 2018, 2:41:26 PM GMT+1, phantomjinx wrote: Hi Dmitry, Wonder if you would mind looking at this issue as well, please. Again, I may been misunderstanding something but I just cannot make headway. So have come up with a test[1] that demonstrates the problem. Essentially, after replacing the component in the context to bypass the null serviceUri issue, the route moves on to initialising the Olingo4Consumer. The latter tests the 'read' method to ensure all properties have been set [2]. However, this fails due to the properties 'edm' and 'responseHandler' being missing. These properties are not documented (since they appear to be output properties). However, they are added into the property names collection of the endpoint [3]. This collection is compared against the method signatures in the Olingo4AppEndpointConfiguration and neither s/getEdm or s/getResponseHandler exist hence the exception thrown. If you want any help in trying to solve either of the issues I've raised then let me know as I've had my head in them for a couple of days now. Thanks and regards Paul [1] https://gist.github.com/phantomjinx/90ee08a989ddff4366d792cc621b36a9#file-properties-issue-java [2] https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/util/component/ApiConsumerHelper.java#L55 [3] https://github.com/apache/camel/blob/master/components/camel-olingo4/camel-olingo4-component/src/main/java/org/apache/camel/component/olingo4/Olingo4Endpoint.java#L150 -- Paul Richardson * “Confronted by the great record of this country, and the tremendous promise of its future, all they do is croak, ‘socialism.’" Harry Truman
Re: Camel website
Really cool! We have now a good starting point. How is the build triggered? Is it manual or we can setup some automatic/PR-based builds (we have multiple repos)? Nicola On Thu, Dec 13, 2018 at 12:36 PM Zoran Regvart wrote: > Hi Cameleers, > the first iteration of the build[1] of the new website is up on the > staging URL: > > https://camel.apache.org/staging/ > > it took a while to get all the kinks worked out but it seems OK now. > > Bare in mind that this is still very early, rough version: links will > be broken or point to wrong places, layout and styling is almost > non-existant. > > This at least gives us the opportunity to see any changes we make > really quickly online. > > I'll work on adding some READMEs to explain how to contribute and > cleanup JIRA issues around the new website next. > > zoran > > [1] > https://builds.apache.org/blue/organizations/jenkins/Camel.website/activity > -- > Zoran Regvart >
Olingo4 ... sorry another one!
Hi Dmitry, Wonder if you would mind looking at this issue as well, please. Again, I may been misunderstanding something but I just cannot make headway. So have come up with a test[1] that demonstrates the problem. Essentially, after replacing the component in the context to bypass the null serviceUri issue, the route moves on to initialising the Olingo4Consumer. The latter tests the 'read' method to ensure all properties have been set [2]. However, this fails due to the properties 'edm' and 'responseHandler' being missing. These properties are not documented (since they appear to be output properties). However, they are added into the property names collection of the endpoint [3]. This collection is compared against the method signatures in the Olingo4AppEndpointConfiguration and neither s/getEdm or s/getResponseHandler exist hence the exception thrown. If you want any help in trying to solve either of the issues I've raised then let me know as I've had my head in them for a couple of days now. Thanks and regards Paul [1] https://gist.github.com/phantomjinx/90ee08a989ddff4366d792cc621b36a9#file-properties-issue-java [2] https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/util/component/ApiConsumerHelper.java#L55 [3] https://github.com/apache/camel/blob/master/components/camel-olingo4/camel-olingo4-component/src/main/java/org/apache/camel/component/olingo4/Olingo4Endpoint.java#L150 -- Paul Richardson * “Confronted by the great record of this country, and the tremendous promise of its future, all they do is croak, ‘socialism.’" Harry Truman signature.asc Description: OpenPGP digital signature
Re: camel-example-cxf-blueprint documentation update request
Can you please raise a JIRA issue to track this?
Thanks
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Thursday, December 13, 2018, 2:37:43 PM GMT+1, Miroslav Beranič
wrote:
Hi all,
I am trying out CXF examples from Camel project. Version 2.23.0-SNAPSHOT (
build from GitHub, today ).
When I follow along guidelines from:
/camel/examples/camel-example-cxf-blueprint/README.md
There is a step, to install bundle:
install -s mvn:org.apache.camel/camel-example-cxf-blueprint/${version}
It looks like, bundle package has changed from org.apache.camel to
org.apache.camel.example, so correct line would be:
install -s
mvn:org.apache.camel.example/camel-example-cxf-blueprint/${version}
With this change all works as documented.
Quick search finds 21 matches in other example projects, that would have to
be updated.
Kind Regards,
Miroslav
--
Miroslav Beranič
MIBESIS
+386(0)40/814-843
miroslav.bera...@mibesis.si
http://www.mibesis.si
[GitHub] lburgazzoli opened a new pull request #290: Runtime enhacements
lburgazzoli opened a new pull request #290: Runtime enhacements URL: https://github.com/apache/camel-k/pull/290 This PR improves the camel-k runtime in the following areas: - it introduces a new concept "runtime trait" that can be enabled by the operator; this is useful to implement features like #259 - it standardizes on camel's own "service loader" for resource discovery instead of java's ServiceLoader which improves interoperability with different frameworks (spring-boot, etc) - restructures the runtime project layout Fixes #287 This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
camel-example-cxf-blueprint documentation update request
Hi all,
I am trying out CXF examples from Camel project. Version 2.23.0-SNAPSHOT (
build from GitHub, today ).
When I follow along guidelines from:
/camel/examples/camel-example-cxf-blueprint/README.md
There is a step, to install bundle:
install -s mvn:org.apache.camel/camel-example-cxf-blueprint/${version}
It looks like, bundle package has changed from org.apache.camel to
org.apache.camel.example, so correct line would be:
install -s
mvn:org.apache.camel.example/camel-example-cxf-blueprint/${version}
With this change all works as documented.
Quick search finds 21 matches in other example projects, that would have to
be updated.
Kind Regards,
Miroslav
--
Miroslav Beranič
MIBESIS
+386(0)40/814-843
miroslav.bera...@mibesis.si
http://www.mibesis.si
Re: Create an Apache Camel Twitter Account
Lets see how to handle this. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, December 13, 2018, 2:22:19 PM GMT+1, Zoran Regvart wrote: +1 Seems that @ApacheCamel on Twitter was abandoned, perhaps it's also inactive[1] and I don't mean to be rude or aggressive but it seems that this individual is also squatting[2] and/or violating the trademark policy[3]. If everyone is on board with this I think it should be a simple as reporting a trademark violation to Twitter[4] to gain access to that Twitter handle. zoran [1] https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts [2] https://help.twitter.com/en/rules-and-policies/twitter-username-squatting [3] https://help.twitter.com/en/rules-and-policies/twitter-trademark-policy [4] https://help.twitter.com/forms/trademark On Thu, Dec 13, 2018 at 1:14 PM Andrea Cosentino wrote: > > What do you think about this? It could be useful to share news, posts etc. > > Feedback welcome. > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd -- Zoran Regvart
Re: Create an Apache Camel Twitter Account
+1 Seems that @ApacheCamel on Twitter was abandoned, perhaps it's also inactive[1] and I don't mean to be rude or aggressive but it seems that this individual is also squatting[2] and/or violating the trademark policy[3]. If everyone is on board with this I think it should be a simple as reporting a trademark violation to Twitter[4] to gain access to that Twitter handle. zoran [1] https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts [2] https://help.twitter.com/en/rules-and-policies/twitter-username-squatting [3] https://help.twitter.com/en/rules-and-policies/twitter-trademark-policy [4] https://help.twitter.com/forms/trademark On Thu, Dec 13, 2018 at 1:14 PM Andrea Cosentino wrote: > > What do you think about this? It could be useful to share news, posts etc. > > Feedback welcome. > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd -- Zoran Regvart
R: Re: Create an Apache Camel Twitter Account
Hey no problem. I didn't mean to say it was the wrong thread. Thanks for your idea :-) Inviato da Yahoo Mail su Android Il gio, 13 dic, 2018 alle 13:49, francois.papon ha scritto: ok, you're right sorry regards, Francois Envoyé depuis mon smartphone Samsung Galaxy. Message d'origine De : Andrea Cosentino Date : 13/12/2018 16:34 (GMT+04:00) À : dev@camel.apache.org Objet : Re: Create an Apache Camel Twitter Account Personally I'd rather prefer to use IRC and the gitter channel. But this may a good discussion in a different thread :-) --Andrea Cosentino --Apache Camel PMC ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd On Thursday, December 13, 2018, 1:26:51 PM GMT+1, francois.papon wrote: Hi, I think it's a good idea :) May be also a channel on the ASF Slack ? regards, Francois Envoyé depuis mon smartphone Samsung Galaxy. Message d'origine De : Andrea Cosentino Date : 13/12/2018 16:14 (GMT+04:00) À : Dev Objet : Create an Apache Camel Twitter Account What do you think about this? It could be useful to share news, posts etc. Feedback welcome. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
Re: Create an Apache Camel Twitter Account
ok, you're right sorry regards, Francois Envoyé depuis mon smartphone Samsung Galaxy. Message d'origine De : Andrea Cosentino Date : 13/12/2018 16:34 (GMT+04:00) À : dev@camel.apache.org Objet : Re: Create an Apache Camel Twitter Account Personally I'd rather prefer to use IRC and the gitter channel. But this may a good discussion in a different thread :-) --Andrea Cosentino --Apache Camel PMC ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd On Thursday, December 13, 2018, 1:26:51 PM GMT+1, francois.papon wrote: Hi, I think it's a good idea :) May be also a channel on the ASF Slack ? regards, Francois Envoyé depuis mon smartphone Samsung Galaxy. Message d'origine De : Andrea Cosentino Date : 13/12/2018 16:14 (GMT+04:00) À : Dev Objet : Create an Apache Camel Twitter Account What do you think about this? It could be useful to share news, posts etc. Feedback welcome. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
Re: Create an Apache Camel Twitter Account
Personally I'd rather prefer to use IRC and the gitter channel. But this may a good discussion in a different thread :-) --Andrea Cosentino --Apache Camel PMC ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd On Thursday, December 13, 2018, 1:26:51 PM GMT+1, francois.papon wrote: Hi, I think it's a good idea :) May be also a channel on the ASF Slack ? regards, Francois Envoyé depuis mon smartphone Samsung Galaxy. Message d'origine De : Andrea Cosentino Date : 13/12/2018 16:14 (GMT+04:00) À : Dev Objet : Create an Apache Camel Twitter Account What do you think about this? It could be useful to share news, posts etc. Feedback welcome. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
Re: Create an Apache Camel Twitter Account
Hi, I think it's a good idea :) May be also a channel on the ASF Slack ? regards, Francois Envoyé depuis mon smartphone Samsung Galaxy. Message d'origine De : Andrea Cosentino Date : 13/12/2018 16:14 (GMT+04:00) À : Dev Objet : Create an Apache Camel Twitter Account What do you think about this? It could be useful to share news, posts etc. Feedback welcome. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
Create an Apache Camel Twitter Account
What do you think about this? It could be useful to share news, posts etc. Feedback welcome. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
Olingo4 serviceUri as query
Hi Paul!
Thanks for pointing.
I will look at this issue more detail and provide feedback or open jira
ticket.
четверг, 13 декабря 2018 г. пользователь phantomjinx написал:
> Hi,
>
> I am wondering if there is a bug in the olingo4 component/endpoint. The
> documentation[1] states that
> the serviceUri can be used as a query hence
>
> from("olingo4://read/Products?serviceUri=" + serviceUri);
>
> However, adding this to a simple test script[2], this results in an
> exception[3] that the serviceUri
> has not been set. Digging into the code it seems that the
> Olingo4Configuration is applied to the
> endpoint but only has the apiName and methodName set. Consequently, when
> the call
> configuration.getServiceUri() is called, the value is null.
>
> Any help much appreciated.
>
> Paul
>
> [1]
> https://github.com/apache/camel/blob/master/components/camel
> -olingo4/camel-olingo4-component/src/main/docs/olingo4-component.adoc
> [2] https://gist.github.com/phantomjinx/085df03915c5813a1f04b32e
> 09d00049#file-simpleolingo4test-java
> [3] https://gist.github.com/phantomjinx/085df03915c5813a1f04b32e
> 09d00049#gistcomment-2784671
>
> --
> Paul Richardson
>
> * “Confronted by the great record of this country, and the tremendous
> promise of its future, all
> they do is croak, ‘socialism.’"
>
> Harry Truman
>
>
>
--
--
Best regards,
Dmitry Volodin
[GitHub] lburgazzoli commented on issue #288: Support for camel context customizer
lburgazzoli commented on issue #288: Support for camel context customizer URL: https://github.com/apache/camel-k/pull/288#issuecomment-446941000 Will rework it This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[GitHub] lburgazzoli closed pull request #288: Support for camel context customizer
lburgazzoli closed pull request #288: Support for camel context customizer
URL: https://github.com/apache/camel-k/pull/288
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/runtime/api/pom.xml b/runtime/api/pom.xml
new file mode 100644
index ..e8e59e63
--- /dev/null
+++ b/runtime/api/pom.xml
@@ -0,0 +1,77 @@
+
+
+http://maven.apache.org/POM/4.0.0;
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+
+org.apache.camel.k
+camel-k-runtime-parent
+0.1.1-SNAPSHOT
+
+4.0.0
+
+camel-k-runtime-api
+
+
+
+
+
+
+
+
+
+
+org.apache.camel
+camel-core
+
+
+org.slf4j
+slf4j-api
+${slf4j.version}
+
+
+
+
+
+
+
+
+
+org.junit.jupiter
+junit-jupiter-api
+${junit-jupiter.version}
+test
+
+
+org.junit.jupiter
+junit-jupiter-engine
+${junit-jupiter.version}
+test
+
+
+
+org.assertj
+assertj-core
+${assertj.version}
+test
+
+
+
+
diff --git
a/runtime/api/src/main/java/org/apache/camel/k/CamelContextCustomizer.java
b/runtime/api/src/main/java/org/apache/camel/k/CamelContextCustomizer.java
new file mode 100644
index ..11a2ae02
--- /dev/null
+++ b/runtime/api/src/main/java/org/apache/camel/k/CamelContextCustomizer.java
@@ -0,0 +1,28 @@
+package org.apache.camel.k;
+
+import org.apache.camel.CamelContext;
+
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+@FunctionalInterface
+public interface CamelContextCustomizer {
+/**
+ * Perform CamelContext customization.
+ */
+void customize(CamelContext camelContext);
+}
diff --git
a/runtime/jvm/src/main/java/org/apache/camel/k/jvm/RuntimeRegistry.java
b/runtime/api/src/main/java/org/apache/camel/k/RuntimeRegistry.java
similarity index 96%
rename from
runtime/jvm/src/main/java/org/apache/camel/k/jvm/RuntimeRegistry.java
rename to runtime/api/src/main/java/org/apache/camel/k/RuntimeRegistry.java
index 7e13a283..895fe339 100644
--- a/runtime/jvm/src/main/java/org/apache/camel/k/jvm/RuntimeRegistry.java
+++ b/runtime/api/src/main/java/org/apache/camel/k/RuntimeRegistry.java
@@ -14,17 +14,13 @@
* See the License for the specific language governing permissions and
* limitations under the License.
*/
-package org.apache.camel.k.jvm;
+package org.apache.camel.k;
import java.util.Map;
import org.apache.camel.spi.Registry;
public interface RuntimeRegistry extends Registry {
-
-/**
- *
- */
void bind(String name, Object bean);
@SuppressWarnings("deprecation")
diff --git
a/runtime/api/src/main/java/org/apache/camel/k/RuntimeRegistryAware.java
b/runtime/api/src/main/java/org/apache/camel/k/RuntimeRegistryAware.java
new file mode 100644
index ..f440aa05
--- /dev/null
+++ b/runtime/api/src/main/java/org/apache/camel/k/RuntimeRegistryAware.java
@@ -0,0 +1,23 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific
Re: Camel website
Hi Cameleers, the first iteration of the build[1] of the new website is up on the staging URL: https://camel.apache.org/staging/ it took a while to get all the kinks worked out but it seems OK now. Bare in mind that this is still very early, rough version: links will be broken or point to wrong places, layout and styling is almost non-existant. This at least gives us the opportunity to see any changes we make really quickly online. I'll work on adding some READMEs to explain how to contribute and cleanup JIRA issues around the new website next. zoran [1] https://builds.apache.org/blue/organizations/jenkins/Camel.website/activity -- Zoran Regvart
Olingo4 serviceUri as query
Hi,
I am wondering if there is a bug in the olingo4 component/endpoint. The
documentation[1] states that
the serviceUri can be used as a query hence
from("olingo4://read/Products?serviceUri=" + serviceUri);
However, adding this to a simple test script[2], this results in an
exception[3] that the serviceUri
has not been set. Digging into the code it seems that the Olingo4Configuration
is applied to the
endpoint but only has the apiName and methodName set. Consequently, when the
call
configuration.getServiceUri() is called, the value is null.
Any help much appreciated.
Paul
[1]
https://github.com/apache/camel/blob/master/components/camel-olingo4/camel-olingo4-component/src/main/docs/olingo4-component.adoc
[2]
https://gist.github.com/phantomjinx/085df03915c5813a1f04b32e09d00049#file-simpleolingo4test-java
[3]
https://gist.github.com/phantomjinx/085df03915c5813a1f04b32e09d00049#gistcomment-2784671
--
Paul Richardson
* “Confronted by the great record of this country, and the tremendous promise
of its future, all
they do is croak, ‘socialism.’"
Harry Truman
signature.asc
Description: OpenPGP digital signature
[GitHub] nicolaferraro opened a new issue #289: Be revision-friendly and do not use revisions by default on Knative profile
nicolaferraro opened a new issue #289: Be revision-friendly and do not use revisions by default on Knative profile URL: https://github.com/apache/camel-k/issues/289 Service revisions are a nice thing as they allow to route traffic to different versions of the integration at the same time if needed. But each time you do a redeploy a new revision (pod, running) is added and it scales down only after 5 minutes. What's even worse is that if the deployment fails it's retried multiple times, generating at every cycle a new revision, blocking the whole cluster. We should understand why a redeployment results in two different revisions if nothing changes. We should use a different strategy by default, to avoid creating multiple pods if not required. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
Re: [HEADS UP] - Apache Camel route coverage tooling on the way
Hi On Thu, Dec 13, 2018 at 11:18 AM Pontus Ullgren wrote: > > Hi, > > Was there ever a support added to create cobertura reports or any > other way to plugin this with sonar based on this tooling ? > > If not I will have a small team of developers available in the > beginning of next year that are interested to taking a stab at > implementing this. > But if it is already in the works I guess our time is better spend on > some other task. > No we have not started such task. Sounds great if you have a team of developers whom want to take a stab at this. We love contributions. > Cheers > Pontus Ullgren > On Mon, Oct 9, 2017 at 10:18 AM Claus Ibsen wrote: > > > > Hi > > > > Just blogged and recorded a video about some cool new tooling on the > > way for Apache Camel 2.21. > > > > Route coverage of Camel routes has been asked from time to time in the > > community. So its good to finally say to the community that we have > > something on the way. And that they can reuse that and build on top of > > it to integrate this with their infrastructure such as CI servers, > > SonarType reporting and whatnot. The intention is to have the APIs and > > functionality out of the box from Apache Camel, and then vendors and > > others can use that. > > > > Anyway more details on the blog and with a video recording > > http://www.davsclaus.com/2017/10/apache-camel-route-coverage-tooling-on.html > > > > > > > > -- > > Claus Ibsen > > - > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Apache Camel route coverage tooling on the way
Hi, Was there ever a support added to create cobertura reports or any other way to plugin this with sonar based on this tooling ? If not I will have a small team of developers available in the beginning of next year that are interested to taking a stab at implementing this. But if it is already in the works I guess our time is better spend on some other task. Cheers Pontus Ullgren On Mon, Oct 9, 2017 at 10:18 AM Claus Ibsen wrote: > > Hi > > Just blogged and recorded a video about some cool new tooling on the > way for Apache Camel 2.21. > > Route coverage of Camel routes has been asked from time to time in the > community. So its good to finally say to the community that we have > something on the way. And that they can reuse that and build on top of > it to integrate this with their infrastructure such as CI servers, > SonarType reporting and whatnot. The intention is to have the APIs and > functionality out of the box from Apache Camel, and then vendors and > others can use that. > > Anyway more details on the blog and with a video recording > http://www.davsclaus.com/2017/10/apache-camel-route-coverage-tooling-on.html > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel website
Hi Nicola, On Thu, Dec 13, 2018 at 10:19 AM Nicola Ferraro wrote: > > I've started to refactor current Camel K doc for Antora. Results are > promising, I've rendered them in a temporary site > https://www.nicolaferraro.me/website-experiments/. > Website is rendered from [1] using the Antora default template, so I think > it would look nicer with the official Camel template. The current template in the `camel-website` git repostory[1] is really basic adaptation of the default theme, I'll polish it a bit more, at least by using the color palette from the logo and adding the logo in the top navigation bar. But this is something I'd like to see contributions from someone with design skills. The Hugo theme there is also super basic (well, just a header and a footer right now), but it loads the Camel Antora UI theme, so any changes to that will reflect both in the documentation and in the other website pages. > The only issue I've found so far is about links. I've used > xref:module/thefile.adoc to add cross links between pages, but this way > it's no more possible to navigate the adoc pages on github in [2]. Yeah, I've noticed that also, I think this is one of the core principles of Antora and it's one that we have to adopt to on our end. But it also has the great opportunity to link to pages between modules, so a page from Camel-K can easily point to a page in the user manual or component reference without knowing the exact URL or path in the directory structure to it. > That is fine, but this means we'll switch to Antora-based doc in Camel K > only when the staging site is available (so we can point users to that from > the README). Cool :) I'm seeing some permission issues as I run the node/antora/yarn/hugo within a Docker container on the build server. Hope to get that sorted soon. > Wdyt? Awesome work, glad it works on Camel in the clouds also :) zoran [1] https://github.com/apache/camel-website/tree/master/antora-ui-camel -- Zoran Regvart
Re: Camel website
Hi Önder, thanks for the feedback! On Thu, Dec 13, 2018 at 7:56 AM Onder SEZGIN wrote: > There is one point i am not %100 sure as we always say that documents will > be auto-generated from source code in asciidoc format and we also have > variosu other pages edited manually (especially examples for components). > After all these, are we going to keep all manually edited pages in > somewhere or we aim to drop them of from the offical documentation and have > them in somewhere else. That's also one of the reasons I think Antora is a good choice. The only way to build documentation is to version it in source control. So for examples we can have an additional Antora module just with the examples. This can then be versioned (or not). I don't see an issue with having more documentation, manually or auto-generated, I think we should embrace automation (as we have) on the parts that can be extracted from the source. This is somewhat reflected in the why I envisioned the current documentation being incorporated: user manual is always built from `master`, and for component documentation we can have one from `master` and multiple for older (maintained) releases. I hope this clarifies my position a bit, if it doesn't please let's keep this conversation going. > And one note i have in terms of documentation, (there are of course quite a > lot of books) is that having doc pages around where different integration > flavours using even small pieces of camel would be very helpful. (of course > there is also blog posts, tutorials and etc... ). surely having such pages > and maintaining them will bring lots of doc management issues and maybe > JIRAs to follow up but in the longer run it will be a great doc base to > start using camel for devs at any level. and maybe maintaing those doc > bases with diffferent versions of camel and upgrading and fixing them is > also a bit of hassle but it will keep track of changes in different > integration styles and env. (CDI, Blueprint, Spring Boot, Karaf, > Standalone, Camel-K), etcc... Just an idea which may get deeper ?? That's a good point, keeping the documentation up to date is a big task we all have to take on. I'm hoping that having it in versioned in git and with a 'Edit' link on the website that takes you to GitHub will help drive contributions to the documentation via pull requests. We should really take care on the new website that this way of contribution is really smooth and easy. zoran -- Zoran Regvart
Re: Camel website
Hi David, thanks for the feedback, I really appreciate it! On Wed, Dec 12, 2018 at 7:25 PM David Jencks wrote: > I don’t quite understand why, how, or where you are setting up symlinks for > the components. Is there some reason not to put the expected antora > directory structure inside each components expected maven directory > structure and assemble them using antora? > > e.g. > > camel-*/src/main/doc/modules/component/pages/*.adoc Yeah I've thought about it, that moves the complexity from having a single module with ~400 pages of component documentation to having ~400 individual modules. We could evaluate that approach but on first hand it seems even more complicated with little to gain. > I haven’t set up anything nearly this complicated with antora so I could > easily be missing something obvious :-) Neither have I, so keep the feedback coming, I could be missing a lot of details here :) > If this doesn’t work I’d be tempted to try to patch antora to work with maven > directory structure, do you know if this is impractical? I'm not sure that's the way we'd like to go -- it would make us maintainers of a fork, doing symlinks looks like a pragmatic approach to me. It's not that much to maintain I think[1]. zoran [1] https://github.com/apache/camel/blob/e5523701ca10458cc21f82bc0933f97009f8438f/docs/gulpfile.js#L8-L19 -- Zoran Regvart
Re: Camel website
I've started to refactor current Camel K doc for Antora. Results are promising, I've rendered them in a temporary site https://www.nicolaferraro.me/website-experiments/. Website is rendered from [1] using the Antora default template, so I think it would look nicer with the official Camel template. The only issue I've found so far is about links. I've used xref:module/thefile.adoc to add cross links between pages, but this way it's no more possible to navigate the adoc pages on github in [2]. That is fine, but this means we'll switch to Antora-based doc in Camel K only when the staging site is available (so we can point users to that from the README). Wdyt? Nicola Refs: [1]: https://github.com/nicolaferraro/website-experiments [2]: https://github.com/nicolaferraro/camel-k/tree/antora/docs/modules/ROOT/pages On Thu, Dec 13, 2018 at 7:56 AM Onder SEZGIN wrote: > Hi, > > Thanks Zoran, it is really great effort. > As i did not have experience with Antora and was following up with previous > effort where we used Hugo, webpack & gulp + ascii doctor. > Both approaches seems having trade-offs, i think better one is where we can > do progress as web-site under construction affects much of experience in > user experience terms especially when they start using any piece as > newbies. > > Still +1 and an will try to follow up with Antora approach and try to help > in the fields where i can. > > There is one point i am not %100 sure as we always say that documents will > be auto-generated from source code in asciidoc format and we also have > variosu other pages edited manually (especially examples for components). > After all these, are we going to keep all manually edited pages in > somewhere or we aim to drop them of from the offical documentation and have > them in somewhere else. > > And one note i have in terms of documentation, (there are of course quite a > lot of books) is that having doc pages around where different integration > flavours using even small pieces of camel would be very helpful. (of course > there is also blog posts, tutorials and etc... ). surely having such pages > and maintaining them will bring lots of doc management issues and maybe > JIRAs to follow up but in the longer run it will be a great doc base to > start using camel for devs at any level. and maybe maintaing those doc > bases with diffferent versions of camel and upgrading and fixing them is > also a bit of hassle but it will keep track of changes in different > integration styles and env. (CDI, Blueprint, Spring Boot, Karaf, > Standalone, Camel-K), etcc... Just an idea which may get deeper ?? > > Thanks again. > > Önder > > > On Wed, Dec 12, 2018 at 9:54 PM wrote: > > > Awesome Zoran! Great work!:) > > Am 12. Dez. 2018, 19:25 +0100 schrieb David Jencks < > > david.a.jen...@gmail.com>: > > > Hi Zoran, > > > > > > I don’t quite understand why, how, or where you are setting up symlinks > > for the components. Is there some reason not to put the expected antora > > directory structure inside each components expected maven directory > > structure and assemble them using antora? > > > > > > e.g. > > > > > > camel-*/src/main/doc/modules/component/pages/*.adoc > > > > > > I haven’t set up anything nearly this complicated with antora so I > could > > easily be missing something obvious :-) > > > > > > If this doesn’t work I’d be tempted to try to patch antora to work with > > maven directory structure, do you know if this is impractical? > > > > > > thanks > > > david jencks > > > > > > > > > > On Dec 12, 2018, at 3:10 AM, Zoran Regvart > wrote: > > > > > > > > Hi Cameleers, > > > > I've found some time to work on the website and here's the current > > > > status on the progress we made. > > > > > > > > We had some great contributions on the new website raging from the > > > > Asciidoctor theme and build for the user manual that Francois > > > > contributed, to the wiki pages migration that Alex, Andrea, Claus, > > > > Gregor, Pascal, Önder, Satyajit, Tadayoshi and Willem did (I'm sorry > > > > if I'm forgetting anyone). > > > > > > > > This started as an effort on the `website` branch where I tried to > > > > create a static build of the website using Hugo, a custom-built > > > > wrapper for Asciidoctor and a bunch of Gulp+Webpack tasks to tie it > > > > all together. That resulted in complex, slow to build and, obviously, > > > > for anyone besides me hard to contribute and comprehend ball of mud. > > > > > > > > I'm going to abandon that effort, and in turn focus on a (I think) > > > > simpler approach. > > > > > > > > The new approach is already looking (to me) much better in terms of > > > > simplicity and maintanability, and I'm about to polish it a bit and > > > > push it so that anyone can take a look and comment on it. > > > > > > > > I've focused on a Antora[1] based website build for the User manual > > > > and the Component reference -- this has great benefits of having > > > > support for documentation version out
[GitHub] nicolaferraro commented on issue #284: Platform options
nicolaferraro commented on issue #284: Platform options URL: https://github.com/apache/camel-k/issues/284#issuecomment-446883732 I think the spec field of the integrationplatform resource is the place where we should store that options. We already have the cluster type (Openshift/Kubernetes) and the profile to use (O/K/Knative), we can continue with info like that such as the global maven settings. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[GitHub] nicolaferraro closed issue #285: Inject camel-k version as environment variable
nicolaferraro closed issue #285: Inject camel-k version as environment variable URL: https://github.com/apache/camel-k/issues/285 This is an automated message from the Apache Git Service. To respond to the message, please log on 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 With regards, Apache Git Services
[GitHub] nicolaferraro closed pull request #283: Runtime cleanup
nicolaferraro closed pull request #283: Runtime cleanup
URL: https://github.com/apache/camel-k/pull/283
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/runtime/.maven-versions-rules.xml
b/runtime/.maven-versions-rules.xml
new file mode 100644
index ..44e512be
--- /dev/null
+++ b/runtime/.maven-versions-rules.xml
@@ -0,0 +1,39 @@
+
+
+http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0;
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+comparisonMethod="maven"
+
xsi:schemaLocation="http://mojo.codehaus.org/versions-maven-plugin/rule/2.0.0
http://mojo.codehaus.org/versions-maven-plugin/xsd/rule-2.0.0.xsd;>
+
+
+
+(?i).*Alpha(?:-?\d+)?
+(?i).*a(?:-?\d+)?
+(?i).*Beta(?:-?\d+)?
+(?i).*-B(?:-?\d+)?
+(?i).*RC(?:-?\d+)?
+(?i).*CR(?:-?\d+)?
+(?i).*M(?:-?\d+)?
+
+
+
+
+
+
\ No newline at end of file
diff --git a/runtime/camel-knative/.gitignore b/runtime/camel-knative/.gitignore
deleted file mode 100644
index ed929831..
--- a/runtime/camel-knative/.gitignore
+++ /dev/null
@@ -1,10 +0,0 @@
-target
-
-*.iml
-
-.idea
-.project
-.metadata
-.settings
-.factorypath
-.classpath
diff --git a/runtime/catalog-builder/.gitignore
b/runtime/catalog-builder/.gitignore
deleted file mode 100644
index ed929831..
--- a/runtime/catalog-builder/.gitignore
+++ /dev/null
@@ -1,10 +0,0 @@
-target
-
-*.iml
-
-.idea
-.project
-.metadata
-.settings
-.factorypath
-.classpath
diff --git a/runtime/dependency-lister/.gitignore
b/runtime/dependency-lister/.gitignore
deleted file mode 100644
index ed929831..
--- a/runtime/dependency-lister/.gitignore
+++ /dev/null
@@ -1,10 +0,0 @@
-target
-
-*.iml
-
-.idea
-.project
-.metadata
-.settings
-.factorypath
-.classpath
diff --git a/runtime/groovy/.gitignore b/runtime/groovy/.gitignore
deleted file mode 100644
index ed929831..
--- a/runtime/groovy/.gitignore
+++ /dev/null
@@ -1,10 +0,0 @@
-target
-
-*.iml
-
-.idea
-.project
-.metadata
-.settings
-.factorypath
-.classpath
diff --git a/runtime/jvm/.gitignore b/runtime/jvm/.gitignore
deleted file mode 100644
index ed929831..
--- a/runtime/jvm/.gitignore
+++ /dev/null
@@ -1,10 +0,0 @@
-target
-
-*.iml
-
-.idea
-.project
-.metadata
-.settings
-.factorypath
-.classpath
diff --git a/runtime/kotlin/.gitignore b/runtime/kotlin/.gitignore
deleted file mode 100644
index ed929831..
--- a/runtime/kotlin/.gitignore
+++ /dev/null
@@ -1,10 +0,0 @@
-target
-
-*.iml
-
-.idea
-.project
-.metadata
-.settings
-.factorypath
-.classpath
diff --git a/runtime/pom.xml b/runtime/pom.xml
index e7f2c3aa..7e421b9c 100644
--- a/runtime/pom.xml
+++ b/runtime/pom.xml
@@ -17,22 +17,17 @@
limitations under the License.
-->
-http://maven.apache.org/POM/4.0.0;
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
-
org.apache.camel.k
camel-k-runtime-parent
0.1.1-SNAPSHOT
pom
-
+
UTF-8
-
1.8
1.8
-
2.23.0
4.12
5.3.2
@@ -49,11 +44,12 @@
1.2-groovy-2.5
2.9.7
2.1.0.RELEASE
-
1.6.1
3.5.40
3.8.0
2.22.1
+2.7
+0.3.1
@@ -79,7 +75,7 @@
org.apache.maven.plugins
maven-compiler-plugin
-3.8.0
+${maven-compiler-plugin.version}
1.8
1.8
@@ -96,7 +92,7 @@
-
+
jvm
groovy
@@ -108,4 +104,42 @@
camel-knative
-
+
+
+deps
+
+false
+
+
+initialize
versions:display-dependency-updates
+
+
+org.commonjava.maven.plugins
+directory-maven-plugin
+${directory-maven-plugin.version}
+
+
+directories
+
+highest-basedir
+
+initialize
+
+camel-k.project.root
+
[GitHub] nicolaferraro closed pull request #286: Inject camel-k version as environment variable
nicolaferraro closed pull request #286: Inject camel-k version as environment
variable
URL: https://github.com/apache/camel-k/pull/286
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/pkg/trait/environment.go b/pkg/trait/environment.go
index f97ee134..9e05d451 100644
--- a/pkg/trait/environment.go
+++ b/pkg/trait/environment.go
@@ -19,6 +19,7 @@ package trait
import (
"github.com/apache/camel-k/pkg/apis/camel/v1alpha1"
+ "github.com/apache/camel-k/version"
appsv1 "k8s.io/api/apps/v1"
"k8s.io/api/core/v1"
)
@@ -29,8 +30,9 @@ type environmentTrait struct {
}
const (
- envVarNamespace = "NAMESPACE"
- envVarPodName = "POD_NAME"
+ envVarNamespace = "NAMESPACE"
+ envVarPodName = "POD_NAME"
+ envVarCamelKVersion = "CAMEL_K_VERSION"
)
func newEnvironmentTrait() *environmentTrait {
@@ -51,10 +53,16 @@ func (t *environmentTrait) Configure(e *Environment) (bool,
error) {
}
func (t *environmentTrait) Apply(e *Environment) error {
- if t.ContainerMeta {
- e.Resources.VisitDeployment(func(deployment *appsv1.Deployment)
{
- for i := 0; i <
len(deployment.Spec.Template.Spec.Containers); i++ {
- c :=
[i]
+ e.Resources.VisitDeployment(func(deployment *appsv1.Deployment) {
+ for i := 0; i < len(deployment.Spec.Template.Spec.Containers);
i++ {
+ c := [i]
+
+ c.Env = append(c.Env, v1.EnvVar{
+ Name: envVarCamelKVersion,
+ Value: version.Version,
+ })
+
+ if t.ContainerMeta {
c.Env = append(c.Env, v1.EnvVar{
Name: envVarNamespace,
ValueFrom: {
@@ -72,8 +80,8 @@ func (t *environmentTrait) Apply(e *Environment) error {
},
})
}
- })
- }
+ }
+ })
return nil
}
diff --git a/pkg/trait/environment_test.go b/pkg/trait/environment_test.go
index 12fdd316..4707a968 100644
--- a/pkg/trait/environment_test.go
+++ b/pkg/trait/environment_test.go
@@ -55,6 +55,7 @@ func TestDefaultEnvironment(t *testing.T) {
ns := false
name := false
+ ck := false
env.Resources.VisitDeployment(func(deployment *v1.Deployment) {
for _, e := range
deployment.Spec.Template.Spec.Containers[0].Env {
@@ -64,11 +65,15 @@ func TestDefaultEnvironment(t *testing.T) {
if e.Name == envVarPodName {
name = true
}
+ if e.Name == envVarCamelKVersion {
+ ck = true
+ }
}
})
assert.True(t, ns)
assert.True(t, name)
+ assert.True(t, ck)
}
func TestEnabledContainerMetaDataEnvVars(t *testing.T) {
@@ -105,6 +110,7 @@ func TestEnabledContainerMetaDataEnvVars(t *testing.T) {
ns := false
name := false
+ ck := false
env.Resources.VisitDeployment(func(deployment *v1.Deployment) {
for _, e := range
deployment.Spec.Template.Spec.Containers[0].Env {
@@ -114,11 +120,15 @@ func TestEnabledContainerMetaDataEnvVars(t *testing.T) {
if e.Name == envVarPodName {
name = true
}
+ if e.Name == envVarCamelKVersion {
+ ck = true
+ }
}
})
assert.True(t, ns)
assert.True(t, name)
+ assert.True(t, ck)
}
func TestDisabledContainerMetaDataEnvVars(t *testing.T) {
@@ -155,6 +165,7 @@ func TestDisabledContainerMetaDataEnvVars(t *testing.T) {
ns := false
name := false
+ ck := false
env.Resources.VisitDeployment(func(deployment *v1.Deployment) {
for _, e := range
deployment.Spec.Template.Spec.Containers[0].Env {
@@ -164,9 +175,13 @@ func TestDisabledContainerMetaDataEnvVars(t *testing.T) {
if e.Name == envVarPodName {
name = true
}
+ if e.Name == envVarCamelKVersion {
+ ck = true
+ }
}
})
assert.False(t, ns)
assert.False(t, name)
+ assert.True(t, ck)
}
This is an automated
