On Thu, Apr 4, 2013 at 1:00 PM, Kishanthan Thangarajah <[email protected]>wrote:
> Let me explain, > > Once this patch is released, it will be publicly available for download. > Say its available under > dist.wso2.org/downloads/carbon/4.1.0/kernel/patches/patch0001 > > Lets take AS 5.1.0 for example. It does not include this patch as it is > released already. So if people want to include this patch, they will have > download and apply it, by following the normal patch applying strategy. > > But for products which are based on platform version 4.1.1 or above, will > be including this patch by default, and will be shipped. > > We will be writing a doc for this, so that people will not get confused. > +1 thanks, > > Thanks, > Kishanthan. > > > On Thu, Apr 4, 2013 at 1:31 AM, Supun Malinga <[email protected]> wrote: > >> Hi, >> >> For my information. >> How are we to include such a patch with a product released on top of >> platform 4.1.x?. Do we need to ship the patch with the product pack or we >> have to manually install the patches afterwards?. I might have missed some >> discussion around this, please point me to a reference if that is so. >> >> thanks, >> >> >> On Thu, Apr 4, 2013 at 12:36 AM, Kishanthan Thangarajah < >> [email protected]> wrote: >> >>> >>> >>> >>> On Wed, Apr 3, 2013 at 10:18 PM, Nuwan Dias <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I need to patch the 4.1.0 kernel with the diff attached. This is to fix >>>> the issue mentioned in the mail thread subject as "NPE when a tenant does a >>>> REST invocation with the OPTIONS verb". >>>> >>>> How do we patch the 4.1.0 kernel? >>>> >>> >>> There is a structure to patch kernel. >>> >>> 1. First create a jira issue for this. >>> >>> 2. The following is the 4.1.0 kernel branch. >>> >>> ── 4.1.0 >>> ├── core >>> ├── dependencies >>> ├── distribution >>> ├── features >>> ├── parent >>> ├── *patches* >>> ├── pom.xml >>> └── service-stubs >>> >>> Since this is the first patch, under the patches directory, you have to >>> create the first patch folder (patch0001). And svn copy the >>> relavant component, which needs to be fixed. Add your fix and build it. >>> >>> 3. Add a README and wso2carbon-version.txt file in the same patch >>> directory with the patch details (eg : WSO2 Carbon Framework v4.1.0 >>> patch0001). >>> >>> Please note that there are no API changes allowed when fixing. >>> >>> Thanks, >>> Kishanthan. >>> >>> >>>> >>>> Thanks, >>>> NuwanD. >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Software Engineer - WSO2, Inc. http://wso2.com >>>> email : [email protected] >>>> Phone : +94 777 775 729 >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Kishanthan Thangarajah* >>> Software Engineer, >>> Development Technologies Team, >>> WSO2, Inc. >>> lean.enterprise.middleware >>> >>> Mobile - +94773426635 >>> Blog - *http://kishanthan.wordpress.com* >>> Twitter - *http://twitter.com/kishanthan* >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Supun Malinga, >> >> Software Engineer, >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> email - [email protected] <[email protected]> >> mobile - 071 56 91 321 >> > > > > -- > *Kishanthan Thangarajah* > Software Engineer, > Development Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com* > Twitter - *http://twitter.com/kishanthan* > -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
