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. > +1. We should not make it too complex. If user has copy a patch that has to apply automatically. thanks, Amila. > > 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 > > -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
