Anjana, Are you going to do the release using this approach... ? If yes I think that is wrong because when we do the actual release after you do the ds release, dataservices 2.0.3 components will be replaced in the repository and something wrong can happen when someone build dataservices(2.0.2) after the carbon 2.0.3 release.
Lahiru On Thu, Nov 19, 2009 at 5:51 PM, Anjana Fernando <[email protected]> wrote: > Hello, > > We are creating a new directory in the data-services carbon component, > which represents a new version as described by the new branching > strategy. The new component's version is selected as "2.0.3", and it's > parents pom has a reference to the carbon-core parents pom with the > given version "2.0.2". > > So by this we are expecting the carbon 2.0.2 libraries to be used by > the new component. But in carbon-core, the versions are stated there > as "pom.version", which is expected to pick the version of its pom > (which is 2.0.2). But when we reference it from our component - which > has the version 2.0.3 - carbon-core parent treats its "pom.version" as > "2.0.3". So I'm suggesting to change the carbon-core parent pom to not > to use the property "pom.version", but to keep a single property > "wso2carbon.version" with the value "2.0.2" and use it in all the > places where the version is needed. Here I've attached a diff with the > changes I suggested. Hope for some feedback. > > Thanks, > Anjana. > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Lahiru Gunathilake Software Engineer - WSO2 Inc.
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
