> I suggest to open a ticket for each task which is not done yet at Google
> Code.
> @Henryk: Could you do this please!?
Sure, I'll do it.
> In my opinion we should release Camel extra 2.10.0 short term and postpone
> the still open tasks to Camel extra 2.10.1 or 2.11.0.
I agree, we can polish t
I suggest to open a ticket for each task which is not done yet at Google
Code.
@Henryk: Could you do this please!?
In my opinion we should release Camel extra 2.10.0 short term and postpone
the still open tasks to Camel extra 2.10.1 or 2.11.0.
Best,
Christian
On Wed, Sep 5, 2012 at 8:58 AM, Clau
>> Thanks for taking care of it. I will try to work together with Henryk on
>> the topics you mentioned.
Ok guys, in rev927 I've polished support for generating the GPG
signature of the deployed artifacts.
GPG Maven plugin will be activated only in the companion of the
'sonatype-oss-release' prof
> Thanks for taking care of it. I will try to work together with Henryk on
> the topics you mentioned.
My availability should increase starting from the beginning of the
next week. Count on me then :) .
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Hello Claus!
Thanks for taking care of it. I will try to work together with Henryk on
the topics you mentioned.
Best,
Christian
On Wed, Sep 5, 2012 at 8:58 AM, Claus Ibsen wrote:
> Hi
>
> Okay I have commited to camel-extra so it supports Camel 2.10 again.
>
> There is a few things I want to s
> Henryk, thanks for all your work. Could you make some progress with the
> release plugin?
Hi guys,
I remember about "Extras" and will continue to work on this topic soon
(in particular on signing artifacts and release plugin). However this
is my first week in the new job place, so I need some m
Hi
Okay I have commited to camel-extra so it supports Camel 2.10 again.
There is a few things I want to suggest being worked on before a release.
1)
Upgrade all the components to latest stable release of JAR deps (eg
some are old, like the hibernate etc).
I did this for camel-esper.
2)
Do not u
On Tue, Sep 4, 2012 at 10:48 PM, Christian Müller
wrote:
> Henryk, thanks for all your work. Could you make some progress with the
> release plugin?
>
> @Claus: Because you went ahead and changes the version to 2.11-SNAPSHOT,
> I'm afraid we cannot build a camel-extra 2.10.0 release. Has the
> vtd
Henryk, thanks for all your work. Could you make some progress with the
release plugin?
@Claus: Because you went ahead and changes the version to 2.11-SNAPSHOT,
I'm afraid we cannot build a camel-extra 2.10.0 release. Has the
vtdxml-component a dependency to Camel 2.11-SNAPSHOT? Can we revert your
> http://camel.apache.org/release-guide.html
Thanks Willem, that's what I needed :)
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Hi Henryk,
You can take a look at the release guide[1] to setup the maven release plugin
and GPG for signing.
http://camel.apache.org/release-guide.html
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willem
> Committed next batch (rev905). 20 licenses to go.
All licenses have been updated (rev906 + rev907). Maven build with RAT
check enabled [1] passes now.
OK Christian, what's the next step? You mentioned that you would like
to have artifacts signed or something like that. Could you tell me
more ab
> Another 20 licenses added in rev904. 50 left to go :) .
Committed next batch (rev905). 20 licenses to go.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
> Thanks a lot for your work so far. I'm sure there is enough left when you
> return. ;-)
Another 20 licenses added in rev904. 50 left to go :) .
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Hello Henryk!
Thanks a lot for your work so far. I'm sure there is enough left when you
return. ;-)
In the mean time I will work further on a Camel extra 2.10.0 release.
Have a nice time!
Best,
Christian
On Fri, Jul 13, 2012 at 1:46 PM, Henryk Konsek wrote:
> > Yeah, I'll handle this tomorrow.
> Yeah, I'll handle this tomorrow. I'll let you know when I'm done with it.
I've updated some part of the files with new license. I'm leaving to
holidays today, so I must stop it now. I'll continue in two weeks.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
> Do you consider updating all the files? Afterwards
Yeah, I'll handle this tomorrow. I'll let you know when I'm done with it.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Yes, we will go with this version:
/**
http://code.google.com/a/apache-extras.org/p/camel-extra/
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Publ
Hi guys,
> Without a copyright statement, the date range is kind of pointless and just
> something else to keep updating. I'd pull that as well.
So can we stick to the version below?
BTW If we accept the license today (or tomorrow at most) I could fix
Camel Extra sources before I leave to my w
On Wednesday, July 11, 2012 12:31:35 AM Christian Müller wrote:
> Hello Henryk, hello Dan,
>
> @Henryk: Thanks for your work!
>
> @Dan: I will go forward with this tomorrow (or may be Henryk if he find
> some time) and change this line from the license header. Than I would
> suggest to use the fo
Hello Henryk, hello Dan,
@Henryk: Thanks for your work!
@Dan: I will go forward with this tomorrow (or may be Henryk if he find
some time) and change this line from the license header. Than I would
suggest to use the following license header:
/
> Check my commit please :) .
>
> [1] Small version of license:
>
As I stated before, this license header is likely wrong. The code in the
files is most likely NOT copyright "Camel Extra Team" and thus that line
needs to be removed. Unless there is a specific copyright transfer, the
origi
> Ok done. I only need to reformat the POM XML to look nicer and then can
> commit.
Ok, commit submitted (rev896).
I've added 'withRatCheck' profile to the project so you can check it
against RAT validation issuing 'mvn install -PwithRatCheck'. This is a
good alternative for calling 'mvn
org.apa
> The last thing I want to check before we release camel-extra 2.10.0 is
> generating the asc files as we do it for our regular Apache Camel releases.
I can handle this too. I hope I can do it this week (before my holidays).
--
Henryk Konsek
http://henryk-konsek.blogspot.com
I'd remove the copyright line as it would most likely be wrong in most cases.
Daniel Kulp
http://dankulp.com/blog
On Jul 5, 2012, at 5:50 PM, Christian Müller
wrote:
> Before we do a camel-extra 2.10.0 release, I would like to discuss to
> change the license header in camel-extra to the foll
I would like to change the license headers for camel-extra and started a
discussion [1]. Feel free to add your opinion. If nobody complains about
this until Wednesday, I assume we reached lazy consensus and we can do the
change.
The last thing I want to check before we release camel-extra 2.10.0 i
> Thanks in advance...
Ok done. I only need to reformat the POM XML to look nicer and then can commit.
Just tell me one thing - is the header below official? Should I start
to apply it to all files in Camel Extra?
/*
Thanks in advance...
Christian
Sent from a mobile device
Am 06.07.2012 08:36 schrieb "Henryk Konsek" :
> > And if you have some minutes/hours free, could you try to get the
> > maven-rat-plugin (version 0.8) working with the new license headers?
>
> Sure, I'll handle this.
>
> --
> Henryk Konsek
> And if you have some minutes/hours free, could you try to get the
> maven-rat-plugin (version 0.8) working with the new license headers?
Sure, I'll handle this.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Before we do a camel-extra 2.10.0 release, I would like to discuss to
change the license header in camel-extra to the following one. It's the GNU
v2 license header template:
/**
Copyright (C) 2008 - 2012 Camel Ex
> When we tag camel-extra 2.10.0, we have to update the version to 2.10.0 in
> camel-extra too. For this, we need the Camel 2.10.0 artifacts (not only in
> a staging repo).
So Camel 2.10.0 arrived to Central [1]. Can I tag 2.10.0 version of
Camel-Extra then? I can almost hear Maven release:prepare
> The only thing I (or someone else) has to figure out is how we signe our
> artifacts and to which repo we want to upload it.
I'll take a look at this but before that I need to deal with broken
camel-hibernate build.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Hadrian canceled the release [1].
This means the existing tag will be replaced by a new one. So we have to
wait for this one...
Running camel-extra against Camel 2.10.0 is done in a few seconds. Tagging
it also. I don't see the advantage not to wait until Camel 2.10.0 is
released.
The only thing I
> When we tag camel-extra 2.10.0, we have to update the version to 2.10.0 in
> camel-extra too. For this, we need the Camel 2.10.0 artifacts (not only in
> a staging repo). This is the dependency I have in mind.
Actually I thought that we could just build+install the Camel 2.10
locally (from 2.10
Nothing to apologize to be pushy - as long you can live with a slightly
delayed answer... ;-)
I have to reach a deadline for an article for a German Java magazine which
took more time as expected...
When we tag camel-extra 2.10.0, we have to update the version to 2.10.0 in
camel-extra too. For thi
> Should we? Why can't we perform tagging simultaneously? We need to
> release regular Camel before Extras (since the latter depends on the
> former) but tagging can be done concurrently - correct me if I'm
> wrong :) .
So what about tagging Camel Extra simultaneously to regular Camel? :)
Sorry
> Hold on a while!
Fear not - I won't do anything without the green light from you :) .
> We should tag camel-extra AFTER we released camel 2.10.0. This is not done
> yet.
Should we? Why can't we perform tagging simultaneously? We need to
release regular Camel before Extras (since the latter dep
Hold on a while!
We should tag camel-extra AFTER we released camel 2.10.0. This is not done
yet.
And we didn't vote for the camel-extra releases in the past. This means the
release procedure for camel-extra releases are much more simpler and faster.
Afterwards we should working on uploading the cam
> Let's start fixing Camel-Extra state with tagging the releases so they
> can be in sync mainstream Camel. So... can I tag 2.10 release? (I got
> appropriate permissions)
Can I? :)
BTW Just to put some pressure on us - CAMEL-5397 [1].
[1] https://issues.apache.org/jira/browse/CAMEL-5397
--
He
> I am not sure if we can keep up with all the patch releases, as
> camel-extra ought to be compatible.
I think we should. It should be transparent for user (as transparent
as possible at least) whether she's using camel or camel-extra. This
is licensing stuff, users usually do not care if they in
Hi
Yeah it would be nice to get camel-extra released as a follow up to
any of the Camel minor releases, eg 2.9.0 2.10.0, 2.11.0.
I am not sure if we can keep up with all the patch releases, as
camel-extra ought to be compatible.
On Mon, Jun 25, 2012 at 12:42 PM, Henryk Konsek wrote:
>> I'm alr
> I'm already delayed with camel-extra 2.9.0 :-( See [1]
> I already tagged a release but didn't uploaded the artifacts and signatures
> until now. I plan to upload it to [2] where the 2.8.0 artifacts already are.
I want to contribute new component to Camel Extra (JGroups [1], which is LGPL).
If
I'm already delayed with camel-extra 2.9.0 :-( See [1]
I already tagged a release but didn't uploaded the artifacts and signatures
until now. I plan to upload it to [2] where the 2.8.0 artifacts already are.
We should release camel-extra right after camel 2.10.0 but after
camel-extra 2.9.0 (or tog
Hi,
When do you plan to release camel-extra 2.10? I want to contribute new
component to it (JGroups, which is LGPL) so I've just seen that
current version is still 2.10-SNAPSHOT.
I can make a release if you want me to (I got commiter rights to
camel-extra) but I won't be able to deploy artifacts
44 matches
Mail list logo
