Re: [Carbon-dev] redefining dependency version under component/feature modules

2012-01-29 Thread Amila Maha Arachchi
These are the versions repeatedly defined in the componets/pom.xml -4.0.0-SNAPSHOT -1.6.1.wso2v5 -1.6.1-wso2v5 -[1.6.1.wso2v1, 1.7.0) -[1.2.11.wso2v1, 1.3.0) -2.1.0-wso2v3 -1.2.11.wso2v1 -1.6.2.wso2v2 - 1.0.1.wso2v1 -1.6.1-wso

Re: [Carbon-dev] redefining dependency version under component/feature modules

2012-01-29 Thread Srinath Perera
Jaggery guys please fix Supun .. could you run a grep for >[0-9.]*.wso2*< and other similar patterns to find other places we are not using platform pom version and send a report? We should do this time to time On Mon, Jan 30, 2012 at 1:50 AM, Supun Malinga wrote: > Hi devs, > > Please always

[Carbon-dev] redefining dependency version under component/feature modules

2012-01-29 Thread Supun Malinga
Hi devs, Please always try to use the platform pom defined versions. Below is only some example of $subject. There is no need of redefining these properties since its already defined in parent poms. ./components/jaggery/pom.xml: 1.6.1.wso2v4 ./components/hostobjects/pom.xml: 1.6.1.wso2v4 ./feat