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
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/100
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post your response.
If your project does not have this feature enabled
"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
GitHub user emacarron opened a pull request:
https://github.com/apache/camel/pull/100
Update MyBatis version from 3.2.4 to 3.2.5
Hi guys,
We released a minor version of MyBatis last week.
Keep up the good work!!
You can merge this pull request into a Git repository
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
Hello,
The org.apache.camel.component.spring.ws.SpringWebserviceConsumer extract
headers and properties of the message context. But cannot find anything
about the attachments. Currently we're using the below processor
implementation to add the received attachments to the exchange.
Some ideas:
-
The vote passes with:
[10] +1 (joed, bvahdat, joed, cschneider, cmueller, raulk, janstey,
dkulp, ningjiang, hadrian)
[1] +1 - non-binding (ceposta)
[0] -1
I will proceed with publishing the artifacts today and make public
announcement of the release tomorrow, after the mirrors sync up.
Many
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):
Forgot my +1.
On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
This is a vote to release Apache Camel 2.11.4, a patch release coming
with about 26 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
Staging repo:
https://rep
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
> Yeah, I'll roll back the changes from the SpringNameSpaceHandler. We
> don't cover this part of code by tests and I don't want to break
> existing code.
Returned original SpringNamespaceHandler code in
667443aee325b406e57b16d4c70d1971fb001294.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
18 matches
Mail list logo
