You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by Colm O hEigeartaigh <co...@apache.org> on 2011/02/14 12:45:35 UTC
[ATTN] WSS4J 1.6-alpha distribution
All,
I have created an "unofficial" WSS4J 1.6-alpha release. I was going to
call a vote and push it to Maven Central as an "alpha" release, but I
have decided to wait until the beta before doing this. The
distribution is available here:
http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/dist/
and the Maven artifacts are available here:
http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/maven/
Please download and play around with it etc. All the usual caveats
apply - it is an alpha version only, *not* suitable for production in
any way, and the APIs are subject to change. *Now* is your chance to
object to any changes that have been made, or to suggest alterations,
tweaks, etc.
The 1.6 release will *not* be backwards compatible with 1.5.x, and so
some work will be required for third-party projects to upgrade to
WSS4J 1.6. Rampart devs in particular should take note - please do not
raise objections in a months time when I call a vote, now is the time.
I've just merged a CXF branch that upgraded from WSS4J 1.5.x -> 1.6 to
trunk.
A rough timeline for this release is as follows:
11 Feb - alpha release
25 Feb - beta release
4 Mar - RC
11 Mar - Vote
91 issues have been closed or resolved for 1.6 (please see JIRA for
more details). 6 issues remain to be fixed at this point.
Colm.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
Re: [ATTN] WSS4J 1.6-alpha distribution
Posted by Thilina Mahesh Buddhika <th...@gmail.com>.
Thanks Colm.
We are planning to doing some cleanup work on Rampart trunk while moving to
WSS4J 1.6 .
Also there will be one or two point releases based on 1_6 branch, for which
we can use WSS4J 1.5.11.
So we have some time to fix and stabilize Rampart trunk on WSS4J 1.6.
Thanks,
Thilina
On Mon, Feb 28, 2011 at 10:24 PM, Colm O hEigeartaigh
<co...@apache.org>wrote:
> Thanks! Feel free to ask me any questions in terms of upgrading
> Rampart to use WSS4J 1.6. You will see quite a lot of compilation
> errors, but most are fairly obvious. There are some slightly tricky
> changes in relation to code which calls WSSecSignature, which was
> necessitated by the move to use the JSR-105 APIs for XML Digital
> signature.
>
> I'm just about to create a beta version, so any feedback you can give
> me would be great. I'm open to some API tweaks after 1.6.0 goes out
> for the first few versions, in case any changes I've made cause
> serious problems for Rampart, or other third-party libraries.
>
> Colm.
>
> On Mon, Feb 28, 2011 at 4:37 PM, Thilina Mahesh Buddhika
> <th...@gmail.com> wrote:
> > Hi Colm,
> > Sorry for the late reply.
> > Kudos for your effort in bringing WSS4J 1.6 to this level.
> > We will start moving Rampart trunk to WSS4J 1.6 soon. We will be using
> WSS4J
> > 1.5.11 release for the upcoming Rampart 1.6 release.
> > Thanks,
> > Thilina
> >
> > On Mon, Feb 14, 2011 at 5:15 PM, Colm O hEigeartaigh <
> coheigea@apache.org>
> > wrote:
> >>
> >> All,
> >>
> >> I have created an "unofficial" WSS4J 1.6-alpha release. I was going to
> >> call a vote and push it to Maven Central as an "alpha" release, but I
> >> have decided to wait until the beta before doing this. The
> >> distribution is available here:
> >>
> >> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/dist/
> >>
> >> and the Maven artifacts are available here:
> >>
> >> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/maven/
> >>
> >> Please download and play around with it etc. All the usual caveats
> >> apply - it is an alpha version only, *not* suitable for production in
> >> any way, and the APIs are subject to change. *Now* is your chance to
> >> object to any changes that have been made, or to suggest alterations,
> >> tweaks, etc.
> >>
> >> The 1.6 release will *not* be backwards compatible with 1.5.x, and so
> >> some work will be required for third-party projects to upgrade to
> >> WSS4J 1.6. Rampart devs in particular should take note - please do not
> >> raise objections in a months time when I call a vote, now is the time.
> >> I've just merged a CXF branch that upgraded from WSS4J 1.5.x -> 1.6 to
> >> trunk.
> >>
> >> A rough timeline for this release is as follows:
> >>
> >> 11 Feb - alpha release
> >> 25 Feb - beta release
> >> 4 Mar - RC
> >> 11 Mar - Vote
> >>
> >> 91 issues have been closed or resolved for 1.6 (please see JIRA for
> >> more details). 6 issues remain to be fixed at this point.
> >>
> >> Colm.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: dev-help@ws.apache.org
> >>
> >
> >
> >
> > --
> > Thilina Mahesh Buddhika
> > http://blog.thilinamb.com
> >
>
--
Thilina Mahesh Buddhika
http://blog.thilinamb.com
Re: [ATTN] WSS4J 1.6-alpha distribution
Posted by Thilina Mahesh Buddhika <th...@gmail.com>.
Thanks Colm.
We are planning to doing some cleanup work on Rampart trunk while moving to
WSS4J 1.6 .
Also there will be one or two point releases based on 1_6 branch, for which
we can use WSS4J 1.5.11.
So we have some time to fix and stabilize Rampart trunk on WSS4J 1.6.
Thanks,
Thilina
On Mon, Feb 28, 2011 at 10:24 PM, Colm O hEigeartaigh
<co...@apache.org>wrote:
> Thanks! Feel free to ask me any questions in terms of upgrading
> Rampart to use WSS4J 1.6. You will see quite a lot of compilation
> errors, but most are fairly obvious. There are some slightly tricky
> changes in relation to code which calls WSSecSignature, which was
> necessitated by the move to use the JSR-105 APIs for XML Digital
> signature.
>
> I'm just about to create a beta version, so any feedback you can give
> me would be great. I'm open to some API tweaks after 1.6.0 goes out
> for the first few versions, in case any changes I've made cause
> serious problems for Rampart, or other third-party libraries.
>
> Colm.
>
> On Mon, Feb 28, 2011 at 4:37 PM, Thilina Mahesh Buddhika
> <th...@gmail.com> wrote:
> > Hi Colm,
> > Sorry for the late reply.
> > Kudos for your effort in bringing WSS4J 1.6 to this level.
> > We will start moving Rampart trunk to WSS4J 1.6 soon. We will be using
> WSS4J
> > 1.5.11 release for the upcoming Rampart 1.6 release.
> > Thanks,
> > Thilina
> >
> > On Mon, Feb 14, 2011 at 5:15 PM, Colm O hEigeartaigh <
> coheigea@apache.org>
> > wrote:
> >>
> >> All,
> >>
> >> I have created an "unofficial" WSS4J 1.6-alpha release. I was going to
> >> call a vote and push it to Maven Central as an "alpha" release, but I
> >> have decided to wait until the beta before doing this. The
> >> distribution is available here:
> >>
> >> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/dist/
> >>
> >> and the Maven artifacts are available here:
> >>
> >> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/maven/
> >>
> >> Please download and play around with it etc. All the usual caveats
> >> apply - it is an alpha version only, *not* suitable for production in
> >> any way, and the APIs are subject to change. *Now* is your chance to
> >> object to any changes that have been made, or to suggest alterations,
> >> tweaks, etc.
> >>
> >> The 1.6 release will *not* be backwards compatible with 1.5.x, and so
> >> some work will be required for third-party projects to upgrade to
> >> WSS4J 1.6. Rampart devs in particular should take note - please do not
> >> raise objections in a months time when I call a vote, now is the time.
> >> I've just merged a CXF branch that upgraded from WSS4J 1.5.x -> 1.6 to
> >> trunk.
> >>
> >> A rough timeline for this release is as follows:
> >>
> >> 11 Feb - alpha release
> >> 25 Feb - beta release
> >> 4 Mar - RC
> >> 11 Mar - Vote
> >>
> >> 91 issues have been closed or resolved for 1.6 (please see JIRA for
> >> more details). 6 issues remain to be fixed at this point.
> >>
> >> Colm.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: dev-help@ws.apache.org
> >>
> >
> >
> >
> > --
> > Thilina Mahesh Buddhika
> > http://blog.thilinamb.com
> >
>
--
Thilina Mahesh Buddhika
http://blog.thilinamb.com
Re: [ATTN] WSS4J 1.6-alpha distribution
Posted by Colm O hEigeartaigh <co...@apache.org>.
Thanks! Feel free to ask me any questions in terms of upgrading
Rampart to use WSS4J 1.6. You will see quite a lot of compilation
errors, but most are fairly obvious. There are some slightly tricky
changes in relation to code which calls WSSecSignature, which was
necessitated by the move to use the JSR-105 APIs for XML Digital
signature.
I'm just about to create a beta version, so any feedback you can give
me would be great. I'm open to some API tweaks after 1.6.0 goes out
for the first few versions, in case any changes I've made cause
serious problems for Rampart, or other third-party libraries.
Colm.
On Mon, Feb 28, 2011 at 4:37 PM, Thilina Mahesh Buddhika
<th...@gmail.com> wrote:
> Hi Colm,
> Sorry for the late reply.
> Kudos for your effort in bringing WSS4J 1.6 to this level.
> We will start moving Rampart trunk to WSS4J 1.6 soon. We will be using WSS4J
> 1.5.11 release for the upcoming Rampart 1.6 release.
> Thanks,
> Thilina
>
> On Mon, Feb 14, 2011 at 5:15 PM, Colm O hEigeartaigh <co...@apache.org>
> wrote:
>>
>> All,
>>
>> I have created an "unofficial" WSS4J 1.6-alpha release. I was going to
>> call a vote and push it to Maven Central as an "alpha" release, but I
>> have decided to wait until the beta before doing this. The
>> distribution is available here:
>>
>> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/dist/
>>
>> and the Maven artifacts are available here:
>>
>> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/maven/
>>
>> Please download and play around with it etc. All the usual caveats
>> apply - it is an alpha version only, *not* suitable for production in
>> any way, and the APIs are subject to change. *Now* is your chance to
>> object to any changes that have been made, or to suggest alterations,
>> tweaks, etc.
>>
>> The 1.6 release will *not* be backwards compatible with 1.5.x, and so
>> some work will be required for third-party projects to upgrade to
>> WSS4J 1.6. Rampart devs in particular should take note - please do not
>> raise objections in a months time when I call a vote, now is the time.
>> I've just merged a CXF branch that upgraded from WSS4J 1.5.x -> 1.6 to
>> trunk.
>>
>> A rough timeline for this release is as follows:
>>
>> 11 Feb - alpha release
>> 25 Feb - beta release
>> 4 Mar - RC
>> 11 Mar - Vote
>>
>> 91 issues have been closed or resolved for 1.6 (please see JIRA for
>> more details). 6 issues remain to be fixed at this point.
>>
>> Colm.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: dev-help@ws.apache.org
>>
>
>
>
> --
> Thilina Mahesh Buddhika
> http://blog.thilinamb.com
>
Re: [ATTN] WSS4J 1.6-alpha distribution
Posted by Colm O hEigeartaigh <co...@apache.org>.
Thanks! Feel free to ask me any questions in terms of upgrading
Rampart to use WSS4J 1.6. You will see quite a lot of compilation
errors, but most are fairly obvious. There are some slightly tricky
changes in relation to code which calls WSSecSignature, which was
necessitated by the move to use the JSR-105 APIs for XML Digital
signature.
I'm just about to create a beta version, so any feedback you can give
me would be great. I'm open to some API tweaks after 1.6.0 goes out
for the first few versions, in case any changes I've made cause
serious problems for Rampart, or other third-party libraries.
Colm.
On Mon, Feb 28, 2011 at 4:37 PM, Thilina Mahesh Buddhika
<th...@gmail.com> wrote:
> Hi Colm,
> Sorry for the late reply.
> Kudos for your effort in bringing WSS4J 1.6 to this level.
> We will start moving Rampart trunk to WSS4J 1.6 soon. We will be using WSS4J
> 1.5.11 release for the upcoming Rampart 1.6 release.
> Thanks,
> Thilina
>
> On Mon, Feb 14, 2011 at 5:15 PM, Colm O hEigeartaigh <co...@apache.org>
> wrote:
>>
>> All,
>>
>> I have created an "unofficial" WSS4J 1.6-alpha release. I was going to
>> call a vote and push it to Maven Central as an "alpha" release, but I
>> have decided to wait until the beta before doing this. The
>> distribution is available here:
>>
>> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/dist/
>>
>> and the Maven artifacts are available here:
>>
>> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/maven/
>>
>> Please download and play around with it etc. All the usual caveats
>> apply - it is an alpha version only, *not* suitable for production in
>> any way, and the APIs are subject to change. *Now* is your chance to
>> object to any changes that have been made, or to suggest alterations,
>> tweaks, etc.
>>
>> The 1.6 release will *not* be backwards compatible with 1.5.x, and so
>> some work will be required for third-party projects to upgrade to
>> WSS4J 1.6. Rampart devs in particular should take note - please do not
>> raise objections in a months time when I call a vote, now is the time.
>> I've just merged a CXF branch that upgraded from WSS4J 1.5.x -> 1.6 to
>> trunk.
>>
>> A rough timeline for this release is as follows:
>>
>> 11 Feb - alpha release
>> 25 Feb - beta release
>> 4 Mar - RC
>> 11 Mar - Vote
>>
>> 91 issues have been closed or resolved for 1.6 (please see JIRA for
>> more details). 6 issues remain to be fixed at this point.
>>
>> Colm.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: dev-help@ws.apache.org
>>
>
>
>
> --
> Thilina Mahesh Buddhika
> http://blog.thilinamb.com
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
Re: [ATTN] WSS4J 1.6-alpha distribution
Posted by Thilina Mahesh Buddhika <th...@gmail.com>.
Hi Colm,
Sorry for the late reply.
Kudos for your effort in bringing WSS4J 1.6 to this level.
We will start moving Rampart trunk to WSS4J 1.6 soon. We will be using WSS4J
1.5.11 release for the upcoming Rampart 1.6 release.
Thanks,
Thilina
On Mon, Feb 14, 2011 at 5:15 PM, Colm O hEigeartaigh <co...@apache.org>wrote:
> All,
>
> I have created an "unofficial" WSS4J 1.6-alpha release. I was going to
> call a vote and push it to Maven Central as an "alpha" release, but I
> have decided to wait until the beta before doing this. The
> distribution is available here:
>
> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/dist/
>
> and the Maven artifacts are available here:
>
> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/maven/
>
> Please download and play around with it etc. All the usual caveats
> apply - it is an alpha version only, *not* suitable for production in
> any way, and the APIs are subject to change. *Now* is your chance to
> object to any changes that have been made, or to suggest alterations,
> tweaks, etc.
>
> The 1.6 release will *not* be backwards compatible with 1.5.x, and so
> some work will be required for third-party projects to upgrade to
> WSS4J 1.6. Rampart devs in particular should take note - please do not
> raise objections in a months time when I call a vote, now is the time.
> I've just merged a CXF branch that upgraded from WSS4J 1.5.x -> 1.6 to
> trunk.
>
> A rough timeline for this release is as follows:
>
> 11 Feb - alpha release
> 25 Feb - beta release
> 4 Mar - RC
> 11 Mar - Vote
>
> 91 issues have been closed or resolved for 1.6 (please see JIRA for
> more details). 6 issues remain to be fixed at this point.
>
> Colm.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
>
--
Thilina Mahesh Buddhika
http://blog.thilinamb.com
Re: [ATTN] WSS4J 1.6-alpha distribution
Posted by Thilina Mahesh Buddhika <th...@gmail.com>.
Hi Colm,
Sorry for the late reply.
Kudos for your effort in bringing WSS4J 1.6 to this level.
We will start moving Rampart trunk to WSS4J 1.6 soon. We will be using WSS4J
1.5.11 release for the upcoming Rampart 1.6 release.
Thanks,
Thilina
On Mon, Feb 14, 2011 at 5:15 PM, Colm O hEigeartaigh <co...@apache.org>wrote:
> All,
>
> I have created an "unofficial" WSS4J 1.6-alpha release. I was going to
> call a vote and push it to Maven Central as an "alpha" release, but I
> have decided to wait until the beta before doing this. The
> distribution is available here:
>
> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/dist/
>
> and the Maven artifacts are available here:
>
> http://people.apache.org/~coheigea/stage/wss4j/1.6.0-alpha/maven/
>
> Please download and play around with it etc. All the usual caveats
> apply - it is an alpha version only, *not* suitable for production in
> any way, and the APIs are subject to change. *Now* is your chance to
> object to any changes that have been made, or to suggest alterations,
> tweaks, etc.
>
> The 1.6 release will *not* be backwards compatible with 1.5.x, and so
> some work will be required for third-party projects to upgrade to
> WSS4J 1.6. Rampart devs in particular should take note - please do not
> raise objections in a months time when I call a vote, now is the time.
> I've just merged a CXF branch that upgraded from WSS4J 1.5.x -> 1.6 to
> trunk.
>
> A rough timeline for this release is as follows:
>
> 11 Feb - alpha release
> 25 Feb - beta release
> 4 Mar - RC
> 11 Mar - Vote
>
> 91 issues have been closed or resolved for 1.6 (please see JIRA for
> more details). 6 issues remain to be fixed at this point.
>
> Colm.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
>
--
Thilina Mahesh Buddhika
http://blog.thilinamb.com