You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Hadrian Zbarcea <hz...@gmail.com> on 2014/02/16 05:16:28 UTC
[VOTE] Release Apache Camel 2.12.3
This is a vote to release Apache Camel 2.12.3, a patch release coming
with about 128 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
Staging repo:
https://repository.apache.org/content/repositories/orgapachecamel-1002
Tarballs:
https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
Tag:
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
Please test this release candidate and cast your vote.
[ ] +1 Release the binary as Apache Camel 2.12.3
[ ] -1 Veto the release (provide specific comments)
Vote is open for at least 72 hours.
Thanks,
Hadrian
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Jon Anstey <ja...@gmail.com>.
+1
On Sun, Feb 16, 2014 at 12:46 AM, Hadrian Zbarcea <hz...@gmail.com>wrote:
> This is a vote to release Apache Camel 2.12.3, a patch release coming with
> about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311211&version=12325593
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1002
>
> Tarballs:
> https://repository.apache.org/content/repositories/
> orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
> 4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.12.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
>
--
Cheers,
Jon
---------------
Red Hat, Inc.
Email: janstey@redhat.com
Web: http://redhat.com
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Daniel Kulp <dk...@apache.org>.
+1
Dan
On Feb 15, 2014, at 11:16 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> This is a vote to release Apache Camel 2.12.3, a patch release coming with about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1002
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.12.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Mark Frazier <mm...@icloud.com>.
Did he mean that it doesn't FORCE 2.7.10?
> On Feb 17, 2014, at 4:55 AM, James Carman <ja...@carmanconsulting.com> wrote:
>
> How does the range from 2.6 (inclusive) to 2.9 (not inclusive) not
> include 2.7.10?
>
> On Mon, Feb 17, 2014 at 5:06 AM, Babak Vahdat
> <ba...@swissonline.ch> wrote:
>> Hi Willem,
>>
>> can you please elaborate your explanation a bit? Currently what we've on the
>> 2.12.x. as well as 2.11.x branches is this:
>>
>> <cxf-version>2.7.10</cxf-version>
>> <cxf-version-range>[2.6,2.9)</cxf-version-range>
>>
>> Now to my understanding this should become:
>>
>> <cxf-version>2.7.10</cxf-version>
>> <cxf-version-range>[2.6,3)</cxf-version-range>
>>
>> I think the current range is a problem for the OSGi folks because if e.g.
>> there's a bug-fix being provided in CXF 2.7.10, currently they can't force
>> the Container to make use of CXF 2.7.10 while they install the "camel-cxf"
>> feature version 2.12.3 or 2.11.4 (e.g. in the context of a dependency of
>> their own Karaf feature "my-cool-app-karaf-feature") because the current
>> range does NOT include 2.7.10.
>>
>> Babak
>>
>>
>> Willem.Jiang wrote
>>> There are some patches of supporting CXF 3.x are not merged to
>>> camel-2.12.x and camel-2.11.x.
>>> So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
>>>
>>> I don’t think it’s a show-stopper.
>>>
>>> --
>>> Willem Jiang
>>>
>>> Red Hat, Inc.
>>> Web: http://www.redhat.com
>>> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
>>> (English)
>>> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>>
>>>
>>>
>>> On February 16, 2014 at 11:35:56 PM, Babak Vahdat (
>>
>>> babak.vahdat@
>>
>>> ) wrote:
>>>>
>>>> O.K. the build has been definetly done using Java 6 as this's how
>>>> MANIFEST.MF
>>>> of camel-core-2.12.3.jar looks like:
>>>>
>>>> Manifest-Version: 1.0
>>>> Bnd-LastModified: 1392475192207
>>>> Build-Jdk: 1.6.0_45
>>>> Built-By: hadrian
>>>> ...
>>>>
>>>>
>>>> Other than that the backport of the fix for CAMEL-7170 did NOT
>>>> adjust the
>>>> maven property accordingly, so on the
>>>> master branch
>>>> we've got:
>>>>
>>>> 2.7.10
>>>> [2.6,4.0)
>>>>
>>>> Which is fine, however on the 2.12.x as well as the 2.11.x branch
>>>> we've got:
>>>>
>>>> 2.7.10
>>>> [2.6,2.9)
>>>>
>>>> So here's my -1
>>>>
>>>> Babak
>>>>
>>>>
>>>> Babak Vahdat wrote
>>>>> Hi
>>>>>
>>>>> The HTML component documentation inside the JARs are missing.
>>>> I assume
>>>>> Java 6 has been used for building this release candidate. See
>>>> also the
>>>>> first "Note" @ http://camel.apache.org/release-guide.html
>>>>>
>>>>> Babak
>>>>> hadrian wrote
>>>>>> This is a vote to release Apache Camel 2.12.3, a patch release
>>>> coming
>>>>>> with about 128 issues fixed.
>>>>>>
>>>>>> Release notes:
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>>>>>
>>>>>> Staging repo:
>>>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>>>>>
>>>>>> Tarballs:
>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>>>>>
>>>>>> Tag:
>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>>>>>
>>>>>> Please test this release candidate and cast your vote.
>>>>>> [ ] +1 Release the binary as Apache Camel 2.12.3
>>>>>> [ ] -1 Veto the release (provide specific comments)
>>>>>> Vote is open for at least 72 hours.
>>>>>>
>>>>>> Thanks,
>>>>>> Hadrian
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747421.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by James Carman <ja...@carmanconsulting.com>.
How does the range from 2.6 (inclusive) to 2.9 (not inclusive) not
include 2.7.10?
On Mon, Feb 17, 2014 at 5:06 AM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> Hi Willem,
>
> can you please elaborate your explanation a bit? Currently what we've on the
> 2.12.x. as well as 2.11.x branches is this:
>
> <cxf-version>2.7.10</cxf-version>
> <cxf-version-range>[2.6,2.9)</cxf-version-range>
>
> Now to my understanding this should become:
>
> <cxf-version>2.7.10</cxf-version>
> <cxf-version-range>[2.6,3)</cxf-version-range>
>
> I think the current range is a problem for the OSGi folks because if e.g.
> there's a bug-fix being provided in CXF 2.7.10, currently they can't force
> the Container to make use of CXF 2.7.10 while they install the "camel-cxf"
> feature version 2.12.3 or 2.11.4 (e.g. in the context of a dependency of
> their own Karaf feature "my-cool-app-karaf-feature") because the current
> range does NOT include 2.7.10.
>
> Babak
>
>
> Willem.Jiang wrote
>> There are some patches of supporting CXF 3.x are not merged to
>> camel-2.12.x and camel-2.11.x.
>> So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
>>
>> I don’t think it’s a show-stopper.
>>
>> --
>> Willem Jiang
>>
>> Red Hat, Inc.
>> Web: http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
>> (English)
>> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>> On February 16, 2014 at 11:35:56 PM, Babak Vahdat (
>
>> babak.vahdat@
>
>> ) wrote:
>>>
>>> O.K. the build has been definetly done using Java 6 as this's how
>>> MANIFEST.MF
>>> of camel-core-2.12.3.jar looks like:
>>>
>>> Manifest-Version: 1.0
>>> Bnd-LastModified: 1392475192207
>>> Build-Jdk: 1.6.0_45
>>> Built-By: hadrian
>>> ...
>>>
>>>
>>> Other than that the backport of the fix for CAMEL-7170 did NOT
>>> adjust the
>>> maven property accordingly, so on the
>>> master branch
>>> we've got:
>>>
>>> 2.7.10
>>> [2.6,4.0)
>>>
>>> Which is fine, however on the 2.12.x as well as the 2.11.x branch
>>> we've got:
>>>
>>> 2.7.10
>>> [2.6,2.9)
>>>
>>> So here's my -1
>>>
>>> Babak
>>>
>>>
>>> Babak Vahdat wrote
>>> > Hi
>>> >
>>> > The HTML component documentation inside the JARs are missing.
>>> I assume
>>> > Java 6 has been used for building this release candidate. See
>>> also the
>>> > first "Note" @ http://camel.apache.org/release-guide.html
>>> >
>>> > Babak
>>> > hadrian wrote
>>> >> This is a vote to release Apache Camel 2.12.3, a patch release
>>> coming
>>> >> with about 128 issues fixed.
>>> >>
>>> >> Release notes:
>>> >>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>> >>
>>> >> Staging repo:
>>> >> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>> >>
>>> >> Tarballs:
>>> >>
>>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>> >>
>>> >> Tag:
>>> >>
>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>> >>
>>> >> Please test this release candidate and cast your vote.
>>> >> [ ] +1 Release the binary as Apache Camel 2.12.3
>>> >> [ ] -1 Veto the release (provide specific comments)
>>> >> Vote is open for at least 72 hours.
>>> >>
>>> >> Thanks,
>>> >> Hadrian
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747421.html
> Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Babak Vahdat <ba...@swissonline.ch>.
See these two comments:
https://github.com/apache/camel/blob/master/camel-core/pom.xml#L417
https://github.com/apache/camel/blob/master/components/pom.xml#L229
AKAIK there've been problems with that for the folks using IntelliJ IDEA.
Using a Maven profile for this dependency gives them then the possibility to
disable it if necessary BUT per default we want it enabled while building
directly through Maven itself, so why
<activeByDefault>true</activeByDefault>.
Babak
dkulp@apache.org wrote
> On Feb 21, 2014, at 5:12 AM, Babak Vahdat <
> babak.vahdat@
> > wrote:
>
>> Thanks Willem, that's just awesome!
>>
>> To reflect your fix I enabled the 'apt' profile by our POMs *per default*
>> and also activated the corresponding tests on Java 6 as well.
>
> If things are working with both 6 and 7, is there any reason for the apt
> profile at all? Can we just remove it?
>
> Dan
>
>
>>
>> The commit has been also backported to the 2.12.x branch.
>>
>> Looking forward for the upcomming 2.12.3 release!
>>
>> Babak
>>
>>
>> Willem.Jiang wrote
>>> I already fixed the issue, and ran the prepare release process with
>>> JDK6.
>>> The html document can be generated without any trouble.
>>>
>>> Please hold you commit to camel-2.12.x until you see the new tag is
>>> created.
>>>
>>> --
>>> Willem Jiang
>>>
>>> Red Hat, Inc.
>>> Web: http://www.redhat.com
>>> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
>>> (English)
>>> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>>
>>>
>>>
>>> On February 21, 2014 at 2:36:51 AM, Hadrian Zbarcea (
>>
>>> hzbarcea@
>>
>>> ) wrote:
>>>>
>>>> Willem, if that problem was so important to you to block a release
>>>> then
>>>> it needs to be fixed. Until it's fixed I will -1 a release. It either
>>>> is
>>>> important or it isn't.
>>>>
>>>> Hadrian
>>>>
>>>> On 02/20/2014 12:26 PM, Willem Jiang wrote:
>>>>> Hi Dan,
>>>>>
>>>>> Thanks for the inputs.
>>>>>
>>>>> The annotation is already RetentionPolicy.RUNTIME.
>>>>>
>>>>> Current the html generator is based the APT processor, But it
>>>> looks like
>>>>> JDK6 has some trouble to load the APT processor when compile
>>>> the code, I’m
>>>>> not sure if I can fix it tomorrow.
>>>>>
>>>>> At mean while, I suggest we can spend some time to address this
>>>> JDK compile
>>>>> issue after Camel 2.12.3 is released, so it won’t block the ActiveMQ
>>>>> release.
>>>>>
>>>>
>>>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747739.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>
> --
> Daniel Kulp
> dkulp@
> - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747778.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Daniel Kulp <dk...@apache.org>.
On Feb 21, 2014, at 5:12 AM, Babak Vahdat <ba...@swissonline.ch> wrote:
> Thanks Willem, that's just awesome!
>
> To reflect your fix I enabled the 'apt' profile by our POMs *per default*
> and also activated the corresponding tests on Java 6 as well.
If things are working with both 6 and 7, is there any reason for the apt profile at all? Can we just remove it?
Dan
>
> The commit has been also backported to the 2.12.x branch.
>
> Looking forward for the upcomming 2.12.3 release!
>
> Babak
>
>
> Willem.Jiang wrote
>> I already fixed the issue, and ran the prepare release process with JDK6.
>> The html document can be generated without any trouble.
>>
>> Please hold you commit to camel-2.12.x until you see the new tag is
>> created.
>>
>> --
>> Willem Jiang
>>
>> Red Hat, Inc.
>> Web: http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
>> (English)
>> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>> On February 21, 2014 at 2:36:51 AM, Hadrian Zbarcea (
>
>> hzbarcea@
>
>> ) wrote:
>>>
>>> Willem, if that problem was so important to you to block a release
>>> then
>>> it needs to be fixed. Until it's fixed I will -1 a release. It either
>>> is
>>> important or it isn't.
>>>
>>> Hadrian
>>>
>>> On 02/20/2014 12:26 PM, Willem Jiang wrote:
>>>> Hi Dan,
>>>>
>>>> Thanks for the inputs.
>>>>
>>>> The annotation is already RetentionPolicy.RUNTIME.
>>>>
>>>> Current the html generator is based the APT processor, But it
>>> looks like
>>>> JDK6 has some trouble to load the APT processor when compile
>>> the code, I’m
>>>> not sure if I can fix it tomorrow.
>>>>
>>>> At mean while, I suggest we can spend some time to address this
>>> JDK compile
>>>> issue after Camel 2.12.3 is released, so it won’t block the ActiveMQ
>>>> release.
>>>>
>>>
>>>
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747739.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: AW: [VOTE] Release Apache Camel 2.12.3
Posted by Willem Jiang <wi...@gmail.com>.
Thanks for point that out.
I will fix it in my next commit, but it just missed the release train of camel-2.12.3.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 21, 2014 at 7:00:15 PM, Jan Matèrne (jhm) (apache@materne.de) wrote:
>
> Maybe a small fix to the EndpointProcessor:
> Line 104 should also print the title to the HTML
>
> protected void writeHtmlDocumentation(PrintWriter writer,
> RoundEnvironment roundEnv, TypeElement classElement, UriEndpoint
> uriEndpoint) {
> writer.println("");
> writer.println("
");
> String scheme = uriEndpoint.scheme();
> String title = scheme + " endpoint";
> writer.println(""); <=== should include
> the title!
>
> Jan
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Babak Vahdat [mailto:babak.vahdat@swissonline.ch]
> > Gesendet: Freitag, 21. Februar 2014 11:12
> > An: dev@camel.apache.org
> > Betreff: Re: [VOTE] Release Apache Camel 2.12.3
> >
> > Thanks Willem, that's just awesome!
> >
> > To reflect your fix I enabled the 'apt' profile by our POMs *per
> > default* and also activated the corresponding tests on Java
> 6 as well.
> >
> > The commit has been also backported to the 2.12.x branch.
> >
> > Looking forward for the upcomming 2.12.3 release!
> >
> > Babak
> >
> >
> > Willem.Jiang wrote
> > > I already fixed the issue, and ran the prepare release process
> with
> > JDK6.
> > > The html document can be generated without any trouble.
> > >
> > > Please hold you commit to camel-2.12.x until you see the new
> tag is
> > > created.
> > >
> > > --
> > > Willem Jiang
> > >
> > > Red Hat, Inc.
> > > Web: http://www.redhat.com
> > > Blog:
> > > http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
> > > (English)
> > > http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > >
> > >
> > > On February 21, 2014 at 2:36:51 AM, Hadrian Zbarcea (
> >
> > > hzbarcea@
> >
> > > ) wrote:
> > >>
> > >> Willem, if that problem was so important to you to block a release
> > >> then it needs to be fixed. Until it's fixed I will -1 a release.
> It
> > >> either is important or it isn't.
> > >>
> > >> Hadrian
> > >>
> > >> On 02/20/2014 12:26 PM, Willem Jiang wrote:
> > >> > Hi Dan,
> > >> >
> > >> > Thanks for the inputs.
> > >> >
> > >> > The annotation is already RetentionPolicy.RUNTIME.
> > >> >
> > >> > Current the html generator is based the APT processor, But
> it
> > >> looks like
> > >> > JDK6 has some trouble to load the APT processor when compile
> > >> the code, I’m
> > >> > not sure if I can fix it tomorrow.
> > >> >
> > >> > At mean while, I suggest we can spend some time to address
> this
> > >> JDK compile
> > >> > issue after Camel 2.12.3 is released, so it won’t block the
> > >> > ActiveMQ release.
> > >> >
> > >>
> > >>
> >
> >
> >
> >
> >
> > --
> > View this message in context: http://camel.465427.n5.nabble.com/VOTE-
> > Release-Apache-Camel-2-12-3-tp5747361p5747739.html
> > Sent from the Camel Development mailing list archive at Nabble.com.
>
>
AW: [VOTE] Release Apache Camel 2.12.3
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
Maybe a small fix to the EndpointProcessor:
Line 104 should also print the title to the HTML
protected void writeHtmlDocumentation(PrintWriter writer, RoundEnvironment roundEnv, TypeElement classElement, UriEndpoint uriEndpoint) {
writer.println("<html>");
writer.println("<header>");
String scheme = uriEndpoint.scheme();
String title = scheme + " endpoint";
writer.println("<title>" + "</title>"); <=== should include the title!
Jan
> -----Ursprüngliche Nachricht-----
> Von: Babak Vahdat [mailto:babak.vahdat@swissonline.ch]
> Gesendet: Freitag, 21. Februar 2014 11:12
> An: dev@camel.apache.org
> Betreff: Re: [VOTE] Release Apache Camel 2.12.3
>
> Thanks Willem, that's just awesome!
>
> To reflect your fix I enabled the 'apt' profile by our POMs *per
> default* and also activated the corresponding tests on Java 6 as well.
>
> The commit has been also backported to the 2.12.x branch.
>
> Looking forward for the upcomming 2.12.3 release!
>
> Babak
>
>
> Willem.Jiang wrote
> > I already fixed the issue, and ran the prepare release process with
> JDK6.
> > The html document can be generated without any trouble.
> >
> > Please hold you commit to camel-2.12.x until you see the new tag is
> > created.
> >
> > --
> > Willem Jiang
> >
> > Red Hat, Inc.
> > Web: http://www.redhat.com
> > Blog:
> > http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
> > (English)
> > http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> >
> >
> > On February 21, 2014 at 2:36:51 AM, Hadrian Zbarcea (
>
> > hzbarcea@
>
> > ) wrote:
> >>
> >> Willem, if that problem was so important to you to block a release
> >> then it needs to be fixed. Until it's fixed I will -1 a release. It
> >> either is important or it isn't.
> >>
> >> Hadrian
> >>
> >> On 02/20/2014 12:26 PM, Willem Jiang wrote:
> >> > Hi Dan,
> >> >
> >> > Thanks for the inputs.
> >> >
> >> > The annotation is already RetentionPolicy.RUNTIME.
> >> >
> >> > Current the html generator is based the APT processor, But it
> >> looks like
> >> > JDK6 has some trouble to load the APT processor when compile
> >> the code, I’m
> >> > not sure if I can fix it tomorrow.
> >> >
> >> > At mean while, I suggest we can spend some time to address this
> >> JDK compile
> >> > issue after Camel 2.12.3 is released, so it won’t block the
> >> > ActiveMQ release.
> >> >
> >>
> >>
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-
> Release-Apache-Camel-2-12-3-tp5747361p5747739.html
> Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Babak Vahdat <ba...@swissonline.ch>.
Thanks Willem, that's just awesome!
To reflect your fix I enabled the 'apt' profile by our POMs *per default*
and also activated the corresponding tests on Java 6 as well.
The commit has been also backported to the 2.12.x branch.
Looking forward for the upcomming 2.12.3 release!
Babak
Willem.Jiang wrote
> I already fixed the issue, and ran the prepare release process with JDK6.
> The html document can be generated without any trouble.
>
> Please hold you commit to camel-2.12.x until you see the new tag is
> created.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
> (English)
> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On February 21, 2014 at 2:36:51 AM, Hadrian Zbarcea (
> hzbarcea@
> ) wrote:
>>
>> Willem, if that problem was so important to you to block a release
>> then
>> it needs to be fixed. Until it's fixed I will -1 a release. It either
>> is
>> important or it isn't.
>>
>> Hadrian
>>
>> On 02/20/2014 12:26 PM, Willem Jiang wrote:
>> > Hi Dan,
>> >
>> > Thanks for the inputs.
>> >
>> > The annotation is already RetentionPolicy.RUNTIME.
>> >
>> > Current the html generator is based the APT processor, But it
>> looks like
>> > JDK6 has some trouble to load the APT processor when compile
>> the code, I’m
>> > not sure if I can fix it tomorrow.
>> >
>> > At mean while, I suggest we can spend some time to address this
>> JDK compile
>> > issue after Camel 2.12.3 is released, so it won’t block the ActiveMQ
>> > release.
>> >
>>
>>
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747739.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Christian Müller <ch...@gmail.com>.
+1 to drop Java 6 support with Camel 2.14.x
+1 to start looking into Java 8 support with Camel 2.14.x.
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 Sat, Feb 22, 2014 at 9:57 AM, Claus Ibsen <cl...@gmail.com> wrote:
> On Thu, Feb 20, 2014 at 7:45 AM, Jan Matèrne (jhm) <ap...@materne.de>
> wrote:
> >> sorry to interfere, but shouldn't the vote be on the src package only
> >> ("releases be primarily based on a signed source package"), therefore
> >> the "binary" is just a nice topping on top and this is just a pure
> >> makeup failure.
> >>
> >> please correct me if I'm wrong :)
> >> The quote was taken from the release.html that Hadrian just posted
> >> before.
> >
> >
> > If I read the ASF release guidelines [1] correctly, all things a project
> ships out is a release.
> > So because Camel ships a bin-distro, that's also a release.
> >
> > [1] http://www.apache.org/dev/release.html#what
> >
> >
> >
> >> I'll give it another 12 hours and if nothing changes I will close
> >> the vote and release 2.12.3. If within this time you convince another
> >> PMC member to change his vote I will cancel this vote.
> >
> > I am also a fan a building against the oldest supported platform.
> > Would it be possible to
> > - build Camel against Java6 for getting the "right" class file format
> > - generate the html using Java7
> > - jar them using Java6?
> >
> > Another option would drop Java6 ... But as Oracle writes [2] for Java6:
> > - Feb 2011: End of Public Updates Notification
> > - Feb 2013: End of Public Updates
> > - Dec 2013: Premier Support Until
> > BUT
> > - Jun 2017: Extended Support Until
> >
> >
> > [2] http://www.oracle.com/technetwork/java/eol-135779.html
> >
>
> Java 6 has been EOL for 1 year now, since end of February 2013 [2]
> You can buy enterprise support from Oracle if you want a paid support
> for Java6 for a longer time.
> But the community releases is EOL.
>
>
>
> So its IMHO about time we also start consider dropping Java6 for newer
> Camel releases.
> Maybe for the Camel release after 2.13.x, meaning 2.13.x branch is the
> last Java6 supported branch of ours.
>
> Also Java8 is around the corner, so we would need to move on in Camel
> so we can start to take advantage of Java8 stuff in future Camel
> releases.
>
>
>
> ===============
>
> Java SE 6 End of Public Updates Notice
>
> After February 2013, Oracle will no longer post updates of Java SE 6
> to its public download sites. Existing Java SE 6 downloads already
> posted as of February 2013 will remain accessible in theJava Archive
> on Oracle Technology Network. Developers and end-users are encouraged
> to update to more recent Java SE versions that remain available for
> public download. For enterprise customers, who need continued access
> to critical bug fixes and security fixes as well as general
> maintenance for Java SE 6 or older versions, long term support is
> available through Oracle Java SE Support .
>
>
> ===============
>
>
> > Jan
> >
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> Make your Camel applications look hawt, try: http://hawt.io
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Feb 20, 2014 at 7:45 AM, Jan Matèrne (jhm) <ap...@materne.de> wrote:
>> sorry to interfere, but shouldn't the vote be on the src package only
>> ("releases be primarily based on a signed source package"), therefore
>> the "binary" is just a nice topping on top and this is just a pure
>> makeup failure.
>>
>> please correct me if I'm wrong :)
>> The quote was taken from the release.html that Hadrian just posted
>> before.
>
>
> If I read the ASF release guidelines [1] correctly, all things a project ships out is a release.
> So because Camel ships a bin-distro, that's also a release.
>
> [1] http://www.apache.org/dev/release.html#what
>
>
>
>> I'll give it another 12 hours and if nothing changes I will close
>> the vote and release 2.12.3. If within this time you convince another
>> PMC member to change his vote I will cancel this vote.
>
> I am also a fan a building against the oldest supported platform.
> Would it be possible to
> - build Camel against Java6 for getting the "right" class file format
> - generate the html using Java7
> - jar them using Java6?
>
> Another option would drop Java6 ... But as Oracle writes [2] for Java6:
> - Feb 2011: End of Public Updates Notification
> - Feb 2013: End of Public Updates
> - Dec 2013: Premier Support Until
> BUT
> - Jun 2017: Extended Support Until
>
>
> [2] http://www.oracle.com/technetwork/java/eol-135779.html
>
Java 6 has been EOL for 1 year now, since end of February 2013 [2]
You can buy enterprise support from Oracle if you want a paid support
for Java6 for a longer time.
But the community releases is EOL.
So its IMHO about time we also start consider dropping Java6 for newer
Camel releases.
Maybe for the Camel release after 2.13.x, meaning 2.13.x branch is the
last Java6 supported branch of ours.
Also Java8 is around the corner, so we would need to move on in Camel
so we can start to take advantage of Java8 stuff in future Camel
releases.
===============
Java SE 6 End of Public Updates Notice
After February 2013, Oracle will no longer post updates of Java SE 6
to its public download sites. Existing Java SE 6 downloads already
posted as of February 2013 will remain accessible in theJava Archive
on Oracle Technology Network. Developers and end-users are encouraged
to update to more recent Java SE versions that remain available for
public download. For enterprise customers, who need continued access
to critical bug fixes and security fixes as well as general
maintenance for Java SE 6 or older versions, long term support is
available through Oracle Java SE Support .
===============
> Jan
>
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Willem Jiang <wi...@gmail.com>.
I already fixed the issue, and ran the prepare release process with JDK6.
The html document can be generated without any trouble.
Please hold you commit to camel-2.12.x until you see the new tag is created.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 21, 2014 at 2:36:51 AM, Hadrian Zbarcea (hzbarcea@gmail.com) wrote:
>
> Willem, if that problem was so important to you to block a release
> then
> it needs to be fixed. Until it's fixed I will -1 a release. It either
> is
> important or it isn't.
>
> Hadrian
>
> On 02/20/2014 12:26 PM, Willem Jiang wrote:
> > Hi Dan,
> >
> > Thanks for the inputs.
> >
> > The annotation is already RetentionPolicy.RUNTIME.
> >
> > Current the html generator is based the APT processor, But it
> looks like
> > JDK6 has some trouble to load the APT processor when compile
> the code, I’m
> > not sure if I can fix it tomorrow.
> >
> > At mean while, I suggest we can spend some time to address this
> JDK compile
> > issue after Camel 2.12.3 is released, so it won’t block the ActiveMQ
> > release.
> >
>
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Willem, if that problem was so important to you to block a release then
it needs to be fixed. Until it's fixed I will -1 a release. It either is
important or it isn't.
Hadrian
On 02/20/2014 12:26 PM, Willem Jiang wrote:
> Hi Dan,
>
> Thanks for the inputs.
>
> The annotation is already RetentionPolicy.RUNTIME.
>
> Current the html generator is based the APT processor, But it looks like
> JDK6 has some trouble to load the APT processor when compile the code, I’m
> not sure if I can fix it tomorrow.
>
> At mean while, I suggest we can spend some time to address this JDK compile
> issue after Camel 2.12.3 is released, so it won’t block the ActiveMQ
> release.
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Willem Jiang <wi...@gmail.com>.
Hi Dan,
Thanks for the inputs.
The annotation is already RetentionPolicy.RUNTIME.
Current the html generator is based the APT processor, But it looks like
JDK6 has some trouble to load the APT processor when compile the code, I’m
not sure if I can fix it tomorrow.
At mean while, I suggest we can spend some time to address this JDK compile
issue after Camel 2.12.3 is released, so it won’t block the ActiveMQ
release.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 20, 2014 at 10:29:47 PM, Daniel Kulp (dkulp@apache.org) wrote:
>
>
> On Feb 20, 2014, at 1:45 AM, Jan Matèrne (jhm)
> wrote:
> >> I'll give it another 12 hours and if nothing changes I will close
> >> the vote and release 2.12.3. If within this time you convince
> another
> >> PMC member to change his vote I will cancel this vote.
> >
> > I am also a fan a building against the oldest supported platform.
> > Would it be possible to
> > - build Camel against Java6 for getting the "right" class file
> format
> > - generate the html using Java7
> > - jar them using Java6?
>
> We could easily make the annotations be RetentionPolicy.RUNTIME
> so they are kept in the compiled classes. At that point, we have
> two options that could work with java6:
>
> 1) Write a utility class that would take a Class object and generate
> the appropriate HTML. Tools could easily use this. This could
> be designed with protected methods or something so that they
> could override parts of it to customize what is generated as they
> need.
>
> 2) Create a maven plugin that runs in process-classes to generate
> static HTML. It could possibly even use the utility from (1).
>
> Again, both would work fine with java 6.
>
> In any case, I also strongly believe that anything that is NOT
> built as part of using our lowest supported JDK is “optional”.
> If it is or is not part of the convenience artifacts is irrelevant
> from a release standpoint. If people want that functionality,
> find a way to make it not optional.
>
>
> Dan
>
>
>
> > Another option would drop Java6 ... But as Oracle writes [2]
> for Java6:
> > - Feb 2011: End of Public Updates Notification
> > - Feb 2013: End of Public Updates
> > - Dec 2013: Premier Support Until
> > BUT
> > - Jun 2017: Extended Support Until
> >
> >
> > [2] http://www.oracle.com/technetwork/java/eol-135779.html
> >
> > Jan
> >
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Daniel Kulp <dk...@apache.org>.
On Feb 20, 2014, at 1:45 AM, Jan Matèrne (jhm) <ap...@materne.de> wrote:
>> I'll give it another 12 hours and if nothing changes I will close
>> the vote and release 2.12.3. If within this time you convince another
>> PMC member to change his vote I will cancel this vote.
>
> I am also a fan a building against the oldest supported platform.
> Would it be possible to
> - build Camel against Java6 for getting the "right" class file format
> - generate the html using Java7
> - jar them using Java6?
We could easily make the annotations be RetentionPolicy.RUNTIME so they are kept in the compiled classes. At that point, we have two options that could work with java6:
1) Write a utility class that would take a Class object and generate the appropriate HTML. Tools could easily use this. This could be designed with protected methods or something so that they could override parts of it to customize what is generated as they need.
2) Create a maven plugin that runs in process-classes to generate static HTML. It could possibly even use the utility from (1).
Again, both would work fine with java 6.
In any case, I also strongly believe that anything that is NOT built as part of using our lowest supported JDK is “optional”. If it is or is not part of the convenience artifacts is irrelevant from a release standpoint. If people want that functionality, find a way to make it not optional.
Dan
> Another option would drop Java6 ... But as Oracle writes [2] for Java6:
> - Feb 2011: End of Public Updates Notification
> - Feb 2013: End of Public Updates
> - Dec 2013: Premier Support Until
> BUT
> - Jun 2017: Extended Support Until
>
>
> [2] http://www.oracle.com/technetwork/java/eol-135779.html
>
> Jan
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
AW: [VOTE] Release Apache Camel 2.12.3
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
> sorry to interfere, but shouldn't the vote be on the src package only
> ("releases be primarily based on a signed source package"), therefore
> the "binary" is just a nice topping on top and this is just a pure
> makeup failure.
>
> please correct me if I'm wrong :)
> The quote was taken from the release.html that Hadrian just posted
> before.
If I read the ASF release guidelines [1] correctly, all things a project ships out is a release.
So because Camel ships a bin-distro, that's also a release.
[1] http://www.apache.org/dev/release.html#what
> I'll give it another 12 hours and if nothing changes I will close
> the vote and release 2.12.3. If within this time you convince another
> PMC member to change his vote I will cancel this vote.
I am also a fan a building against the oldest supported platform.
Would it be possible to
- build Camel against Java6 for getting the "right" class file format
- generate the html using Java7
- jar them using Java6?
Another option would drop Java6 ... But as Oracle writes [2] for Java6:
- Feb 2011: End of Public Updates Notification
- Feb 2013: End of Public Updates
- Dec 2013: Premier Support Until
BUT
- Jun 2017: Extended Support Until
[2] http://www.oracle.com/technetwork/java/eol-135779.html
Jan
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Achim Nierbeck <bc...@googlemail.com>.
sorry to interfere, but shouldn't the vote be on the src package only
("releases be primarily based on a signed source package"), therefore the
"binary" is just a nice topping on top
and this is just a pure makeup failure.
please correct me if I'm wrong :)
The quote was taken from the release.html that Hadrian just posted before.
regards, Achim
2014-02-19 16:38 GMT+01:00 Hadrian Zbarcea <hz...@gmail.com>:
> Babak, per the ASF policy we can release 2.12.3 even with -1s.
> However, I usually shoot for consensus. Here's what I am going to do in
> this case, because yours is the only -1 with an overwhelming majority of
> +1s. I'll give it another 12 hours and if nothing changes I will close the
> vote and release 2.12.3. If within this time you convince another PMC
> member to change his vote I will cancel this vote.
>
> We had two releases in the past, years ago (1.4 and 1.5 time) that were
> built with a newer version that the oldest supported and we got burned by
> the version of the class file format. (I was the one who messed up, had to
> redo the releases and learned my lesson). I personally don't release with a
> newer java version than the oldest supported.
>
> Cheers,
> Hadrian
>
> [1] http://www.apache.org/dev/release.html
>
>
>
> On 02/19/2014 10:19 AM, Babak Vahdat wrote:
>
>> Hi Harian,
>>
>> I'm actually still -1 to this release candidate as the HTML documentation
>> inside the bundles are missing (as a side effect of Java 6 being used for
>> building instead of Java 7). This requirement has been clearly stated
>> inside
>> our release guides (yes, I was the one who added that note):
>>
>> http://camel.apache.org/release-guide.html
>>
>> And we've also discussed this many times @ the dev-forum as well:
>>
>> http://camel.465427.n5.nabble.com/improving-Endpoint-
>> documentation-and-tooling-td5731334.html
>> http://camel.465427.n5.nabble.com/Our-builds-looks-really-
>> bad-tp5731673p5731743.html
>>
>> That all said, I may sound too pedantic, sorry for that!
>>
>> Last but not least I ask for apologies by the Apache Camel PMC because of
>> the STUPID mistake I made while voting for the 2.11.4 release candidate:
>>
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-
>> 2-11-4-tp5747362p5747430.html
>>
>> As I had A LOT OF BEERS the night before that vote of mine. So I guess
>> that
>> was why my brain went terribly wrong :)
>>
>> Many thanks for your effort to prepare these two release candidates!
>>
>> Babak
>>
>>
>> hadrian wrote
>>
>>> Babak,
>>>
>>> We're past the 72 hours mark and I would like to close this vote with a
>>> consensus is possible. Do you still think we have an issue, or you want
>>> to consider reverting your vote?
>>>
>>> Cheers,
>>> Hadrian
>>>
>>>
>>> On 02/17/2014 05:06 AM, Babak Vahdat wrote:
>>>
>>>> Hi Willem,
>>>>
>>>> can you please elaborate your explanation a bit? Currently what we've on
>>>> the
>>>> 2.12.x. as well as 2.11.x branches is this:
>>>>
>>>>
>>>>
>>> <cxf-version>
>>> 2.7.10
>>> </cxf-version>
>>>
>>>>
>>>>
>>> <cxf-version-range>
>>> [2.6,2.9)
>>> </cxf-version-range>
>>>
>>>> Now to my understanding this should become:
>>>>
>>>>
>>>>
>>> <cxf-version>
>>> 2.7.10
>>> </cxf-version>
>>>
>>>>
>>>>
>>> <cxf-version-range>
>>> [2.6,3)
>>> </cxf-version-range>
>>>
>>>> I think the current range is a problem for the OSGi folks because if
>>>> e.g.
>>>> there's a bug-fix being provided in CXF 2.7.10, currently they can't
>>>> force
>>>> the Container to make use of CXF 2.7.10 while they install the
>>>> "camel-cxf"
>>>> feature version 2.12.3 or 2.11.4 (e.g. in the context of a dependency of
>>>> their own Karaf feature "my-cool-app-karaf-feature") because the current
>>>> range does NOT include 2.7.10.
>>>>
>>>> Babak
>>>>
>>>>
>>>> Willem.Jiang wrote
>>>>
>>>>> There are some patches of supporting CXF 3.x are not merged to
>>>>> camel-2.12.x and camel-2.11.x.
>>>>> So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
>>>>>
>>>>> I don’t think it’s a show-stopper.
>>>>>
>>>>> --
>>>>> Willem Jiang
>>>>>
>>>>> Red Hat, Inc.
>>>>> Web: http://www.redhat.com
>>>>> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/
>>>>> )
>>>>> (English)
>>>>> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
>>>>> Twitter: willemjiang
>>>>> Weibo: 姜宁willem
>>>>>
>>>>>
>>>>>
>>>>> On February 16, 2014 at 11:35:56 PM, Babak Vahdat (
>>>>> babak.vahdat@
>>>>> ) wrote:
>>>>>
>>>>>> O.K. the build has been definetly done using Java 6 as this's how
>>>>>> MANIFEST.MF
>>>>>> of camel-core-2.12.3.jar looks like:
>>>>>> Manifest-Version: 1.0
>>>>>> Bnd-LastModified: 1392475192207
>>>>>> Build-Jdk: 1.6.0_45
>>>>>> Built-By: hadrian
>>>>>> ...
>>>>>> Other than that the backport of the fix for CAMEL-7170 did NOT
>>>>>> adjust the
>>>>>> maven property accordingly, so on the
>>>>>> master branch
>>>>>> we've got:
>>>>>> 2.7.10
>>>>>> [2.6,4.0)
>>>>>> Which is fine, however on the 2.12.x as well as the 2.11.x branch
>>>>>> we've got:
>>>>>> 2.7.10
>>>>>> [2.6,2.9)
>>>>>> So here's my -1
>>>>>> Babak
>>>>>> Babak Vahdat wrote
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> The HTML component documentation inside the JARs are missing.
>>>>>>>
>>>>>> I assume
>>>>>>
>>>>>>> Java 6 has been used for building this release candidate. See
>>>>>>>
>>>>>> also the
>>>>>>
>>>>>>> first "Note" @ http://camel.apache.org/release-guide.html
>>>>>>>
>>>>>>> Babak
>>>>>>> hadrian wrote
>>>>>>>
>>>>>>>> This is a vote to release Apache Camel 2.12.3, a patch release
>>>>>>>>
>>>>>>> coming
>>>>>>
>>>>>>> with about 128 issues fixed.
>>>>>>>>
>>>>>>>> Release notes:
>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>>>>> projectId=12311211&version=12325593
>>>>>>
>>>>>>> Staging repo:
>>>>>>>> https://repository.apache.org/content/repositories/
>>>>>>>> orgapachecamel-1002
>>>>>>>>
>>>>>>>> Tarballs:
>>>>>>>>
>>>>>>>> https://repository.apache.org/content/repositories/
>>>>>> orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>>>>>
>>>>>>> Tag:
>>>>>>>>
>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
>>>>>> 4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>>>>>
>>>>>>> Please test this release candidate and cast your vote.
>>>>>>>> [ ] +1 Release the binary as Apache Camel 2.12.3
>>>>>>>> [ ] -1 Veto the release (provide specific comments)
>>>>>>>> Vote is open for at least 72 hours.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Hadrian
>>>>>>>>
>>>>>>> --
>>>>>> View this message in context:
>>>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-
>>>>>> 2-12-3-tp5747361p5747375.html
>>>>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-
>>>> 2-12-3-tp5747361p5747421.html
>>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>>
>>>
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.
>> com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747563.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
>
>
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
Commiter & Project Lead
blog <http://notizblog.nierbeck.de/>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Willem Jiang <wi...@gmail.com>.
Hi Hadrian,
I released the Camel 2.12.0 with JDK 1.7, as the compile plugin is set the source and target with 1.6, I don’t get any complain about it.
As I had said the HTML documentation issue could cause some trouble when some tools to load camel bundles, I changed my vote to -1. We need to recut the kit with JDK 1.7.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 19, 2014 at 11:39:13 PM, Hadrian Zbarcea (hzbarcea@gmail.com) wrote:
>
> Babak, per the ASF policy we can release 2.12.3 even with -1s.
> However, I usually shoot for consensus. Here's what I am going
> to do in
> this case, because yours is the only -1 with an overwhelming majority
> of
> +1s. I'll give it another 12 hours and if nothing changes I will
> close
> the vote and release 2.12.3. If within this time you convince
> another
> PMC member to change his vote I will cancel this vote.
>
> We had two releases in the past, years ago (1.4 and 1.5 time) that
> were
> built with a newer version that the oldest supported and we got
> burned
> by the version of the class file format. (I was the one who messed
> up,
> had to redo the releases and learned my lesson). I personally
> don't
> release with a newer java version than the oldest supported.
>
> Cheers,
> Hadrian
>
> [1] http://www.apache.org/dev/release.html
>
>
> On 02/19/2014 10:19 AM, Babak Vahdat wrote:
> > Hi Harian,
> >
> > I'm actually still -1 to this release candidate as the HTML documentation
> > inside the bundles are missing (as a side effect of Java 6 being
> used for
> > building instead of Java 7). This requirement has been clearly
> stated inside
> > our release guides (yes, I was the one who added that note):
> >
> > http://camel.apache.org/release-guide.html
> >
> > And we've also discussed this many times @ the dev-forum as well:
> >
> > http://camel.465427.n5.nabble.com/improving-Endpoint-documentation-and-tooling-td5731334.html
> > http://camel.465427.n5.nabble.com/Our-builds-looks-really-bad-tp5731673p5731743.html
> >
> > That all said, I may sound too pedantic, sorry for that!
> >
> > Last but not least I ask for apologies by the Apache Camel PMC
> because of
> > the STUPID mistake I made while voting for the 2.11.4 release
> candidate:
> >
> > http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747430.html
> >
> > As I had A LOT OF BEERS the night before that vote of mine. So I guess
> that
> > was why my brain went terribly wrong :)
> >
> > Many thanks for your effort to prepare these two release candidates!
> >
> > Babak
> >
> >
> > hadrian wrote
> >> Babak,
> >>
> >> We're past the 72 hours mark and I would like to close this vote
> with a
> >> consensus is possible. Do you still think we have an issue,
> or you want
> >> to consider reverting your vote?
> >>
> >> Cheers,
> >> Hadrian
> >>
> >>
> >> On 02/17/2014 05:06 AM, Babak Vahdat wrote:
> >>> Hi Willem,
> >>>
> >>> can you please elaborate your explanation a bit? Currently
> what we've on
> >>> the
> >>> 2.12.x. as well as 2.11.x branches is this:
> >>>
> >>>
> >>
> >> 2.7.10
> >>
> >>>
> >>
> >> [2.6,2.9)
> >>
> >>> Now to my understanding this should become:
> >>>
> >>>
> >>
> >> 2.7.10
> >>
> >>>
> >>
> >> [2.6,3)
> >>
> >>> I think the current range is a problem for the OSGi folks because
> if e.g.
> >>> there's a bug-fix being provided in CXF 2.7.10, currently
> they can't
> >>> force
> >>> the Container to make use of CXF 2.7.10 while they install
> the
> >>> "camel-cxf"
> >>> feature version 2.12.3 or 2.11.4 (e.g. in the context of a
> dependency of
> >>> their own Karaf feature "my-cool-app-karaf-feature")
> because the current
> >>> range does NOT include 2.7.10.
> >>>
> >>> Babak
> >>>
> >>>
> >>> Willem.Jiang wrote
> >>>> There are some patches of supporting CXF 3.x are not merged
> to
> >>>> camel-2.12.x and camel-2.11.x.
> >>>> So the cxf version rang of camel-2.12.x and camel-2.11.x
> is right.
> >>>>
> >>>> I don’t think it’s a show-stopper.
> >>>>
> >>>> --
> >>>> Willem Jiang
> >>>>
> >>>> Red Hat, Inc.
> >>>> Web: http://www.redhat.com
> >>>> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
> >>>> (English)
> >>>> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> >>>> Twitter: willemjiang
> >>>> Weibo: 姜宁willem
> >>>>
> >>>>
> >>>>
> >>>> On February 16, 2014 at 11:35:56 PM, Babak Vahdat (
> >>>> babak.vahdat@
> >>>> ) wrote:
> >>>>>
> >>>>> O.K. the build has been definetly done using Java 6 as this's
> how
> >>>>> MANIFEST.MF
> >>>>> of camel-core-2.12.3.jar looks like:
> >>>>>
> >>>>> Manifest-Version: 1.0
> >>>>> Bnd-LastModified: 1392475192207
> >>>>> Build-Jdk: 1.6.0_45
> >>>>> Built-By: hadrian
> >>>>> ...
> >>>>>
> >>>>>
> >>>>> Other than that the backport of the fix for CAMEL-7170 did
> NOT
> >>>>> adjust the
> >>>>> maven property accordingly, so on the
> >>>>> master branch
> >>>>> we've got:
> >>>>>
> >>>>> 2.7.10
> >>>>> [2.6,4.0)
> >>>>>
> >>>>> Which is fine, however on the 2.12.x as well as the 2.11.x
> branch
> >>>>> we've got:
> >>>>>
> >>>>> 2.7.10
> >>>>> [2.6,2.9)
> >>>>>
> >>>>> So here's my -1
> >>>>>
> >>>>> Babak
> >>>>>
> >>>>>
> >>>>> Babak Vahdat wrote
> >>>>>> Hi
> >>>>>>
> >>>>>> The HTML component documentation inside the JARs are
> missing.
> >>>>> I assume
> >>>>>> Java 6 has been used for building this release candidate.
> See
> >>>>> also the
> >>>>>> first "Note" @ http://camel.apache.org/release-guide.html
> >>>>>>
> >>>>>> Babak
> >>>>>> hadrian wrote
> >>>>>>> This is a vote to release Apache Camel 2.12.3, a patch
> release
> >>>>> coming
> >>>>>>> with about 128 issues fixed.
> >>>>>>>
> >>>>>>> Release notes:
> >>>>>>>
> >>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
> >>>>>>> Staging repo:
> >>>>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002
> >>>>>>>
> >>>>>>> Tarballs:
> >>>>>>>
> >>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
> >>>>>>> Tag:
> >>>>>>>
> >>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
> >>>>>>> Please test this release candidate and cast your vote.
> >>>>>>> [ ] +1 Release the binary as Apache Camel 2.12.3
> >>>>>>> [ ] -1 Veto the release (provide specific comments)
> >>>>>>> Vote is open for at least 72 hours.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Hadrian
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> View this message in context:
> >>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
> >>>>> Sent from the Camel Development mailing list archive at
> Nabble.com.
> >>>>>
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context:
> >>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747421.html
> >>> Sent from the Camel Development mailing list archive at Nabble.com.
> >
> >
> >
> >
> > --
> > View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747563.html
> > Sent from the Camel Development mailing list archive at Nabble.com.
>
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Babak, per the ASF policy we can release 2.12.3 even with -1s.
However, I usually shoot for consensus. Here's what I am going to do in
this case, because yours is the only -1 with an overwhelming majority of
+1s. I'll give it another 12 hours and if nothing changes I will close
the vote and release 2.12.3. If within this time you convince another
PMC member to change his vote I will cancel this vote.
We had two releases in the past, years ago (1.4 and 1.5 time) that were
built with a newer version that the oldest supported and we got burned
by the version of the class file format. (I was the one who messed up,
had to redo the releases and learned my lesson). I personally don't
release with a newer java version than the oldest supported.
Cheers,
Hadrian
[1] http://www.apache.org/dev/release.html
On 02/19/2014 10:19 AM, Babak Vahdat wrote:
> Hi Harian,
>
> I'm actually still -1 to this release candidate as the HTML documentation
> inside the bundles are missing (as a side effect of Java 6 being used for
> building instead of Java 7). This requirement has been clearly stated inside
> our release guides (yes, I was the one who added that note):
>
> http://camel.apache.org/release-guide.html
>
> And we've also discussed this many times @ the dev-forum as well:
>
> http://camel.465427.n5.nabble.com/improving-Endpoint-documentation-and-tooling-td5731334.html
> http://camel.465427.n5.nabble.com/Our-builds-looks-really-bad-tp5731673p5731743.html
>
> That all said, I may sound too pedantic, sorry for that!
>
> Last but not least I ask for apologies by the Apache Camel PMC because of
> the STUPID mistake I made while voting for the 2.11.4 release candidate:
>
> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747430.html
>
> As I had A LOT OF BEERS the night before that vote of mine. So I guess that
> was why my brain went terribly wrong :)
>
> Many thanks for your effort to prepare these two release candidates!
>
> Babak
>
>
> hadrian wrote
>> Babak,
>>
>> We're past the 72 hours mark and I would like to close this vote with a
>> consensus is possible. Do you still think we have an issue, or you want
>> to consider reverting your vote?
>>
>> Cheers,
>> Hadrian
>>
>>
>> On 02/17/2014 05:06 AM, Babak Vahdat wrote:
>>> Hi Willem,
>>>
>>> can you please elaborate your explanation a bit? Currently what we've on
>>> the
>>> 2.12.x. as well as 2.11.x branches is this:
>>>
>>>
>> <cxf-version>
>> 2.7.10
>> </cxf-version>
>>>
>> <cxf-version-range>
>> [2.6,2.9)
>> </cxf-version-range>
>>> Now to my understanding this should become:
>>>
>>>
>> <cxf-version>
>> 2.7.10
>> </cxf-version>
>>>
>> <cxf-version-range>
>> [2.6,3)
>> </cxf-version-range>
>>> I think the current range is a problem for the OSGi folks because if e.g.
>>> there's a bug-fix being provided in CXF 2.7.10, currently they can't
>>> force
>>> the Container to make use of CXF 2.7.10 while they install the
>>> "camel-cxf"
>>> feature version 2.12.3 or 2.11.4 (e.g. in the context of a dependency of
>>> their own Karaf feature "my-cool-app-karaf-feature") because the current
>>> range does NOT include 2.7.10.
>>>
>>> Babak
>>>
>>>
>>> Willem.Jiang wrote
>>>> There are some patches of supporting CXF 3.x are not merged to
>>>> camel-2.12.x and camel-2.11.x.
>>>> So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
>>>>
>>>> I don’t think it’s a show-stopper.
>>>>
>>>> --
>>>> Willem Jiang
>>>>
>>>> Red Hat, Inc.
>>>> Web: http://www.redhat.com
>>>> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
>>>> (English)
>>>> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
>>>> Twitter: willemjiang
>>>> Weibo: 姜宁willem
>>>>
>>>>
>>>>
>>>> On February 16, 2014 at 11:35:56 PM, Babak Vahdat (
>>>> babak.vahdat@
>>>> ) wrote:
>>>>>
>>>>> O.K. the build has been definetly done using Java 6 as this's how
>>>>> MANIFEST.MF
>>>>> of camel-core-2.12.3.jar looks like:
>>>>>
>>>>> Manifest-Version: 1.0
>>>>> Bnd-LastModified: 1392475192207
>>>>> Build-Jdk: 1.6.0_45
>>>>> Built-By: hadrian
>>>>> ...
>>>>>
>>>>>
>>>>> Other than that the backport of the fix for CAMEL-7170 did NOT
>>>>> adjust the
>>>>> maven property accordingly, so on the
>>>>> master branch
>>>>> we've got:
>>>>>
>>>>> 2.7.10
>>>>> [2.6,4.0)
>>>>>
>>>>> Which is fine, however on the 2.12.x as well as the 2.11.x branch
>>>>> we've got:
>>>>>
>>>>> 2.7.10
>>>>> [2.6,2.9)
>>>>>
>>>>> So here's my -1
>>>>>
>>>>> Babak
>>>>>
>>>>>
>>>>> Babak Vahdat wrote
>>>>>> Hi
>>>>>>
>>>>>> The HTML component documentation inside the JARs are missing.
>>>>> I assume
>>>>>> Java 6 has been used for building this release candidate. See
>>>>> also the
>>>>>> first "Note" @ http://camel.apache.org/release-guide.html
>>>>>>
>>>>>> Babak
>>>>>> hadrian wrote
>>>>>>> This is a vote to release Apache Camel 2.12.3, a patch release
>>>>> coming
>>>>>>> with about 128 issues fixed.
>>>>>>>
>>>>>>> Release notes:
>>>>>>>
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>>>>>> Staging repo:
>>>>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>>>>>>
>>>>>>> Tarballs:
>>>>>>>
>>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>>>>>> Tag:
>>>>>>>
>>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>>>>>> Please test this release candidate and cast your vote.
>>>>>>> [ ] +1 Release the binary as Apache Camel 2.12.3
>>>>>>> [ ] -1 Veto the release (provide specific comments)
>>>>>>> Vote is open for at least 72 hours.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Hadrian
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747421.html
>>> Sent from the Camel Development mailing list archive at Nabble.com.
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747563.html
> Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi Harian,
I'm actually still -1 to this release candidate as the HTML documentation
inside the bundles are missing (as a side effect of Java 6 being used for
building instead of Java 7). This requirement has been clearly stated inside
our release guides (yes, I was the one who added that note):
http://camel.apache.org/release-guide.html
And we've also discussed this many times @ the dev-forum as well:
http://camel.465427.n5.nabble.com/improving-Endpoint-documentation-and-tooling-td5731334.html
http://camel.465427.n5.nabble.com/Our-builds-looks-really-bad-tp5731673p5731743.html
That all said, I may sound too pedantic, sorry for that!
Last but not least I ask for apologies by the Apache Camel PMC because of
the STUPID mistake I made while voting for the 2.11.4 release candidate:
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747430.html
As I had A LOT OF BEERS the night before that vote of mine. So I guess that
was why my brain went terribly wrong :)
Many thanks for your effort to prepare these two release candidates!
Babak
hadrian wrote
> Babak,
>
> We're past the 72 hours mark and I would like to close this vote with a
> consensus is possible. Do you still think we have an issue, or you want
> to consider reverting your vote?
>
> Cheers,
> Hadrian
>
>
> On 02/17/2014 05:06 AM, Babak Vahdat wrote:
>> Hi Willem,
>>
>> can you please elaborate your explanation a bit? Currently what we've on
>> the
>> 2.12.x. as well as 2.11.x branches is this:
>>
>>
> <cxf-version>
> 2.7.10
> </cxf-version>
>>
> <cxf-version-range>
> [2.6,2.9)
> </cxf-version-range>
>>
>> Now to my understanding this should become:
>>
>>
> <cxf-version>
> 2.7.10
> </cxf-version>
>>
> <cxf-version-range>
> [2.6,3)
> </cxf-version-range>
>>
>> I think the current range is a problem for the OSGi folks because if e.g.
>> there's a bug-fix being provided in CXF 2.7.10, currently they can't
>> force
>> the Container to make use of CXF 2.7.10 while they install the
>> "camel-cxf"
>> feature version 2.12.3 or 2.11.4 (e.g. in the context of a dependency of
>> their own Karaf feature "my-cool-app-karaf-feature") because the current
>> range does NOT include 2.7.10.
>>
>> Babak
>>
>>
>> Willem.Jiang wrote
>>> There are some patches of supporting CXF 3.x are not merged to
>>> camel-2.12.x and camel-2.11.x.
>>> So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
>>>
>>> I don’t think it’s a show-stopper.
>>>
>>> --
>>> Willem Jiang
>>>
>>> Red Hat, Inc.
>>> Web: http://www.redhat.com
>>> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
>>> (English)
>>> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>>
>>>
>>>
>>> On February 16, 2014 at 11:35:56 PM, Babak Vahdat (
>>> babak.vahdat@
>>> ) wrote:
>>>>
>>>> O.K. the build has been definetly done using Java 6 as this's how
>>>> MANIFEST.MF
>>>> of camel-core-2.12.3.jar looks like:
>>>>
>>>> Manifest-Version: 1.0
>>>> Bnd-LastModified: 1392475192207
>>>> Build-Jdk: 1.6.0_45
>>>> Built-By: hadrian
>>>> ...
>>>>
>>>>
>>>> Other than that the backport of the fix for CAMEL-7170 did NOT
>>>> adjust the
>>>> maven property accordingly, so on the
>>>> master branch
>>>> we've got:
>>>>
>>>> 2.7.10
>>>> [2.6,4.0)
>>>>
>>>> Which is fine, however on the 2.12.x as well as the 2.11.x branch
>>>> we've got:
>>>>
>>>> 2.7.10
>>>> [2.6,2.9)
>>>>
>>>> So here's my -1
>>>>
>>>> Babak
>>>>
>>>>
>>>> Babak Vahdat wrote
>>>>> Hi
>>>>>
>>>>> The HTML component documentation inside the JARs are missing.
>>>> I assume
>>>>> Java 6 has been used for building this release candidate. See
>>>> also the
>>>>> first "Note" @ http://camel.apache.org/release-guide.html
>>>>>
>>>>> Babak
>>>>> hadrian wrote
>>>>>> This is a vote to release Apache Camel 2.12.3, a patch release
>>>> coming
>>>>>> with about 128 issues fixed.
>>>>>>
>>>>>> Release notes:
>>>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>>>>> Staging repo:
>>>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>>>>>
>>>>>> Tarballs:
>>>>>>
>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>>>>> Tag:
>>>>>>
>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>>>>> Please test this release candidate and cast your vote.
>>>>>> [ ] +1 Release the binary as Apache Camel 2.12.3
>>>>>> [ ] -1 Veto the release (provide specific comments)
>>>>>> Vote is open for at least 72 hours.
>>>>>>
>>>>>> Thanks,
>>>>>> Hadrian
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747421.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747563.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Babak,
We're past the 72 hours mark and I would like to close this vote with a
consensus is possible. Do you still think we have an issue, or you want
to consider reverting your vote?
Cheers,
Hadrian
On 02/17/2014 05:06 AM, Babak Vahdat wrote:
> Hi Willem,
>
> can you please elaborate your explanation a bit? Currently what we've on the
> 2.12.x. as well as 2.11.x branches is this:
>
> <cxf-version>2.7.10</cxf-version>
> <cxf-version-range>[2.6,2.9)</cxf-version-range>
>
> Now to my understanding this should become:
>
> <cxf-version>2.7.10</cxf-version>
> <cxf-version-range>[2.6,3)</cxf-version-range>
>
> I think the current range is a problem for the OSGi folks because if e.g.
> there's a bug-fix being provided in CXF 2.7.10, currently they can't force
> the Container to make use of CXF 2.7.10 while they install the "camel-cxf"
> feature version 2.12.3 or 2.11.4 (e.g. in the context of a dependency of
> their own Karaf feature "my-cool-app-karaf-feature") because the current
> range does NOT include 2.7.10.
>
> Babak
>
>
> Willem.Jiang wrote
>> There are some patches of supporting CXF 3.x are not merged to
>> camel-2.12.x and camel-2.11.x.
>> So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
>>
>> I don’t think it’s a show-stopper.
>>
>> --
>> Willem Jiang
>>
>> Red Hat, Inc.
>> Web: http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
>> (English)
>> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>> On February 16, 2014 at 11:35:56 PM, Babak Vahdat (
>> babak.vahdat@
>> ) wrote:
>>>
>>> O.K. the build has been definetly done using Java 6 as this's how
>>> MANIFEST.MF
>>> of camel-core-2.12.3.jar looks like:
>>>
>>> Manifest-Version: 1.0
>>> Bnd-LastModified: 1392475192207
>>> Build-Jdk: 1.6.0_45
>>> Built-By: hadrian
>>> ...
>>>
>>>
>>> Other than that the backport of the fix for CAMEL-7170 did NOT
>>> adjust the
>>> maven property accordingly, so on the
>>> master branch
>>> we've got:
>>>
>>> 2.7.10
>>> [2.6,4.0)
>>>
>>> Which is fine, however on the 2.12.x as well as the 2.11.x branch
>>> we've got:
>>>
>>> 2.7.10
>>> [2.6,2.9)
>>>
>>> So here's my -1
>>>
>>> Babak
>>>
>>>
>>> Babak Vahdat wrote
>>>> Hi
>>>>
>>>> The HTML component documentation inside the JARs are missing.
>>> I assume
>>>> Java 6 has been used for building this release candidate. See
>>> also the
>>>> first "Note" @ http://camel.apache.org/release-guide.html
>>>>
>>>> Babak
>>>> hadrian wrote
>>>>> This is a vote to release Apache Camel 2.12.3, a patch release
>>> coming
>>>>> with about 128 issues fixed.
>>>>>
>>>>> Release notes:
>>>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>>>> Staging repo:
>>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>>>>
>>>>> Tarballs:
>>>>>
>>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>>>> Tag:
>>>>>
>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>>>> Please test this release candidate and cast your vote.
>>>>> [ ] +1 Release the binary as Apache Camel 2.12.3
>>>>> [ ] -1 Veto the release (provide specific comments)
>>>>> Vote is open for at least 72 hours.
>>>>>
>>>>> Thanks,
>>>>> Hadrian
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747421.html
> Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi Willem,
can you please elaborate your explanation a bit? Currently what we've on the
2.12.x. as well as 2.11.x branches is this:
<cxf-version>2.7.10</cxf-version>
<cxf-version-range>[2.6,2.9)</cxf-version-range>
Now to my understanding this should become:
<cxf-version>2.7.10</cxf-version>
<cxf-version-range>[2.6,3)</cxf-version-range>
I think the current range is a problem for the OSGi folks because if e.g.
there's a bug-fix being provided in CXF 2.7.10, currently they can't force
the Container to make use of CXF 2.7.10 while they install the "camel-cxf"
feature version 2.12.3 or 2.11.4 (e.g. in the context of a dependency of
their own Karaf feature "my-cool-app-karaf-feature") because the current
range does NOT include 2.7.10.
Babak
Willem.Jiang wrote
> There are some patches of supporting CXF 3.x are not merged to
> camel-2.12.x and camel-2.11.x.
> So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
>
> I don’t think it’s a show-stopper.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
> (English)
> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On February 16, 2014 at 11:35:56 PM, Babak Vahdat (
> babak.vahdat@
> ) wrote:
>>
>> O.K. the build has been definetly done using Java 6 as this's how
>> MANIFEST.MF
>> of camel-core-2.12.3.jar looks like:
>>
>> Manifest-Version: 1.0
>> Bnd-LastModified: 1392475192207
>> Build-Jdk: 1.6.0_45
>> Built-By: hadrian
>> ...
>>
>>
>> Other than that the backport of the fix for CAMEL-7170 did NOT
>> adjust the
>> maven property accordingly, so on the
>> master branch
>> we've got:
>>
>> 2.7.10
>> [2.6,4.0)
>>
>> Which is fine, however on the 2.12.x as well as the 2.11.x branch
>> we've got:
>>
>> 2.7.10
>> [2.6,2.9)
>>
>> So here's my -1
>>
>> Babak
>>
>>
>> Babak Vahdat wrote
>> > Hi
>> >
>> > The HTML component documentation inside the JARs are missing.
>> I assume
>> > Java 6 has been used for building this release candidate. See
>> also the
>> > first "Note" @ http://camel.apache.org/release-guide.html
>> >
>> > Babak
>> > hadrian wrote
>> >> This is a vote to release Apache Camel 2.12.3, a patch release
>> coming
>> >> with about 128 issues fixed.
>> >>
>> >> Release notes:
>> >>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>> >>
>> >> Staging repo:
>> >> https://repository.apache.org/content/repositories/orgapachecamel-1002
>> >>
>> >> Tarballs:
>> >>
>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>> >>
>> >> Tag:
>> >>
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>> >>
>> >> Please test this release candidate and cast your vote.
>> >> [ ] +1 Release the binary as Apache Camel 2.12.3
>> >> [ ] -1 Veto the release (provide specific comments)
>> >> Vote is open for at least 72 hours.
>> >>
>> >> Thanks,
>> >> Hadrian
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747421.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Willem Jiang <wi...@gmail.com>.
There are some patches of supporting CXF 3.x are not merged to camel-2.12.x and camel-2.11.x.
So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
I don’t think it’s a show-stopper.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 16, 2014 at 11:35:56 PM, Babak Vahdat (babak.vahdat@swissonline.ch) wrote:
>
> O.K. the build has been definetly done using Java 6 as this's how
> MANIFEST.MF
> of camel-core-2.12.3.jar looks like:
>
> Manifest-Version: 1.0
> Bnd-LastModified: 1392475192207
> Build-Jdk: 1.6.0_45
> Built-By: hadrian
> ...
>
>
> Other than that the backport of the fix for CAMEL-7170 did NOT
> adjust the
> maven property accordingly, so on the
> master branch
> we've got:
>
> 2.7.10
> [2.6,4.0)
>
> Which is fine, however on the 2.12.x as well as the 2.11.x branch
> we've got:
>
> 2.7.10
> [2.6,2.9)
>
> So here's my -1
>
> Babak
>
>
> Babak Vahdat wrote
> > Hi
> >
> > The HTML component documentation inside the JARs are missing.
> I assume
> > Java 6 has been used for building this release candidate. See
> also the
> > first "Note" @ http://camel.apache.org/release-guide.html
> >
> > Babak
> > hadrian wrote
> >> This is a vote to release Apache Camel 2.12.3, a patch release
> coming
> >> with about 128 issues fixed.
> >>
> >> Release notes:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/orgapachecamel-1002
> >>
> >> Tarballs:
> >> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
> >>
> >> Tag:
> >> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
> >>
> >> Please test this release candidate and cast your vote.
> >> [ ] +1 Release the binary as Apache Camel 2.12.3
> >> [ ] -1 Veto the release (provide specific comments)
> >> Vote is open for at least 72 hours.
> >>
> >> Thanks,
> >> Hadrian
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Babak Vahdat <ba...@swissonline.ch>.
O.K. the build has been definetly done using Java 6 as this's how MANIFEST.MF
of camel-core-2.12.3.jar looks like:
Manifest-Version: 1.0
Bnd-LastModified: 1392475192207
Build-Jdk: 1.6.0_45
Built-By: hadrian
...
Other than that the backport of the fix for CAMEL-7170 did NOT adjust the
maven property <cxf-version-range> accordingly, so on the master branch
we've got:
<cxf-version>2.7.10</cxf-version>
<cxf-version-range>[2.6,4.0)</cxf-version-range>
Which is fine, however on the 2.12.x as well as the 2.11.x branch we've got:
<cxf-version>2.7.10</cxf-version>
<cxf-version-range>[2.6,2.9)</cxf-version-range>
So here's my -1
Babak
Babak Vahdat wrote
> Hi
>
> The HTML component documentation inside the JARs are missing. I assume
> Java 6 has been used for building this release candidate. See also the
> first "Note" @ http://camel.apache.org/release-guide.html
>
> Babak
> hadrian wrote
>> This is a vote to release Apache Camel 2.12.3, a patch release coming
>> with about 128 issues fixed.
>>
>> Release notes:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>
>> Tarballs:
>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>
>> Tag:
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>
>> Please test this release candidate and cast your vote.
>> [ ] +1 Release the binary as Apache Camel 2.12.3
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks,
>> Hadrian
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Willem Jiang <wi...@gmail.com>.
I think we need to release Apache Camel 2.12.x with JDK7 as we did before.
In this way it could generate better HTML component documentation for the other tools to use.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 16, 2014 at 6:07:01 PM, Babak Vahdat (babak.vahdat@swissonline.ch) wrote:
>
> Hi
>
> The HTML component documentation inside the JARs are missing.
> I assume Java
> 6 has been used for building this release candidate. See also
> the first
> "Note" @ http://camel.apache.org/release-guide.html
>
> Babak
>
>
> hadrian wrote
> > This is a vote to release Apache Camel 2.12.3, a patch release
> coming
> > with about 128 issues fixed.
> >
> > Release notes:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachecamel-1002
> >
> > Tarballs:
> > https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
> >
> > Tag:
> > https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as Apache Camel 2.12.3
> > [ ] -1 Veto the release (provide specific comments)
> > Vote is open for at least 72 hours.
> >
> > Thanks,
> > Hadrian
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747366.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi
The HTML component documentation inside the JARs are missing. I assume Java
6 has been used for building this release candidate. See also the first
"Note" @ http://camel.apache.org/release-guide.html
Babak
hadrian wrote
> This is a vote to release Apache Camel 2.12.3, a patch release coming
> with about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1002
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.12.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747366.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Aki Yoshida <el...@gmail.com>.
+1 (non-binding)
aki
2014-02-16 5:16 GMT+01:00 Hadrian Zbarcea <hz...@gmail.com>:
> This is a vote to release Apache Camel 2.12.3, a patch release coming with
> about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1002
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.12.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
AW: [CANCEL][VOTE] Release Apache Camel 2.12.3
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
AFAIK that vulnerability is inside the built javadoc-html.
Is that generated javadoc part of the release?
I checked http://apache.openmirror.de/camel/apache-camel/2.12.2/apache-camel-2.12.2.zip and didnt found any javadoc.
So that wouldnt force the use of Java7.
Jan
> -----Ursprüngliche Nachricht-----
> Von: Willem Jiang [mailto:willem.jiang@gmail.com]
> Gesendet: Donnerstag, 20. Februar 2014 08:43
> An: dev@camel.apache.org
> Betreff: Re: [CANCEL][VOTE] Release Apache Camel 2.12.3
>
> "Supports JDK 6" could mean from the source and binary level, but we
> still need to choice one version of JDK to build the kit. There is a
> known javadoc issue[1] which we cannot get fix from public released
> JDK6, so I prefer to build the kit with JDK7 and make sure the classes
> are target to 1.6.
>
> I can cut a new version Camel 2.12.3 this week but we need to postpone
> the release of Camel 2.13.0 , as I don’t have enough time to do two
> release this month.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
> (English)
> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On February 20, 2014 at 11:03:42 AM, Hadrian Zbarcea
> (hzbarcea@gmail.com) wrote:
> >
> > While we had enough votes to pass this release I chose not to. I
> don't
> > have cycles to cut another release in the next week week or so.
> > This
> > release is also blocking the AMQ release.
> >
> > I would not release with 1.7 anyway, so maybe it would be a good idea
> > to look into fixing the html doc stuff with 1.6 if it's that
> important
> > to you guys. There are many users who rebuild Camel from sources and
> > what you are saying is that while we support 1.6, we actually don't.
> >
> > Cheers,
> > Hadrian
> >
> >
> >
> > On 02/19/2014 09:53 PM, Hadrian Zbarcea wrote:
> > > On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
> > >> This is a vote to release Apache Camel 2.12.3, a patch release
> > coming
> > >> with about 128 issues fixed.
> > >>
> > >> Release notes:
> > >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12
> > >> 311211&version=12325593
> > >>
> > >>
> > >> Staging repo:
> > >> https://repository.apache.org/content/repositories/orgapachecamel-
> 1
> > >> 002
> > >>
> > >> Tarballs:
> > >> https://repository.apache.org/content/repositories/orgapachecamel-
> 1
> > >> 002/org/apache/camel/apache-camel/2.12.3/
> > >>
> > >>
> > >> Tag:
> > >> https://git-wip-
> us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2
> > >> e2cbc34fda60d68c0dd33cb39d63ba1c6
> > >>
> > >>
> > >> Please test this release candidate and cast your vote.
> > >> [ ] +1 Release the binary as Apache Camel 2.12.3 [ ] -1 Veto the
> > >> release (provide specific comments) Vote is open for at least 72
> > >> hours.
> > >>
> > >> Thanks,
> > >> Hadrian
> > >
> >
> >
Re: [CANCEL][VOTE] Release Apache Camel 2.12.3
Posted by Hadrian Zbarcea <hz...@gmail.com>.
My point is this: if we say that Camel supports 1.6 then it should be
built with 1.6 with the expected results, including the html doc if we
claim that to be part of the release. Otherwise we support 1.6 only for
runtime, which is not what we say actually. I think this has to be
clarified before the next 2.12.x release. Without this fixed, I will -1
the next 2.12.x release, because part of testing the release I will
build from sources.
Cheers,
Hadrian
On 02/20/2014 02:43 AM, Willem Jiang wrote:
> "Supports JDK 6" could mean from the source and binary level, but we still need to choice one version of JDK to build the kit. There is a known javadoc issue[1] which we cannot get fix from public released JDK6, so I prefer to build the kit with JDK7 and make sure the classes are target to 1.6.
>
> I can cut a new version Camel 2.12.3 this week but we need to postpone the release of Camel 2.13.0 , as I don’t have enough time to do two release this month.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On February 20, 2014 at 11:03:42 AM, Hadrian Zbarcea (hzbarcea@gmail.com) wrote:
>>
>> While we had enough votes to pass this release I chose not to. I
>> don't
>> have cycles to cut another release in the next week week or so.
>> This
>> release is also blocking the AMQ release.
>>
>> I would not release with 1.7 anyway, so maybe it would be a good
>> idea to
>> look into fixing the html doc stuff with 1.6 if it's that important
>> to
>> you guys. There are many users who rebuild Camel from sources
>> and what
>> you are saying is that while we support 1.6, we actually don't.
>>
>> Cheers,
>> Hadrian
>>
>>
>>
>> On 02/19/2014 09:53 PM, Hadrian Zbarcea wrote:
>>> On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
>>>> This is a vote to release Apache Camel 2.12.3, a patch release
>> coming
>>>> with about 128 issues fixed.
>>>>
>>>> Release notes:
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>>>
>>>>
>>>> Staging repo:
>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>>>
>>>> Tarballs:
>>>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>>>
>>>>
>>>> Tag:
>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>>>
>>>>
>>>> Please test this release candidate and cast your vote.
>>>> [ ] +1 Release the binary as Apache Camel 2.12.3
>>>> [ ] -1 Veto the release (provide specific comments)
>>>> Vote is open for at least 72 hours.
>>>>
>>>> Thanks,
>>>> Hadrian
>>
>>
Re: [CANCEL][VOTE] Release Apache Camel 2.12.3
Posted by Willem Jiang <wi...@gmail.com>.
Here is the link of javadoc issue[1] which I forgot to add in my last mail.
[1]http://blog.trendmicro.com/trendlabs-security-intelligence/oracle-update-includes-javadoc-frame-injection-vulnerability/
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 20, 2014 at 3:43:43 PM, Willem Jiang (willem.jiang@gmail.com) wrote:
>
> "Supports JDK 6" could mean from the source and binary level,
> but we still need to choice one version of JDK to build the kit.
> There is a known javadoc issue[1] which we cannot get fix from
> public released JDK6, so I prefer to build the kit with JDK7 and
> make sure the classes are target to 1.6.
>
> I can cut a new version Camel 2.12.3 this week but we need to postpone
> the release of Camel 2.13.0 , as I don’t have enough time to do two
> release this month.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
> (English)
> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On February 20, 2014 at 11:03:42 AM, Hadrian Zbarcea (hzbarcea@gmail.com)
> wrote:
> >
> > While we had enough votes to pass this release I chose not to.
> I
> > don't
> > have cycles to cut another release in the next week week or so.
> > This
> > release is also blocking the AMQ release.
> >
> > I would not release with 1.7 anyway, so maybe it would be a good
> > idea to
> > look into fixing the html doc stuff with 1.6 if it's that important
> > to
> > you guys. There are many users who rebuild Camel from sources
> > and what
> > you are saying is that while we support 1.6, we actually don't.
> >
> > Cheers,
> > Hadrian
> >
> >
> >
> > On 02/19/2014 09:53 PM, Hadrian Zbarcea wrote:
> > > On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
> > >> This is a vote to release Apache Camel 2.12.3, a patch release
> > coming
> > >> with about 128 issues fixed.
> > >>
> > >> Release notes:
> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
> > >>
> > >>
> > >> Staging repo:
> > >> https://repository.apache.org/content/repositories/orgapachecamel-1002
> > >>
> > >> Tarballs:
> > >> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
> > >>
> > >>
> > >> Tag:
> > >> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
> > >>
> > >>
> > >> Please test this release candidate and cast your vote.
> > >> [ ] +1 Release the binary as Apache Camel 2.12.3
> > >> [ ] -1 Veto the release (provide specific comments)
> > >> Vote is open for at least 72 hours.
> > >>
> > >> Thanks,
> > >> Hadrian
> > >
> >
> >
>
>
Re: [CANCEL][VOTE] Release Apache Camel 2.12.3
Posted by Willem Jiang <wi...@gmail.com>.
"Supports JDK 6" could mean from the source and binary level, but we still need to choice one version of JDK to build the kit. There is a known javadoc issue[1] which we cannot get fix from public released JDK6, so I prefer to build the kit with JDK7 and make sure the classes are target to 1.6.
I can cut a new version Camel 2.12.3 this week but we need to postpone the release of Camel 2.13.0 , as I don’t have enough time to do two release this month.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 20, 2014 at 11:03:42 AM, Hadrian Zbarcea (hzbarcea@gmail.com) wrote:
>
> While we had enough votes to pass this release I chose not to. I
> don't
> have cycles to cut another release in the next week week or so.
> This
> release is also blocking the AMQ release.
>
> I would not release with 1.7 anyway, so maybe it would be a good
> idea to
> look into fixing the html doc stuff with 1.6 if it's that important
> to
> you guys. There are many users who rebuild Camel from sources
> and what
> you are saying is that while we support 1.6, we actually don't.
>
> Cheers,
> Hadrian
>
>
>
> On 02/19/2014 09:53 PM, Hadrian Zbarcea wrote:
> > On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
> >> This is a vote to release Apache Camel 2.12.3, a patch release
> coming
> >> with about 128 issues fixed.
> >>
> >> Release notes:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
> >>
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/orgapachecamel-1002
> >>
> >> Tarballs:
> >> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
> >>
> >>
> >> Tag:
> >> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
> >>
> >>
> >> Please test this release candidate and cast your vote.
> >> [ ] +1 Release the binary as Apache Camel 2.12.3
> >> [ ] -1 Veto the release (provide specific comments)
> >> Vote is open for at least 72 hours.
> >>
> >> Thanks,
> >> Hadrian
> >
>
>
AW: [CANCEL][VOTE] Release Apache Camel 2.12.3
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
> I would not release with 1.7 anyway, so maybe it would be a good idea
> to look into fixing the html doc stuff with 1.6 if it's that important
> to you guys. There are many users who rebuild Camel from sources and
> what you are saying is that while we support 1.6, we actually don't.
>
> Cheers,
> Hadrian
I found a list which Java versions are supported:
http://camel.apache.org/can-i-use-camel-on-java-14.html
- Camel <2 .7.0: Java5
- Camel 2. 7.0: Java6
- Camel 2.10.0: Java6 required, Java7 supported
Jan
Re: [CANCEL][VOTE] Release Apache Camel 2.12.3
Posted by Hadrian Zbarcea <hz...@gmail.com>.
While we had enough votes to pass this release I chose not to. I don't
have cycles to cut another release in the next week week or so. This
release is also blocking the AMQ release.
I would not release with 1.7 anyway, so maybe it would be a good idea to
look into fixing the html doc stuff with 1.6 if it's that important to
you guys. There are many users who rebuild Camel from sources and what
you are saying is that while we support 1.6, we actually don't.
Cheers,
Hadrian
On 02/19/2014 09:53 PM, Hadrian Zbarcea wrote:
> On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
>> This is a vote to release Apache Camel 2.12.3, a patch release coming
>> with about 128 issues fixed.
>>
>> Release notes:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>
>> Tarballs:
>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>
>>
>> Tag:
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>
>>
>> Please test this release candidate and cast your vote.
>> [ ] +1 Release the binary as Apache Camel 2.12.3
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks,
>> Hadrian
>
[CANCEL][VOTE] Release Apache Camel 2.12.3
Posted by Hadrian Zbarcea <hz...@gmail.com>.
On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
> This is a vote to release Apache Camel 2.12.3, a patch release coming
> with about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1002
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.12.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Henryk Konsek <he...@gmail.com>.
+1 (non-binding)
On Tue, Feb 18, 2014 at 3:56 PM, Raul Kripalani <ra...@evosent.com> wrote:
> +1.
>
> *Raúl Kripalani*
> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> Integration specialist
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Sun, Feb 16, 2014 at 4:16 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
>
>> This is a vote to release Apache Camel 2.12.3, a patch release coming with
>> about 128 issues fixed.
>>
>> Release notes:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12311211&version=12325593
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>
>> Tarballs:
>> https://repository.apache.org/content/repositories/
>> orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>
>> Tag:
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
>> 4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>
>> Please test this release candidate and cast your vote.
>> [ ] +1 Release the binary as Apache Camel 2.12.3
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks,
>> Hadrian
>>
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Raul Kripalani <ra...@evosent.com>.
+1.
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Sun, Feb 16, 2014 at 4:16 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> This is a vote to release Apache Camel 2.12.3, a patch release coming with
> about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311211&version=12325593
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1002
>
> Tarballs:
> https://repository.apache.org/content/repositories/
> orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
> 4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.12.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Gert Vanthienen <ge...@gmail.com>.
+1
Regards,
Gert Vanthienen
On Wed, Feb 19, 2014 at 2:37 AM, Willem Jiang <wi...@gmail.com> wrote:
> +1
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On February 16, 2014 at 12:17:03 PM, Hadrian Zbarcea (hzbarcea@gmail.com) wrote:
>>
>> This is a vote to release Apache Camel 2.12.3, a patch release
>> coming
>> with about 128 issues fixed.
>>
>> Release notes:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>
>> Tarballs:
>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>
>> Tag:
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>
>> Please test this release candidate and cast your vote.
>> [ ] +1 Release the binary as Apache Camel 2.12.3
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks,
>> Hadrian
>>
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Willem Jiang <wi...@gmail.com>.
+1
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 16, 2014 at 12:17:03 PM, Hadrian Zbarcea (hzbarcea@gmail.com) wrote:
>
> This is a vote to release Apache Camel 2.12.3, a patch release
> coming
> with about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1002
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.12.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Christian Posta <ch...@gmail.com>.
looking forward to this release, +1
On Mon, Feb 17, 2014 at 5:01 PM, Johan Edstrom <se...@gmail.com> wrote:
> +1
> On Feb 17, 2014, at 2:11 PM, Christian Schneider <ch...@die-schneider.net> wrote:
>
>> +1
>>
>> Christian
>>
>> Am 16.02.2014 05:16, schrieb Hadrian Zbarcea:
>>> This is a vote to release Apache Camel 2.12.3, a patch release coming with about 128 issues fixed.
>>>
>>> Release notes:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>>
>>> Tarballs:
>>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>>
>>> Tag:
>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>>
>>> Please test this release candidate and cast your vote.
>>> [ ] +1 Release the binary as Apache Camel 2.12.3
>>> [ ] -1 Veto the release (provide specific comments)
>>> Vote is open for at least 72 hours.
>>>
>>> Thanks,
>>> Hadrian
>>
>>
>> --
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Open Source Architect
>> Talend Application Integration Division http://www.talend.com
>>
>
--
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Johan Edstrom <se...@gmail.com>.
+1
On Feb 17, 2014, at 2:11 PM, Christian Schneider <ch...@die-schneider.net> wrote:
> +1
>
> Christian
>
> Am 16.02.2014 05:16, schrieb Hadrian Zbarcea:
>> This is a vote to release Apache Camel 2.12.3, a patch release coming with about 128 issues fixed.
>>
>> Release notes:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachecamel-1002
>>
>> Tarballs:
>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>
>> Tag:
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>
>> Please test this release candidate and cast your vote.
>> [ ] +1 Release the binary as Apache Camel 2.12.3
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks,
>> Hadrian
>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Christian Schneider <ch...@die-schneider.net>.
+1
Christian
Am 16.02.2014 05:16, schrieb Hadrian Zbarcea:
> This is a vote to release Apache Camel 2.12.3, a patch release coming
> with about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1002
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.12.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
Re: [VOTE] Release Apache Camel 2.12.3
Posted by Christian Müller <ch...@gmail.com>.
+1
The signatures are good.
The doc looks good (we only have to update the copyright year).
I could upgrade Camel-in-action to Camel 2.12.3 (and CXF 2.7.10) without
any issues.
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 Sun, Feb 16, 2014 at 5:16 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> This is a vote to release Apache Camel 2.12.3, a patch release coming with
> about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311211&version=12325593
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1002
>
> Tarballs:
> https://repository.apache.org/content/repositories/
> orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
> 4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.12.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
>