+1
Too late to count, but builds from sources produce the expected results
with both Java 6 and Java 7. Signatures are good, features work,
examples work.
Hadrian
On 02/25/2014 12:44 AM, Willem Jiang wrote:
The vote passes with:
[4] +1 (ningjiang, davsclaus, bvahdat, mueller)
[0] -1
I wil
The vote passes with:
[4] +1 (ningjiang, davsclaus, bvahdat, mueller)
[0] -1
I will proceed with publishing the artifacts today and make public
announcement of the release after the mirrors sync up.
Many thanks to all contributors,
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.co
+1
The signatures are good and the manual looks good too.
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
+1
I verified the HTML documentation of the following bundles which are all in
place (although the build is done using Java 6):
- camel-core
- camel-ftp
- camel-jms
- camel-twitter
Babak
Willem.Jiang wrote
> This is a vote to release Apache Camel 2.12.3, a patch release coming
> with about 14
+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.li
On Thu, Feb 20, 2014 at 7:45 AM, Jan Matèrne (jhm) 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.
>>
>>
Hi Dan,
Thanks for the inputs.
Current the html generator is based the APT processor, But it looks JDK6 have
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
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 p
+1
I didn't have time to test that 1st attempt. But here friday afternoon
I gave a little test spin.
I wanted to check that the camel-example-console worked again = OK.
Also I tried Karaf 2.3.4 and installed the camel-example-osgi and it
worked fine = OK.
On Fri, Feb 21, 2014 at 3:59 PM, Will
I did a quick check of the kit and ran the all tests of camel-in-action,
every thing looks fine.
Here is my +1.
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.
This is a vote to release Apache Camel 2.12.3, a patch release coming
with about 140 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-1004
On Feb 21, 2014, at 5:12 AM, 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
; writer.println(""); <=== should include
> the title!
>
> Jan
>
>
> > -Ursprüngliche Nachricht-
> > Von: Babak Vahdat [mailto:babak.vah...@swissonline.ch]
> > Gesendet: Freitag, 21. Februar 2014 11:12
> > An: dev@camel.apache.org
> > Betre
online.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 als
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.
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.blogs
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 RetentionPolic
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 ca
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
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 befor
che Nachricht-
> Von: Willem Jiang [mailto:willem.ji...@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, bu
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.co
"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 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,
> 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 th
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 wit
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
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 re
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
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 rel
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):
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 expl
+1
Regards,
Gert Vanthienen
On Wed, Feb 19, 2014 at 2:37 AM, Willem Jiang 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/) (Chi
+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 (
+1
Dan
On Feb 15, 2014, at 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 r
+1
On Sun, Feb 16, 2014 at 12:46 AM, 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:
+1 (non-binding)
On Tue, Feb 18, 2014 at 3:56 PM, Raul Kripalani 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
+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 wrote:
> This i
+1 (non-binding)
aki
2014-02-16 5:16 GMT+01:00 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:
looking forward to this release, +1
On Mon, Feb 17, 2014 at 5:01 PM, Johan Edstrom wrote:
> +1
> On Feb 17, 2014, at 2:11 PM, Christian Schneider
> 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 relea
+1
On Feb 17, 2014, at 2:11 PM, Christian Schneider
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/secu
+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://rep
+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
Did he mean that it doesn't FORCE 2.7.10?
> On Feb 17, 2014, at 4:55 AM, James Carman 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
> wrote:
>> Hi Willem,
>>
>> can you please elaborate your ex
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
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
>
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
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.co
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(ht
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 prope
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
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
Tarb
51 matches
Mail list logo
