To make sure that I didn't make any mistake while copying a bundle with a change to the product's plugins folder, I made it a habit to copy as "cp /home/senaka/carbon-trunk/components/registry/org.wso2.carbon.registry.ws.api/target/org.wso2.carbon.registry.ws.api-3.0.0-SNAPSHOT.jar ../repository/components/plugins/org.wso2.carbon.registry.ws.api-3.0.0.SNAPSHOT.jar" instead of "cp /home/senaka/carbon-trunk/components/registry/org.wso2.carbon.registry.ws.api/target/org.wso2.carbon.registry.ws.api-3.0.0-SNAPSHOT.jar ../repository/components/plugins/". It was a matter of typing org and hitting the tab key a few times, while typing a few characters so that I could reduce the number of matches returned on the console.
The gain here is that, I'll always certain that the bundle was properly copied, instead of having to verify it after having spent sometime (~20s) to start the server. HTH, Thanks, Senaka. On Thu, Feb 11, 2010 at 6:57 PM, Lahiru Gunathilake <[email protected]> wrote: > There are some jars we are not changing the name by putting a "." instead > of "-" which comes from carbon (core.installer,server,utils,xboot) , those > are usually on lib directory and just have to copy them. > > Lahiru > > > On Thu, Feb 11, 2010 at 5:55 PM, Saminda Wijeratne <[email protected]>wrote: > >> >> >> On Thu, Feb 11, 2010 at 4:59 PM, Sumedha Rubasinghe <[email protected]>wrote: >> >>> >>> >>> On Thu, Feb 11, 2010 at 4:43 PM, Saminda Wijeratne <[email protected]>wrote: >>> >>>> Unfortunately this may not be possible directly as we used to. >>> >>> >>> This is a major hit to the development time. >>> >>> >>> >>>> One reason is that once the product is run atleast once some of the >>>> classes in the bundles can be cached. >>>> One sure way to handle this is to rebuild the product in the manner >>>> depicted in the diagram below. >>>> >>>> >>>> >>>> for example if the change is of a carbon core bundle (eg: >>>> org.wso2.carbon.server.admin.ui) then you need to build everything that >>>> goes >>>> through the arrows upward until the product distribution. >>>> i.e. eg: >>>> build, org.wso2.carbon.server.admin.ui -> >>>> org.wso2.carbon.core.ui.feature -> carbon-p2-profile -> wso2esb-p2-profile >>>> -> esb distribution >>>> >>>> There might be shortcut solutions which would work in specific >>>> scenarios. Will update this thread with those also. >>>> >>> >>> >>> I have found out that org.wso2.carbon.ui bundle can be updated as we did >>> before. Just copy the bundle to plugins folder (you need to rename _SNAPSHOT >>> to .SNAPSHOT). >>> >> >> This may not be enough in some cases. eg: "synapse-commons-1.4.0-SNAPSHOT" >> should be renamed to "org.apache.synapse.synapse-commons-1.4.0.SNAPSHOT" >> >> Saminda >> >> >>> >>> >>> /sumedha >>> >>> >>> >>>> >>>> Regards, >>>> Saminda >>>> >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> _______________________________________________ >> 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 > > -- Senaka Fernando Software Engineer WSO2 Inc. E-mail: senaka AT wso2.com; Mobile: +94 77 322 1818 http://www.wso2.com/ - "Lean . Enterprise . Middleware"
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
