Well, even right now, One has to build the distribution module separately after building the axis2 project from the root pom. So in effect it is really a separate thing. I suggest we move the axis2 distribution into a separate subproject under Axis2. I really think that the Axis2 distro should have Rampart and Sandesha2 built into it. We can also decide on the transports that we need to add by default to this distro with this method.
WDYT? Ruwan On Wed, Dec 22, 2010 at 7:36 PM, Samisa Abeysinghe < [email protected]> wrote: > If it is too many logistics to build one pack, we can have separate packs > but release all three at the same time, at least few days apart > > Samisa... > > On Wed, Dec 22, 2010 at 6:12 PM, Andreas Veithen < > [email protected]> wrote: > >> This would require again changes to the project structure and/or to >> the build and release system. I'm not in principle against this, but >> the issue I see with this is the following: In 2009 we moved the >> transports into a separate project and in 2010 we migrated to a new >> TLP. All this required lots of changes and it took a long time to >> complete this (the TLP migration is still not entirely complete). If >> we change the project structure every year and every time it takes >> months to complete this, then we will never reach a stable situation. >> >> My counterproposal is to keep things as they are in terms of project >> structure, but continue to streamline the release processes. We can >> then move to a release early, release often policy (as is happening >> right now with the Axis2 1.5 branch) and also have simultaneous >> releases (as I did for Sandesha2 and Axis2). This would allow us to >> keep the flexibility to postpone the release of one of the subprojects >> if there are blocking issues. >> >> To summarize: I think that the real pain point is not that we have >> separate subprojects, but that the release cycles are too long. This >> can only be solved by making the release process easier, more >> predictable and well documented. >> >> Andreas >> >> On Wed, Dec 22, 2010 at 05:09, Ruwan Linton <[email protected]> >> wrote: >> > In the future how about bundling Rampart and Sandesha2 into the Axis2 >> > distribution itself? It is really part of Axis2 I guess. The recent >> > experience that I had with the Synapse release convinced me that Rampart >> and >> > Sandesha2 are really part of Axis2? Why do't we create a one single >> > distribution with Rampart and Sandesh2 when we release Axis2. >> > May be I am hijacking this thread, but I guess this thread is there also >> > because of the above issue of separately releasing the Rampart and >> > Sandesha2. >> > WDYT? >> > Thanks, >> > Ruwan >> > >> > On Wed, Dec 22, 2010 at 9:32 AM, Thilina Mahesh Buddhika >> > <[email protected]> wrote: >> >> >> >> On Wed, Dec 22, 2010 at 7:56 AM, Samisa Abeysinghe >> >> <[email protected]> wrote: >> >>> >> >>> We have fixed loads of Rampart issues yesterday and we will be able to >> >>> fix some more today as well. >> >>> >> >>> How about a release ASAP? I think users will benefit by having latest >> >>> rampart working with latest Axis2. >> >> >> >> +1. >> >> >> >> We can do this release based on the recently released WSS4J 1.5.10. >> >> >> >> Thanks, >> >> Thilina >> >> >> >>> >> >>> Samisa... >> >> >> > >> > >> > >> > -- >> > Ruwan Linton >> > Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb >> > WSO2 Inc.; http://wso2.org >> > >> > Lean . Enterprise . Middleware >> > >> > phone: +1 408 754 7388 ext 51789 >> > email: [email protected]; cell: +94 77 341 3097 >> > blog: http://blog.ruwan.org >> > linkedin: http://www.linkedin.com/in/ruwanlinton >> > google: http://www.google.com/profiles/ruwan.linton >> > tweet: http://twitter.com/ruwanlinton >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > -- Ruwan Linton Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: [email protected]; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton google: http://www.google.com/profiles/ruwan.linton tweet: http://twitter.com/ruwanlinton
