Hi all, Please make sure add relative paths to the parents poms when you are adding a new component/feature/etc for 3.2.1, if the parent pom is not in the immediate parent directory. Otherwise online build with a clean repo doesn't work cos' it can't resolve the parent poms.
thanks and regards, On Fri, Jun 24, 2011 at 11:37 AM, Muhammed Shariq <[email protected]> wrote: > On Fri, Jun 24, 2011 at 11:21 AM, Afkham Azeez <[email protected]> wrote: > >> >> >> On Fri, Jun 24, 2011 at 10:57 AM, Muhammed Shariq <[email protected]>wrote: >> >>> >>> On Fri, Jun 24, 2011 at 8:45 AM, Ruchira Wageesha <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> When we add a 3.2.1 feature into 3.2.0 branch, we need to modify the >>>> feature root pom to build only those 3.2.1 features?? i.e. If I take the >>>> system-staticstics feature >>>> >>>> system-statistics/ >>>> ├── org.wso2.carbon.system.statistics.feature >>>> │ ├── 3.2.0 >>>> │ │ └── pom.xml >>>> │ └── 3.2.1 >>>> │ └── pom.xml >>>> ├── org.wso2.carbon.system.statistics.server.feature >>>> │ ├── 3.2.0 >>>> │ │ └── pom.xml >>>> │ └── 3.2.1 >>>> │ └── pom.xml >>>> ├── org.wso2.carbon.system.statistics.ui.feature >>>> │ └── 3.2.0 >>>> │ └── pom.xml >>>> └── pom.xml -- we need to update this pom's version to 3.2.1 and build >>>> only 3.2.1 features ??? >>>> >>> >>> Ideally we should not modify this pom, but while branching stratos/common >>> features we faced an issue. All the stratos component's versions were are >>> defined in this parent pom and the version was defined as ${pom.version}. So >>> at build time maven started searching the patched version of all dependent >>> components, to overcome this we created a patch version of the >>> common/feature parent and pointed this as the parent for the patched server >>> and aggregate feature. Hope my explanation was clear :) >>> >> >> Yes, we learned that the dependency versions should have been defined as >> carbon.platform.version, not POM version. In fact, thinking about it >> logically, using pom.version to define the version of a dependency is wrong. >> It is only a coincidence that the pom.version & carbon.platform.version >> happened to be the same value. Ideally, we should define separate versions >> for each and every component. >> > > +1 .. I'll fix this on trunk for the stratos common feature. > >> >> >>>> regards, >>>> Ruchira >>>> -- >>>> Ruchira Wageesha >>>> Software Engineer - WSO2 Inc. www.wso2.com >>>> >>>> Email: [email protected] Blog: [email protected] >>>> Mobile: +94771083017 >>>> >>>> Lean . Enterprise . Middleware >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
