The Apache Jenkins build system has built Camel.trunk.notest (build #2395)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2395/
to view the results.
The Apache Jenkins build system has built Camel.2.14.x.notest (build #163)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.14.x.notest/163/
to view the results.
The Apache Jenkins build system has built Camel.2.15.x.notest (build #63)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.15.x.notest/63/
to view the results.
Fine, good luck! ;-)
It would be good, if you could also update [1] with the missing pieces. It
should be easier for the next RM...
[1] http://camel.apache.org/building.html
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Mem
Thanks Christian. I will add my key to 2.14.x branch as well.
I should cut the first release candidate tomorrow.
Cheers.
wt., 19.05.2015 o 21:50 użytkownik Christian Müller <
christian.muel...@gmail.com> napisał:
> It's not really a MUST, it's a good practice. The user can still check the
> KEY
Yes.
And you have to provide your Apache credentials to be able to upload the
release artifacts [1].
[1] http://www.apache.org/dev/publishing-maven-artifacts.html
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apach
You can find more about the key signing (party) here:
[1] http://wiki.apache.org/apachecon/PgpKeySigning
[2] http://www.apache.org/dev/release-signing.html
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel
It's not really a MUST, it's a good practice. The user can still check the
KEYS [1] file in our repo whether the key which was used to sign the
release is your key.
Unfortunately, the KEYS file doesn't contain your key. You have to update
the file first (MASTER, camel-2.15.x, camel-2.14.x).
[1]
ht
Just add it to the exclusions.
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Tue, May 19, 2015 at 9:2
Hi,
The RAT check now returns something like this:
grep -e ' !?' camel/examples/target/rat.txt
!? camel/examples/camel-example-spring/src/data/message2.xml
!? camel/examples/camel-example-spring/src/data/message1.xml
!? camel/examples/camel-example-spring-javaconfig/src/data/me
GitHub user coffeejolts opened a pull request:
https://github.com/apache/camel/pull/522
Added support for reference parameters to the Timer component
I added support for reference parameters to the Timer component. Users
should use the standard '#' notation to specify param values t
Github user sebi-hgdata closed the pull request at:
https://github.com/apache/camel/pull/521
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Hi
Thanks for helping out. I have granted your user karma.
On Tue, May 19, 2015 at 12:14 PM, akoufoudakis wrote:
> Dear all!
>
> Apologies for the late reply and slow reaction.
> Was landing the new job.
> Now you can find my name, Alexandros Koufoudakis, in the list of unlisted
> CLA's.
> So, I
Dear all!
Apologies for the late reply and slow reaction.
Was landing the new job.
Now you can find my name, Alexandros Koufoudakis, in the list of unlisted
CLA's.
So, I would like to repeat my request to get "karma", which allows me to
comment/edit the Apache Camel web site.
Thank you in advance
Github user victornoel closed the pull request at:
https://github.com/apache/camel/pull/518
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
15 matches
Mail list logo
