[jira] Commented: (AXIS2-4265) ModulePolicyExtension mixes buildtime and runtime

[ https://issues.apache.org/jira/browse/AXIS2-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927733#action_12927733 ] Dennis Sosnoski commented on AXIS2-4265: Until this is fixed, the "" line in the A

[jira] Commented: (AXIS2-4855) Support new SOAP/JMS binding ID

[ https://issues.apache.org/jira/browse/AXIS2-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927572#action_12927572 ] Jeff Barrett commented on AXIS2-4855: - The patch causes a JAX-WS integration test to fa

Hudson build became unstable: axis2-transports-trunk #213

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

Hudson build became unstable: axis2-transpor ts-trunk » Apache Axis2 - Transport - Sms #213

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apac

Re: Preparation of the Axis2 1.5.3 release

On Tue, Nov 2, 2010 at 7:42 PM, Andreas Veithen wrote: > On Tue, Nov 2, 2010 at 14:49, Samisa Abeysinghe > wrote: > > Why not we just pull off 1.6 as it is? > > > > What do we lack, a release manager, or fix cycles? > > Samisa... > > The insight that in order to make progress one should let the p

Re: Preparation of the Axis2 1.5.3 release

On Tue, Nov 2, 2010 at 14:49, Samisa Abeysinghe wrote: > Why not we just pull off 1.6 as it is? > > What do we lack, a release manager, or fix cycles? > Samisa... The insight that in order to make progress one should let the people who are willing to make progress and know what needs to be done,

Re: Preparation of the Axis2 1.5.3 release

Why not we just pull off 1.6 as it is? What do we lack, a release manager, or fix cycles? Samisa... On Tue, Nov 2, 2010 at 6:13 PM, Andreas Veithen wrote: > All, > > Considering that > > * progress on the 1.6 release has stalled because of a disagreement > [1] on the right strategy and the fact

Preparation of the Axis2 1.5.3 release

All, Considering that * progress on the 1.6 release has stalled because of a disagreement [1] on the right strategy and the fact that nobody volunteers to make progress using the strategy supported by the majority of the people who expressed their opinion; * there are still open issues with the H

[jira] Resolved: (AXIS2-4870) mex-x.y.z-impl.jar not included in standard binary distribution

[ https://issues.apache.org/jira/browse/AXIS2-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4870. Resolution: Fixed Fix Version/s: 1.5.3 1.6 Fixed on the trunk (r1

[jira] Created: (AXIS2-4870) mex-x.y.z-impl.jar not included in standard binary distribution

mex-x.y.z-impl.jar not included in standard binary distribution --- Key: AXIS2-4870 URL: https://issues.apache.org/jira/browse/AXIS2-4870 Project: Axis2 Issue Type: Bug Affects

Re: Moving to website to the new CMS?

I followed the discussion that gave birth to that CMS. I think it represents a progress for non-project sites (such as www and community, but I'm not convinced that it is a good solution for project sites. The main points are: * It's SVN based. In contrast to Confluence, this means that non-commit