GitHub user sebi-hgdata opened a pull request:
https://github.com/apache/camel/pull/521
Resolving latest REST/Swagger TODOs
Hey,
This PR is for the latest rest dsl and swagger TODO s that were added
for PR https://github.com/apache/camel/pull/515 .
I will need to ad
The Apache Jenkins build system has built Camel.trunk.notest (build #2394)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2394/
to view the results.
The Apache Jenkins build system has built Camel.2.15.x.notest (build #62)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.15.x.notest/62/
to view the results.
The Apache Jenkins build system has built Camel.2.14.x.notest (build #162)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.14.x.notest/162/
to view the results.
I've set up everything on Apache/Maven side and downloaded fresh clone of
the project to the sandbox. Now I'm checking the licenses.
I've excluded src/signatures from RAT check, as we do in the master branch.
There are still some RAT licenses issues remaining - I will handle them
tomorrow and proc
> Your public key must also be cross-signed by other Apache committers
> (this can be done at key signing parties at ApacheCon for instance)
I don't recall any signing party at the last ApacheCon :) .
My key is not signed by other committers. Can I still release? I maybe
somebody can sign my key?
+1
Regards
JB
On 05/11/2015 05:43 PM, Claus Ibsen wrote:
Hi
I think we should if possible later this month release a new patch
release of this branch.
Any thoughts?
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
GitHub user manuelh9r opened a pull request:
https://github.com/apache/camel/pull/520
CAMEL-8647: Fix duplicated import-package statement for org.osgi.framâ¦
It seems that in change f058e02b00 the wildcard expression
org.osgi.framework*;version="[1.5,2)", was removed and replaced b
As we need to upload the private key to sign the artifacts, it not safe for us
to just leverage the Apache CI build box if every one can click the button to
do the release.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.itey
GitHub user carljmosca opened a pull request:
https://github.com/apache/camel/pull/519
initial commit support for service accounts
initial commit for google calendar suport for service accounts
You can merge this pull request into a Git repository by running:
$ git pull https:/
GitHub user victornoel opened a pull request:
https://github.com/apache/camel/pull/518
Maven plugins: m2e compatibility
Hi, here is a PR following a discussion on the mailing list.
The idea is that currently, the camel-package-maven-plugin does not
integrate very well with
Sounds like a plan. :) I will let you know how the release process goes on
my side later today.
And big +1 for Claus suggestions regarding the automated releases.
pon., 18.05.2015 o 10:07 użytkownik Andrea Cosentino
napisał:
> You're right.Maybe we can propose a different release process to ASF
You're right.Maybe we can propose a different release process to ASF.
Anyway, for the next release (after 2.14.3) I can do the RM to allow rotation
between us.
Andrea Cosentino--
Apache Camel Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Mon, May 18, 2015 at 9:29 AM, Henryk Konsek wrote:
> I can give it a try. I feel bad about not helping you with the releases ;) .
>
> I will start the release setup/process today late evening (EMEA time).
>
Yay thanks.
I wonder if ASF has on the table or we can reuse the CI servers to do
the
I can give it a try. I feel bad about not helping you with the releases ;) .
I will start the release setup/process today late evening (EMEA time).
Cheers!
pon., 18.05.2015 o 05:07 użytkownik Willem Jiang
napisał:
> Yeah, I think it could be good if we have more than one release manager :)
>
>
15 matches
Mail list logo
