Final step of the java_cpp_template -> java_cpp_enum migration.

build/get_landmines.py

 #!/usr/bin/env python
 # Copyright 2013 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 """
 This file emits the list of reasons why a particular build needs to be clobbered
 (or a list of 'landmines').
 """
 
@@ skipping 41 matching lines @@
   if (platform() != 'ios'):
     print 'Clobber to get rid of obselete test plugin after r248358'
     print 'Clobber to rebuild GN files for V8'
   print 'Need to clobber everything due to build_nexe change in nacl r13424'
   print '[chromium-dev] PSA: clobber build needed for IDR_INSPECTOR_* compil...'
   print 'blink_resources.grd changed: crbug.com/400860'
   print 'ninja dependency cycle: crbug.com/408192'
   if platform() == 'android':
     print 'Clobber: To delete stale generated .java files.'
     print 'Delete stale generated .java files again. crbug.com/349592'
+    print 'Delete stale generated .java files again. crbug.com/349592'

[Yaron, 2014/10/15 02:36:49]

dup? or is this file special in that adding an output line generates a new
landmine?

[mkosiba (inactive), 2014/10/15 09:46:08]

Intentional and seems to work. I changed the line so that it's obvious that it's
intentional.

[cjhopman, 2014/10/16 16:54:51]

For the record, a landmine is triggered whenever the output of running this
script changes. Having a single print statement for each condition is sufficient
if you just change what is printed.

 
 
 def main():
   print_landmines()
   return 0
 
 
 if __name__ == '__main__':
   sys.exit(main())