Welcome back folks, after the vacation - and wish you all very happy new year...!!!
[1] lists all possible ways how we broke the build in 2011 :-) Please take two minutes go through them... It's boring to break the build in the same way we did in 2011 - so let's not repeat them - if you find much innovative ways - please update [1] :-) Thanks everyone who contributed to build the list... Thanks & regards, -Prabath [1]: https://docs.google.com/a/wso2.com/document/d/1Cuj62jX8nA2bcZSDEpfIp72fF6ts9_7ASyChkARgOcw/edit ---------- Forwarded message ---------- From: Prabath Siriwardena <[email protected]> Date: Thu, Dec 8, 2011 at 9:12 AM Subject: How we break the build..? :-) To: carbon-dev-group <[email protected]> Nothing serious.. just for fun.. following are few ways how we did break the build in the past.. :-) Please add whatever you remember how you or your colleague broke the build... No names please.... 1. Changed a public API, built the components in my product and committed 2. Added a new method to an interface - updated it's implementation in my product and committed - forgot to send mail to carbon-dev on the interface change 3. Added new class - builds fine locally - committed all the other changes - forgot to commit the new file 4. Added new a component - added a new feature - committed both - updated the root pom of features - but, forgot to update the root pom of components 5. Added a new dependency to the pom of my component - did some code changes - did an svn stat from ../src - committed all code changes - missed the pom with the new dependency Let's build this list.. :) -- Thanks & Regards, Prabath http://blog.facilelogin.com http://RampartFAQ.com -- Thanks & Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
