If products had enough integration tests, this would have been just a matter of running these tests. So, if you come across any failure in your products, please make it a point to write an integration test for those scenarios, and then go about fixing the issues.
Thanks Azeez On Thu, Feb 16, 2012 at 10:02 AM, Pradeep Fernando <[email protected]> wrote: > Hi all, > > We have removed most of the jar files found under ${carbon.home}/lib . > These changes will affect the products that are using them. Product teams > should convert the necessary jars in to bundles and package them with their > respective features. Product teams : please make sure that your product is > in working condition, as these modifications will affect the product > runtime. > > I have only tested wso2-as at the moment. > > @Nuwan: > > you got to port JaggeryDeployer.java found under org.wso2.carbon.server to > one of the jaggery components. Think Dilshan has already done that. Commit > it to the trunk and uncomment jaggery related components in > components/pom.xml > > thanks, > --Pradeep > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
