On Wed, May 22, 2013 at 9:53 AM, Senaka Fernando <[email protected]> wrote:
> Hi all, > > With the new patching strategy that we have, we preserve the same version > numbers for patches when it comes to the jars that are patched. My question > is how would these get deployed into our Maven Repos? > You don't need to deployed them to maven repos. Only patch zip is deployed to maven repo. > > A. The releases that use the older (non-patched) versions would require > the older jars (which would most probably already be in the Maven repos), > for samples and other 3rd party implementations. > > B. The newer releases that use the patched versions would require the new > jars OTOH, for samples and other 3rd party implementations. > If a new product need that, need to get the patch. > > How is this problem addressed in our patching strategy? > Please read this[1]. And ask your team members to read as well :) One issue with the current path process is to run the integration tests with the patch. You can do this by running the features and distribution after patch is build. But need to find a better way. thanks, Amila. [1] https://docs.google.com/a/wso2.com/document/d/1Kz6vINXA1j74sM8vb8BE0BSIAUnYJH0BERbJxwxi2xQ/edit > > Thanks, > Senaka. > > -- > *Senaka Fernando* > Member - Integration Technologies Management Committee; > Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > -- *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
