On Thu, Feb 11, 2010 at 5:23 PM, Sumedha Rubasinghe <[email protected]>wrote:
> > > On Thu, Feb 11, 2010 at 5:18 PM, Isuru Suriarachchi <[email protected]>wrote: > >> >> >> On Thu, Feb 11, 2010 at 5:03 PM, Sameera Jayasoma <[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). >>>> >>> >>> Yes. Copying the updated bundle is the best solution. >>> >> >> +1. What I also used to do is to build my component, replace '-' from '.' >> and copy it into the plugins folder of the product. It's far easier than >> building all those feature modules. :) >> > > > I am confused now. Then why is Saminda telling that this is not working? > Yes it should work. But this will not be the case all the time. If the bundle is cached the above solution will not work. Also p2 keeps some file information relating to the bundle. Not sure abt the implication of that. If you do get such a caching issue another way to solve it is to delete repository/components/configuration/org.eclipse.osgi/bundles folder (which is where the caches are created if they are being cached). Saminda > /sumedha > > >> >> Thanks, >> ~Isuru >> >> >>> >>> Thanks >>> Sameera >>> >>>> >>>> >>>> /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 >>> >>> >> >> _______________________________________________ >> 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
