Hi
On 11/06/12 14:35, Sergey Beryozkin wrote:
Hi Dan, All,
sorry for a delay
On 08/06/12 20:55, Daniel Kulp wrote:
Not really much of a discussion, but no objections either. Thus, I'll go
ahead and create the branch. :-)
Dan
On Friday, June 01, 2012 11:10:26 AM Daniel Kulp wrote:
With
Hi Dan, All,
sorry for a delay
On 08/06/12 20:55, Daniel Kulp wrote:
Not really much of a discussion, but no objections either. Thus, I'll go
ahead and create the branch. :-)
Dan
On Friday, June 01, 2012 11:10:26 AM Daniel Kulp wrote:
With 2.6.1 hopefully going out shortly, I'd like to
Not really much of a discussion, but no objections either. Thus, I'll go
ahead and create the branch. :-)
Dan
On Friday, June 01, 2012 11:10:26 AM Daniel Kulp wrote:
With 2.6.1 hopefully going out shortly, I'd like to get peoples thoughts
about creating a 2.6.x-fixes branch and changing
+1.
I intend on introducing streaming WS-Security support in 2.7, which will
depend on Santuario 2.0 and WSS4J 2.0, both of which are slated to require
JDK 1.6.
Colm.
On Fri, Jun 1, 2012 at 4:10 PM, Daniel Kulp dk...@apache.org wrote:
With 2.6.1 hopefully going out shortly, I'd like to get
+1 for both branching out and dropping Java 5 Support.
Regards,
Ulhas Bhole
On 5 Jun 2012, at 10:11, Colm O hEigeartaigh wrote:
+1.
I intend on introducing streaming WS-Security support in 2.7, which will
depend on Santuario 2.0 and WSS4J 2.0, both of which are slated to require
JDK
With 2.6.1 hopefully going out shortly, I'd like to get peoples thoughts
about creating a 2.6.x-fixes branch and changing trunk to target 2.7. Here
is a list of some things I'd like to start thinking about for 2.7:
1) Drop support for Java 5 - this may be a bit contentious. :-) It would
