Hi Tharindu, +1 That's the correct way to do. But we tend to simply change the versions manually..
thanks, On Wed, Jan 30, 2013 at 10:36 AM, Tharindu Mathew <[email protected]> wrote: > Hi, > > I have seen that the maven property project.version has been used by many > in poms. I believe it's a better practice to define the version in > properties like <carbon.platform.patch.version.407> > > What happens otherwise is when a new version of the component or feature > is made, it will eventually break the build. This is because some of the > dependencies will not have the new version of the component. In the case of > the feature, sometimes you will not know you broke the build until a > product's p2-profile-gen is built. > > WDYT? > > -- > Regards, > > Tharindu Mathew > > Associate Technical Lead, WSO2 BAM > Member - Data Mgmt. Committee > > blog: http://tharindumathew.com/ > M: +94777759908 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
