Saminda Wijeratne wrote: > > > On Mon, Jan 4, 2010 at 7:38 AM, Ruwan Linton <[email protected] > <mailto:[email protected]>> wrote: > > Saminda Wijeratne wrote: > > > > > > On Mon, Jan 4, 2010 at 1:14 AM, Ruwan Linton <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > Saminda Wijeratne wrote: > > > Thanx ruwan. I was finally able to build couple of > components I > > > couldn't build before. > > > > > > the versioning is not limited to carbon versions. we use > alot of > > other > > > bundles in orbit/common and from apache trunk. Shall we > have them on > > > dependency management list in carbon-parent, > carbon-component-parent > > > pom without any duplication while carbon-parent being the > parent pom > > > of carbon-component-parent pom. > > Nope, the whole point of the new structure is to be able to > release > > individual components separately in which case the above doesn't > > apply. > > What we can do is to group the similar components like in > registry, > > governance, mashup and so on and declare the dependency > management on > > those root poms. I am not done with that, but after I am > done with > > that, > > all the bundles will be declared at the dependency > management sections > > of the respective component root poms. > > > If we have a single place like that for those non-carbon > > bundles, when > > > changing/upgrading the versions we wont have to go through > > hundreds of > > > poms when > > Even now if you are doing a bulk change, it is just one > place which is > > carbon-componets pom. > > > > That is the thing. Will it be only one place? For example currently > > axis2 is a dependent on following carbon components (so far as I've > > found). > > dashboard > > aar-services > > logging > > bam-data-publishers > > eventing > > endpoint-publisher > > javascript-stub-generator > > localentry > > soap-tracer > > sts > > xfer > > policy-builder > > registry > > pojo-services > > wsdl2code > > sequence-editor > > system-statistics > > scheduled-tasks > > cluster-mgt > > endpoint > > axis1-services > > js-services > > throttling > > synapse-config-admin > > component-manager > > spring > > proxy-admin > > ejb-services > > java2wsdl > > view-flows > > identity > > governance > > jar-services > > data-sources > > bam > > mex > > gauges > > module-mgt > > wsdlconverter > > jruby > > jaxws > > codegen > > javascript-hostobjects > > bpel > > If we have dependency management per individual component, then we > > need check all carbon-component root poms in order to update a > version > > of a single bundle. And this affects the p2 features as well > since all > > the bundles are refered there in which case it shall have to manage > > its own dependencies. Correct me if I'm wrong, but if a person wants > > to update axis2 version for a release/branch he/she will have to > > change close to 50 poms. > WRONG!!, please have a look at the way I have done that, you have to > just change the carbon component root pom. > > Lets take aar-services as an example, there you have a property > defined > axis2.wso2.version.aar-services which gets mapped to > axis2.wso2.version > at the build time which is declared at the components root pom. > > > If you already have the version as a property coming from the > components root pom why not just define it in the dependency > management rather than using a property. In that way no one needs to > know what is the property name for a particular maven artifact (which > will stop problems on spelling mistakes or redefining properties with > different names - trust me this can happen) and if the version is > different in the carbon component all it needs is to redefine the > dependency management for that bundle in that components pom. With that approach how do you release a given component????
Thanks, Ruwan > > Saminda > > > This way user has the flexibility to go with the framework's > axis2.wso2 > version or his/her own axis2.wso2 version for his/her component. > > I was unable to finish up these for all the components yet, once I am > done with it, it will be very clean. > > Thanks, > Ruwan > > > > Saminda > > > > > Any reason why carbon-component is not using the carbon-parent > > as the > > > parent pom? > > The whole point of the new structuring is to isolate the > carbon parent > > and the components, it is a basic maven fault to refer to a > parent > > outside of the current project. Maven2 uses parent first > property > > lookup > > where the carbon parent pom will always provide all the versions > > in that > > case, without being able to change the versions for only a > particular > > component. > > > > Thanks, > > Ruwan > > > > > > Saminda > > > > > > If we follow a pattern like this version for non-carbon > bundles only > > > has to be managed atmost 2 places > > > > > > On Sun, Jan 3, 2010 at 10:52 PM, Ruwan Linton > <[email protected] <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>> > > > <mailto:[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>>> wrote: > > > > > > Folks, > > > > > > It seems I am unable to finish up all the components > today, > > so you can > > > work on your components. Some components refer to carbon > > parent as the > > > parent while some others refer to carbon-components as the > > parent. > > > > > > It should be OK. Also, please note that the warnings are > > removed till > > > governance in the alphabetical order, excluding the > > governance. There > > > are some more cleanups in the rest of the components > that I > > have fixed > > > just to work with the carbon-components parent. > > > > > > I have used a methodology where it requires only a single > > version > > > change > > > to change the carbon version in the components, (provided > > that the > > > parent versions are fixed) yet keeping the ability to > easily > > use a > > > different carbon version within your component. To do > this I > > have used > > > the component prefix in the versions, which then gets > mapped > > to the > > > global version value in this particular case. > > > > > > I expect some help from the component authors on cleaning > > the poms. It > > > takes a bit of time, but once it is done it is a very > clean > > model and > > > also will make our life really easy when it comes to > releasing > > > individual components, also this will fasten the build > with the > > > introduction of the wso2 repositories. > > > > > > Hope nothing has broken :-) I tested ESB and it works just > > fine, with > > > the old permissions exception :-) which was there even > before. > > > > > > Thanks, > > > Ruwan > > > > > > Ruwan Linton wrote: > > > > An update: > > > > > > > > I am planning to comment out the modules in the carbon > > component > > > parent > > > > default profile and enable them as and when I > complete the > > > migration of > > > > the components. > > > > > > > > Please note that you could work on your own > component without > > > trying to > > > > build all components. > > > > > > > > I will try to minimize the maven warnings while in > the process > > > of migration. > > > > > > > > Thanks, > > > > Ruwan > > > > > > > > Ruwan Linton wrote: > > > > > > > >> Folks, > > > >> > > > >> I am planning to re-format the maven structure of the > > > carbon-components > > > >> trunk and add svn:ignores as appropriate. You > better not take > > > svn update > > > >> till I finish this off. > > > >> > > > >> I will let you know once I am done!, doing it > atomically is > > > extremely > > > >> difficult and that is why I had to send this mail. > > > >> > > > >> Thanks, > > > >> Ruwan > > > >> > > > >> > > > >> > > > > > > > > > > > > > > > > > > > > > -- > > > Ruwan Linton > > > Technical Lead & Product Manager; WSO2 ESB; > http://wso2.org/esb > > > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > > > email: [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > <mailto:[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>>; cell: +94 77 341 > 3097 > > > blog: http://blog.ruwan.org > > > > > > > > > > > > _______________________________________________ > > > Carbon-dev mailing list > > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > <mailto:[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>> > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Carbon-dev mailing list > > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > -- > > Ruwan Linton > > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > > email: [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>; cell: +94 77 341 3097 > > blog: http://blog.ruwan.org > > > > > > > > _______________________________________________ > > Carbon-dev mailing list > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Carbon-dev mailing list > > [email protected] <mailto:[email protected]> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: [email protected] <mailto:[email protected]>; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] <mailto:[email protected]> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > ------------------------------------------------------------------------ > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://blog.ruwan.org _______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
