On Sun, Jun 30, 2013 at 6:59 PM, Afkham Azeez <[email protected]> wrote:
> > > > On Sun, Jun 30, 2013 at 3:55 PM, Manoj Kumara <[email protected]> wrote: > >> Hi Devs, >> >> Currently if any change (revert patch or insert new patch) in the patches >> directory we are applying all the existing patches along with >> bundleBackupDir (patch0000) which is quite a large directory to the plugins >> directory. As I feel we can optimize this process even more and reduce >> server start-up time if only new patches has being added. >> >> >> - *If any patch revert :* no change in the current patch applying >> process. >> >> >> - *if only new patches has added* : we can only apply the newly added >> patches since previous patches are already exist in the plugins directory. >> >> We would need to see if the there are any changes in already applied patches.. if not we can do this. thanks, > >> >> > +1 > > >> >> >> >> WDYT ? >> >> Thanks, >> Manoj >> >> >> Best Regards.. >> >> >> Manoj Kumara >> Software Engineer >> WSO2, Inc.; http://wso2.com >> >> Twitter: http://twitter.com/ManKuma >> Mobile: +94713448188 >> >> >> On Thu, Jun 20, 2013 at 4:50 PM, Shameera Rathnayaka >> <[email protected]>wrote: >> >>> Hi devs, >>> >>> Idea is to remove -DapplyPatches option from server startup. If user put >>> new patches or remove existing patches to and from >>> repository/components/patches directory, what he simply need is to apply >>> those changes. We can automate this process with the implemented patch >>> application and verification process as we can identify new patches and >>> reverted patches at server startup. server automatically activate patch >>> application process if there is any patch changes(add or remove) in >>> repository/components/patches when server starts. User don't need to >>> provide -DapplyPatches with startup and server intelligently handle it. >>> Hence we can get rid of -DapplyPatches parameter. >>> >>> Existing patch application and verification keep as it is , that means >>> if there is any verification problem still it prints warn in startup and >>> log to patches.log file more details as well. >>> >>> WDYT? >>> >>> Thanks, >>> Shameera. >>> >>> *Software Engineer - WSO2 Inc.* >>> *email: shameera AT wso2.com <[email protected]> , shameera AT >>> apache.org <[email protected]>* >>> *phone: +9471 922 1454* >>> * >>> * >>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>> *Twitter : *https://twitter.com/Shameera_R >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > > * > * > *Lean . Enterprise . Middleware* > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
