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. 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 branching. Any reason why carbon-component is not using the carbon-parent as the parent pom? 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]> 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]; 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 >
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
