Re: Axis2 1.6 release plan

Done! Ruwan On Tue, Feb 8, 2011 at 5:37 PM, Ruwan Linton wrote: > +1, will use it. > > Thanks, > Ruwan > > > On Tue, Feb 8, 2011 at 5:20 PM, Andreas Veithen > wrote: > >> Can you try to use maven-release-plugin (release:branch) to create the >> branch? That should automatically update all POM

Re: Axis2 1.6 release plan

+1, will use it. Thanks, Ruwan On Tue, Feb 8, 2011 at 5:20 PM, Andreas Veithen wrote: > Can you try to use maven-release-plugin (release:branch) to create the > branch? That should automatically update all POM files. Note that you > will have to activate the "everything" profile (maven -Peveryth

Re: Axis2 1.6 release plan

Can you try to use maven-release-plugin (release:branch) to create the branch? That should automatically update all POM files. Note that you will have to activate the "everything" profile (maven -Peverything) to make sure that the distribution module is also updated. Andreas On Tue, Feb 8, 2011 a

Re: Axis2 1.6 release plan

Thanks a lot Sagara. Then I guess the platform is set for the release. Let me create the branch for the release. Ruwan On Tue, Feb 8, 2011 at 4:00 PM, Sagara Gunathunga < sagara.gunathu...@gmail.com> wrote: > Hi Ruwan , > > You can expect Woden release within this week. > > Thanks ! > > > >

Re: Axis2 1.6 release plan

OK, I got it passing :-) I was using the Neethi version 2.0.3 not sure whether that is the cause, but I was able to run the build 2 times with 2.0.4 version successfully. Thanks, Ruwan On Tue, Feb 8, 2011 at 3:54 PM, Ruwan Linton wrote: > +1, I was also checking the neethi release with the Axis

Re: Axis2 1.6 release plan

Hi Ruwan , You can expect Woden release within this week. Thanks ! On Tue, Feb 8, 2011 at 3:54 PM, Ruwan Linton wrote: > +1, I was also checking the neethi release with the Axis2 trunk, but I got > some test failures on the integration module, which doesn't seem to be > related to neethi.

Re: Axis2 1.6 release plan

+1, I was also checking the neethi release with the Axis2 trunk, but I got some test failures on the integration module, which doesn't seem to be related to neethi. I am verifying the build again. Once it is done lets create the branch and move ahead for the release. BTW: Sagara what is the statu

Re: Axis2 1.6 release plan

+1 On Feb 7, 2011 12:28 PM, "Ruwan Linton" wrote: > What I would suggest is to do the 1.6 release without the JAX-WS TCK > compatibility, if there are lot to be fixed. This is because we have enough > fixes on the trunk to do a release. May be we can target a major release > like 2.0 with the JAX-

Re: Axis2 1.6 release plan

The trunk seems to build just fine with Neethi 2.0.4. This confirms Dan's (and also my own) finding that there have been no significant changes on the Neethi trunk since the last release. On the other hand, Dan's recent changes broke integration with the Axis2 trunk. Probably nobody noticed that b

Re: Axis2 1.6 release plan

I agree with Ruwan. Instead of further increasing the scope of Axis2 1.6, just get this thing out and make sure that we can easily do maintenance releases. I think that with the 1.5.x releases, I've proven that it is perfectly possible to have a release every 2-3 months. Andreas On Mon, Feb 7, 20

Re: Axis2 1.6 release plan

On Feb 3, 2011, at 11:21 PM, Sanjiva Weerawarana wrote: > What's the verdict on this? I don't see the point of rushing out 1.6 without > passing the TCK .. having full JAX-WS support would (finally) be a major > milestone! From the perspective of an Axis2 consumer (i.e. Geornimo), I'd agree...

Re: Axis2 1.6 release plan

Also the AXIOM release is in-flight and we better close of the complete cycle with compatible releases from all the related projects, which includes, Woden, Neethi, Axis2, Rampart, Sandesha2 and so forth. Thanks, Ruwan On Mon, Feb 7, 2011 at 12:28 PM, Ruwan Linton wrote: > What I would suggest i

Re: Axis2 1.6 release plan

What I would suggest is to do the 1.6 release without the JAX-WS TCK compatibility, if there are lot to be fixed. This is because we have enough fixes on the trunk to do a release. May be we can target a major release like 2.0 with the JAX-WS support completed with the TCK running without any issue

Re: Axis2 1.6 release plan

When I run TCK for last time around half of test cases were failed. I didn't make any configuration change or had no time to investigate about failing test cases , with some modifications we may improve the pass rate. But I also believe it will take much more time to pass complete TCK. BTW rece

Re: Axis2 1.6 release plan

On Fri, Feb 4, 2011 at 9:51 AM, Sanjiva Weerawarana wrote: > What's the verdict on this? I don't see the point of rushing out 1.6 > without passing the TCK .. having full JAX-WS support would (finally) be a > major milestone! > We've got few more JAX-WS related issues to be addressed and after th

Re: Axis2 1.6 release plan

What's the verdict on this? I don't see the point of rushing out 1.6 without passing the TCK .. having full JAX-WS support would (finally) be a major milestone! Sanjiva. On Wed, Jan 26, 2011 at 7:16 AM, Ruwan Linton wrote: > I will evaluate this effort and get back to the list, to be frank I don

Re: Axis2 1.6 release plan

I will evaluate this effort and get back to the list, to be frank I don't have a clear idea as of now on how much work this adds to the release and the time frame either. Ruwan On Tue, Jan 25, 2011 at 10:10 PM, Sanjiva Weerawarana wrote: > Ruwan what about the JAX-WS TCK? It seems to me it woul

Re: Axis2 1.6 release plan

What we have agreed is to create a separate distro with all bundled together and release that inline with Axis2 core, as moving the rampart and sandesha modules into axis2 required a bit of SVN refactoring too. I think we should be able to create that distro. Just a matter of writing an assembly, b

Re: Axis2 1.6 release plan

+1, for getting JAX-WS TCK (if we have enough man power). Deepal > Ruwan what about the JAX-WS TCK? It seems to me it would be better to > release with that passed? I have no idea what that implies in terms of > effort and time .. > > Sanjiva. > > On Tue, Jan 25, 2011 at 7:13 AM, Ruwan Linton

Re: Axis2 1.6 release plan

Ruwan what about the JAX-WS TCK? It seems to me it would be better to release with that passed? I have no idea what that implies in terms of effort and time .. Sanjiva. On Tue, Jan 25, 2011 at 7:13 AM, Ruwan Linton wrote: > Folks, > > After a set of hackathons on Axis2 trunk it is sort of at a s

Re: Axis2 1.6 release plan

I thought we agreed to basically making them be one release- with the mars being in the same dist even? Sanjiva. On Tue, Jan 25, 2011 at 1:48 PM, Samisa Abeysinghe < samisa.abeysin...@gmail.com> wrote: > May be we need to think about down-stream project release plans as well. > > It would be ide

Re: Axis2 1.6 release plan

Thanks Thilina, who is going to work on the Sandesha2 release? Ruwan On Tue, Jan 25, 2011 at 4:54 PM, Thilina Mahesh Buddhika < thilin...@gmail.com> wrote: > I will start on working Rampart 1.6 release. > > Thanks, > Thilina > > Thilina Mahesh Buddhika > http://blog.thilinamb.com > > > > On Tue,

Re: Axis2 1.6 release plan

Yeah, but for the time being they are separate modules, so we need to do separate releases in sync this time. Ruwan On Tue, Jan 25, 2011 at 7:00 PM, Deepal jayasinghe wrote: > Indeed, all should go together. > > Deepal > > May be we need to think about down-stream project release plans as well.

Re: Axis2 1.6 release plan

Indeed, all should go together. Deepal > May be we need to think about down-stream project release plans as well. > > It would be ideal to have Rampart and Sandesha2 also released with > Axis2 1.6 > > Thanks, > Samisa... > > On Tue, Jan 25, 2011 at 1:20 PM, Ruwan Linton

Re: Axis2 1.6 release plan

I will start on working Rampart 1.6 release. Thanks, Thilina Thilina Mahesh Buddhika http://blog.thilinamb.com On Tue, Jan 25, 2011 at 2:48 PM, Ruwan Linton wrote: > +1, any volunteers for those releases?? > > Ruwan > > > On Tue, Jan 25, 2011 at 1:48 PM, Samisa Abeysinghe < > samisa.abeysin...

Re: Axis2 1.6 release plan

Thanks Sagara, that helps a lot. Neethi doesn't seem to have much activity around it, and I assume that could be released without much issue as well, I will see what are the changes after the previous release and will try to see if we can go with the previous version of neethi, but not sure about

Re: Axis2 1.6 release plan

I have configured Maven release plug in locally for Woden trunk and had a successful dry run in last December, Woden M9 release can be start any time. If Axis2 1.6 plan to go with Axiom 1.2.11 version it's better to use same Axiom version for Woden too. I will start Woden release just after the Axo

Re: Axis2 1.6 release plan

+1, any volunteers for those releases?? Ruwan On Tue, Jan 25, 2011 at 1:48 PM, Samisa Abeysinghe < samisa.abeysin...@gmail.com> wrote: > May be we need to think about down-stream project release plans as well. > > It would be ideal to have Rampart and Sandesha2 also released with Axis2 > 1.6 > >

Re: Axis2 1.6 release plan

May be we need to think about down-stream project release plans as well. It would be ideal to have Rampart and Sandesha2 also released with Axis2 1.6 Thanks, Samisa... On Tue, Jan 25, 2011 at 1:20 PM, Ruwan Linton wrote: > Thanks Andreas for volunteering for the Axiom release. > > I will have a

Re: Axis2 1.6 release plan

Thanks Andreas for volunteering for the Axiom release. I will have a look at Neethi and Wooden state. Thanks, Ruwan On Tue, Jan 25, 2011 at 12:44 PM, Andreas Veithen wrote: > We need to figure out what releases we need from upstream projects. > Right now the trunk has the following snapshot de

Re: Axis2 1.6 release plan

We need to figure out what releases we need from upstream projects. Right now the trunk has the following snapshot dependencies: 1.2.11-SNAPSHOT 3.0.0-SNAPSHOT 1.0-SNAPSHOT We definitely need a new Axiom release, but this is not a problem because the code is in a releasabl