You dont have to patch jenkins war. Just copy the jars to build server Thanks & Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729
On Mon, Dec 15, 2014 at 10:37 PM, Danushka Fernando <[email protected]> wrote: > > @Rajeevan: Please apply this for the setup in 16.2. Its updated by the > merged code. Do these manually, restart the buildserver and test > > Thanks & Regards > Danushka Fernando > Software Engineer > WSO2 inc. http://wso2.com/ > Mobile : +94716332729 > > On Mon, Dec 15, 2014 at 8:37 PM, Mahesh Chinthaka <[email protected]> > wrote: >> >> Hi Danushka, >> >> This is how I used to patch while testing, >> >> 1). patch jenkins.war >> >> 2). copy following jars to location : buildserver/lib/runtime/jenkins >> >> org.wso2.carbon.appfactory.common-2.1.0.jar >> >> org.wso2.carbon.appfactory.core-2.1.0.jar >> >> org.wso2.carbon.appfactory.deployers-2.1.0.jar >> >> org.wso2.carbon.appfactory.repository.mgt.service-2.1.0.jar >> >> >> 3). copy following jars to location : >> buildserver/repository/components/dropins >> >> org.wso2.carbon.appfactory.common-2.1.0.jar >> >> org.wso2.carbon.appfactory.core-2.1.0.jar >> >> >> For the moment you can do above, and I'm working on avoiding copying jars >> to runtime/jenkins >> >> >> Thanks >> >> On Mon, Dec 15, 2014 at 8:30 PM, Danushka Fernando <[email protected]> >> wrote: >>> >>> Hi Mahesh >>> Please consider doing $subject. Current setup is failing due to this. >>> >>> Thanks & Regards >>> Danushka Fernando >>> Software Engineer >>> WSO2 inc. http://wso2.com/ >>> Mobile : +94716332729 >>> >> >> >> -- >> *Mahesh Chinthaka Vidanagama* | Software Engineer >> WSO2, Inc | lean. enterprise. middleware. >> #20, Palm Grove, Colombo 03, Sri Lanka >> Mobile: +94 71 63 63 083 | Work: +94 112 145 345 >> Email: [email protected] | Web: www.wso2.com >> >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
