[X] Stable - go ahead and release The following areas were tested.
*Java Security Manager Scenarios* - Sign all jars with JDK 7 and check the packs [1] - check deployment of webapps - check deployment of jaggery apps - check deployment of jsf apps - check deployment of spring apps - check log file roll over - Sign all jars with JDK 6 and check the packs *SVN based deployment synchronizer * - Deploy an axis2 service at master node and verify whether it's synchronized to slave nodes - Deploy a module at master node and verify whether it's synchronized to slave nodes - Deploy a webapp at master node and verify whether it's synchronized to slave nodes - Deploy a jar service/jaxrw service/jaggery app at master node and verify whether they are synchronized to slave nodes - Do changes to a service at master node and verify whether it's reflected at slave node - Delete a service at master node and verify whether it's reflected at slave node - Delete a cApp at master node and verify whether it's reflected at slave node - Drop to file system (do manual checking to the svn location) and verify whether they are available in both master & slave nodes" - axis2services - webapps - cApps - Edit axis2service/webapp configuration at svn level (commit an updated axis2service) and verify whether changes are reflected at both master & slave nodes - Delete axis2service/webapp configuration at svn level (do an svn delete) and verify whether they are removed both from master & slave nodes - Try with an svn secured with security credentials - Try with an svn that is not secured with security credentials [1]. Pack did not start after signing with JDK 7, but was start with JDK 7 after sigining JDK 6 Regards, Aruna On Tue, Dec 16, 2014 at 6:38 PM, Niranjan Karunanandham <[email protected]> wrote: > > [X] Stable - go ahead and release > > The following were tested in both Linux and Windows environment: > > - Artifact Deployment with and without GD > - Access axis2 services with http & https endpoints > - Access axis2 services with http & https endpoints (Ghost enable) > - Try to deploy a Service Archive (.aar) which is not properly > build and check the error logs > - Deploy webapp and invoke > - Deploy webapp and invoke (Ghost enable) > - WS-Security for web-services > - Ghost-deployment (CApp) in standalone mode > - Ghost-deployment (CApp) in cluster > - Feature Management > - Install features > - Un-install features > - Install features by Category > - Install feature without license (Expected: Prevent installation) > - Install features with and without license (Expected: Prevent > installation) > - Secure Vault > - Exceute ciphertool using arguements (-Dconfigure, -help, -Dchange) > - Secure vault using the default WSO2 Keystore > - Secure vault after replacing the certificate in alias wso2carbon > in Keystore > - Secure vault with different passwords for wso2carbon.jks and > client-truststore.jks > - Logging > - Log roll over (Reduce the log roll over time and test if it works) > - - special case : keep the logs opened by an editor/tool during > roll over and see whether it is successful > - Tenant aware logging > - Create a webapp that logs using carbon logging framework > - Change the logs directory and log file name using the > log4.properties file > - With Append=true in file appender the log file doesn't get > resetted > - Changing the Max File Size (Log: RollingFileAppender) > - Changing the Backup Index (Log: RollingFileAppender) > > > Regards, > Nira > > > On Mon, Dec 15, 2014 at 9:28 AM, Sameera Jayasoma <[email protected]> > wrote: >> >> Hi Devs, >> >> This is the *4th* release candidate of WSO2 Carbon Kernel 4.3.0. >> >> This release fixes the following issues : >> https://wso2.org/jira/issues/?filter=12088 >> >> Please download, test and vote. >> >> *Binary distribution for Carbon, AS & ESB :* >> http://svn.wso2.org/repos/wso2/scratch/carbon/4.3.0-RC4/ >> >> *Maven staging repository :* >> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-037/ >> >> *The tag to be voted upon :* >> https://github.com/wso2/carbon4-kernel/releases/tag/4.3.0-RC4 >> >> >> [ ] Broken - do not release (explain why) >> [ ] Stable - go ahead and release >> >> Thanks, >> Carbon Team. >> >> -- >> Sameera Jayasoma, >> Software Architect, >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://sameera.adahas.org >> twitter: https://twitter.com/sameerajayasoma >> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >> Mobile: 0094776364456 >> >> Lean . Enterprise . Middleware >> >> > > -- > > *Niranjan Karunanandham* > Senior Software Engineer - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > -- *Aruna Sujith Karunarathna* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 9040362 | Work: +94 112145345 Email: [email protected] | Web: www.wso2.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
