I believe we could do the following to resolve the matter. The kernel patch009 is unzipped at build time in the bin.xml before the contents are getting coppied over to the patches folder. So at the time of copying these aretifacts we can purposely omit the particular jar from getting copied over.
However, I do not suppose this will fix the problem, as even if you stop the copying the woden.jar over from the kernel patch, a woden jar would still exist in the plugins directory. This happens i believe because there is a dependency from some component, direct or indirect to wodenM8. We need to figure out what this connection is and maybe update the referred version to m9 instead of m8. Thanks and Regards, Ruwan Yatawara Senior Software Engineer, WSO2 Inc. email : [email protected] mobile : +94 77 9110413 blog : http://thoughts.ruwan-ace.com/ www: :http://wso2.com On Thu, Sep 11, 2014 at 2:19 AM, Jenananthan Yogendran <[email protected] > wrote: > > Hi , > > I am working on this jira[1] issue. > > This fix involves updating the version of woden to version M9 and set of > code changes in org.wso2.carbon.apimgt.impl component. > > we will need to add version M9 as a dependency to the Turing branch till > woden does the next release with fix[2] and RuwanY has done changes to > include this jar as dependency. > > I have made necessary changes to apimgt.impl and added a feature to pack > this jar at build time. > But we need to prevent the older woden M8 from packing to the product as > this will cause OSGI issues.It seems this older woden M8 comes to the pack > from kernel patch0009. > > so how to prevent woden M8 from packing to the product? > > 1.https://wso2.org/jira/browse/APIMANAGER-2528 > 2.https://issues.apache.org/jira/browse/WODEN-236 > -- > Jenananthan Yogendran > *Software Engineer,* > *WSO2 inc., http://wso2.com <http://wso2.com>* > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
