Hi Sameera, On Thu, Feb 24, 2011 at 3:34 PM, Sameera Jayasoma <same...@wso2.com> wrote:
> > > On Thu, Feb 24, 2011 at 3:22 PM, Senaka Fernando <sen...@wso2.com> wrote: > >> >> >> On Thu, Feb 24, 2011 at 12:34 PM, Sameera Jayasoma <same...@wso2.com>wrote: >> >>> Hi Folks, >>> >>> We came up with following action items for the Carbon trunk. >>> >>> >>> - Use Maven dependency exclusions properly to exclude unused >>> dependencies. This will significantly improve build time. But this >>> needs to >>> be done with extra care. >>> >>> >>> - All the Maven plugins used across the Carbon platform need to be >>> specified the PluginManagement section in carbon-platform pom. This pom >>> is >>> these grad-parent of all the pom files in the Carbon platform. >>> >>> >>> - A DependencyManagement section should be introduced at core, >>> components, features and individual product/services level. This would >>> make >>> our lives easier when we apply Maven exclusions. >>> >>> >>> - Use Maven properties properly and specify dependecy versions using >>> these properties. Versions of all most-widely used dependencies should be >>> defined in the carbon-platform pom. This why, when there is a version >>> change, we got only a single place to change. >>> >>> >>> - Commit build.sh/bat scripts to Carbon trunk. This way, we can >>> achive one-checkout one-build. >>> >>> >>> - Use WSO2 Nexus repository in Carbon trunk. We had issues in >>> wsdl-validator and shinding when we use Nexus repository in Carbon 3.1.0 >>> branch. We need to fix this also. >>> >>> >>> - Fix the repository blacklist issue which occurs in generating API >>> docs(Maven java-doc plugin). This happens nealy 5 times during a complete >>> build and the build hangs for about 45min each time. >>> >>> I fixed the above on the branch. Does this solve the issue? If so, I'll >> add the same to trunk. >> >> Will also write some blog post around this. No one from the Maven end ever >> explained how to fix this issue, despite explaining that this is an issue, >> and had to do a trial and error approach yesterday, to figure this out, :-). >> > > Excellent. It works like a charm :). Please fix this in the trunk also. > Btw, carbon-core/distribution/ should also be fixed in both branch and > trunk. > Fixed on trunk. For carbon-core/distribution, as discussed offline, please do list the reports that are required to be generated by the WSO2 Carbon documentation distribution. Once I know the list, I can fix the issue in report generation. Thanks, Senaka. > > Thanks > Sameera > >> >> Thanks, >> Senaka. >> >> >>> There can be exceptional situations though. >>> >>> We can start this effort from tomorrow it self. >>> >>> Thanks, >>> Sameera >>> >>> >>> On Wed, Feb 23, 2011 at 5:33 PM, Sameera Jayasoma <same...@wso2.com>wrote: >>> >>>> >>>> >>>> On Wed, Feb 23, 2011 at 4:58 PM, Isuru Suriarachchi <is...@wso2.com>wrote: >>>> >>>>> >>>>> >>>>> On Wed, Feb 23, 2011 at 7:33 AM, Sumedha Rubasinghe >>>>> <sume...@wso2.com>wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Feb 23, 2011 at 7:08 AM, Samisa Abeysinghe >>>>>> <sam...@wso2.com>wrote: >>>>>> >>>>>>> So are we going to do this on trunk? If so when? >>>>>>> >>>>>>> Do we not how to do it right? >>>>>>> >>>>>> >>>>>> We do know how to do it. But AFAIK that knowledge is only within few >>>>>> of us. >>>>>> Most importantly everyone should understand, >>>>>> -Why we should do it? >>>>>> -How we do it? >>>>>> -How to do it when introducing a new external dependency? >>>>>> >>>>>> But, as per the current trunk, lets gets 7-8 together and do it in one >>>>>> shot. >>>>>> Doing this right will introduce a significant improvement to our build >>>>>> time. Hence, we should do it as soon as we can allocate said number of >>>>>> engineers (more the quicker) for the task. Then we can update everyone >>>>>> else >>>>>> on above 3 topics. >>>>>> >>>>> >>>>> +1. We have to do this in hackathon mode. >>>>> >>>> >>>> Yes we must do this :). >>>> >>>> Sameera >>>> >>>> >>>>> >>>>> Thanks, >>>>> ~Isuru >>>>> >>>>> >>>>>> >>>>>> /sumedha >>>>>> >>>>>> >>>>>>> >>>>>>> ---------- Forwarded message ---------- >>>>>>> From: Sameera Jayasoma <same...@wso2.com> >>>>>>> Date: Tue, Feb 22, 2011 at 7:49 AM >>>>>>> Subject: Re: [Carbon-dev] Carbon 3.2.0 depending Axis2 1.6.x branch >>>>>>> To: Thilina Buddhika <thili...@wso2.com> >>>>>>> Cc: carbon-dev <carbon-dev@wso2.org> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Feb 22, 2011 at 2:11 AM, Thilina Buddhika <thili...@wso2.com >>>>>>> > wrote: >>>>>>> >>>>>>>> We were able to incorporate these changes to Carbon trunk. And I was >>>>>>>> able to build it until Carbon-Core with a fresh repo. >>>>>>>> >>>>>>>> A couple of issues encountered in Sandesha branch(Versions are not >>>>>>>> updated properly) and Savan trunk. I informed about this to the Axis >>>>>>>> list >>>>>>>> and hopefully we will be able to get it resolved within today. Savan >>>>>>>> seems >>>>>>>> to be depending on Sandesha trunk. So it should be branched off >>>>>>>> similar to >>>>>>>> transports (Will do it today). Until then you can apply the attached >>>>>>>> patches >>>>>>>> when building dependencies/sandesha and dependencies/savan. >>>>>>>> >>>>>>>> We will be depending on the Neethi orbit version released with >>>>>>>> Carbon 3.1.0 chunk2 (Neethi-2.0.4.wso2v2), so I have commented out >>>>>>>> Neethi >>>>>>>> from the default build profiles. >>>>>>>> >>>>>>>> I observed few places which have transitive dependencies to the >>>>>>>> Axiom trunk which need to be fixed. >>>>>>>> >>>>>>> >>>>>>> This needs to be fixed. We had similar issues while working on the >>>>>>> Carbon 3.1.0 branch. Lets fix these transitive dependencies in a >>>>>>> platform >>>>>>> wide manner using Maven dependency exclusions. >>>>>>> >>>>>>> Thanks >>>>>>> Sameera >>>>>>> >>>>>>>> >>>>>>>> We will make sure all the products and Stratos services can be built >>>>>>>> with a fresh repo with these modifications by end of the day. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Thilina >>>>>>>> >>>>>>>> On Mon, Feb 21, 2011 at 4:41 PM, Thilina Buddhika < >>>>>>>> thili...@wso2.com> wrote: >>>>>>>> >>>>>>>>> After having some offline discussions, we came up with the >>>>>>>>> following plan. >>>>>>>>> >>>>>>>>> - Modify the Axis2, Rampart and Sandesha svn externals to point to >>>>>>>>> corresponding Apache 1_6_x branches >>>>>>>>> >>>>>>>>> - Switching to Axiom 1.2.11 and WSS4J-1.5.11 released versions, >>>>>>>>> since Axis2 and Rampart 1_6_x branches are depending on these >>>>>>>>> versions. (So >>>>>>>>> these externals will be removed from the trunk) >>>>>>>>> >>>>>>>>> - Modifying the Orbit versions of Axiom and WSS4J to 1.2.11-wso2v1 >>>>>>>>> and 1.5.11-wso2v1 respectively to be consistent. (At the moment, they >>>>>>>>> are >>>>>>>>> 1.2.12-SNAPSHOT-wso2v1 and 1.5.12-SNAPSHOT-wso2v1) >>>>>>>>> >>>>>>>>> - Modifying the Synapse trunk to point to Axis2 1_6_x branch >>>>>>>>> instead of the trunk until we branch it for the release. (As per >>>>>>>>> Supun, we >>>>>>>>> can't branch at the moment, since some active development is going in >>>>>>>>> Synapse trunk) >>>>>>>>> >>>>>>>>> - Creating Carbon 3.2.0 branch and branching off form 'Transports' >>>>>>>>> trunk and making it dependent on Axis 1_6_x >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Thilina >>>>>>>>> >>>>>>>>> -- >>>>>>>> Thilina Buddhika >>>>>>>> Senior Software Engineer >>>>>>>> WSO2 Inc. ; http://wso2.com >>>>>>>> lean . enterprise . middleware >>>>>>>> >>>>>>>> phone : <%2B94%2077%2044%2088%20727> >>>>>>>> <%2B94%2077%2044%2088%20727><%2B94%2077%2044%2088%20727>+94 >>>>>>>> 77 44 88 727 >>>>>>>> blog : http://blog.thilinamb.com >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sameera Jayasoma >>>>>>> Technical Lead and Product Manager, WSO2 Carbon >>>>>>> >>>>>>> WSO2, Inc. (http://wso2.com) >>>>>>> email: same...@wso2.com >>>>>>> blog: http://tech.jayasoma.org >>>>>>> >>>>>>> Lean . Enterprise . Middleware >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Carbon-dev mailing list >>>>>>> Carbon-dev@wso2.org >>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>> >>>>>>> Thanks, >>>>>>> Samisa... >>>>>>> >>>>>>> Samisa Abeysinghe >>>>>>> VP Engineering >>>>>>> WSO2 Inc. >>>>>>> http://wso2.com >>>>>>> http://wso2.org >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Carbon-dev mailing list >>>>>>> Carbon-dev@wso2.org >>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Carbon-dev mailing list >>>>>> Carbon-dev@wso2.org >>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Isuru Suriarachchi >>>>> Technical Lead & Product Manager, WSO2 Application Server >>>>> >>>>> WSO2 Inc. http://wso2.com >>>>> email : is...@wso2.com >>>>> blog : http://isurues.wordpress.com/ >>>>> >>>>> lean . enterprise . middleware >>>>> >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> Carbon-dev@wso2.org >>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Sameera Jayasoma >>>> Technical Lead and Product Manager, WSO2 Carbon >>>> >>>> WSO2, Inc. (http://wso2.com) >>>> email: same...@wso2.com >>>> blog: http://tech.jayasoma.org >>>> >>>> Lean . Enterprise . Middleware >>>> >>> >>> >>> >>> -- >>> Sameera Jayasoma >>> Technical Lead and Product Manager, WSO2 Carbon >>> >>> WSO2, Inc. (http://wso2.com) >>> email: same...@wso2.com >>> blog: http://tech.jayasoma.org >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate Technical Lead; WSO2, Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://www.linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > > > -- > Sameera Jayasoma > Technical Lead and Product Manager, WSO2 Carbon > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://tech.jayasoma.org > > Lean . Enterprise . Middleware > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
