1) most frequent case in patch-releases : when adding a new version of a component, we never add the relative path property. :)
On Thu, Dec 8, 2011 at 9:12 AM, Prabath Siriwardena <[email protected]>wrote: > 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 > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
