It's always a best practice to execute 'mvn clean install' instead of 'mvn install'. When building the p2-profile, we create the p2-repo inside the target. So if we don't clean, it'll use the existing one. +1 for enforcing clean.
~Isuru On Tue, Jan 31, 2012 at 10:47 AM, Supun Malinga <[email protected]> wrote: > Hi devs, > > Shall we do $subject? > when we do mvn install, p2 repo generation is not working properly. > After I updated the axis version to 1.6.1.wso2v5 from 1.6.1.wso2v4, I > still got the 1.6.1.wso2v4 jar inside the core distribution. > And found the issue resolved after I builts the > core/p2-profile-generation/ with mvn *clean* install. > > thanks, > -- > 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 > > -- Isuru Suriarachchi Technical Lead & Product Manager, WSO2 Application Server WSO2 Inc. http://wso2.com email : [email protected] blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
