Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 357337

Summary: Incremental build doesn't work as per bucky book.
Product: z_Archived Reporter: Philip Bedingfield <philip.bedingfield>
Component: BuckminsterAssignee: buckminster.core-inbox <buckminster.core-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: henrik.lindberg, thomas
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Philip Bedingfield CLA 2011-09-11 20:57:57 EDT
Build Identifier: 1.4.0.v20110827-1535

According to the definitive guide, buckminster 'build' without any options should do an 'INCREMENTAL' build, but it is always a full build.

From the bucky book ->

build [ { -? | --help } ]
[ { -c | --clean } ]
[ { -t | --thorough } ]

Description
Runs a workspace build. If -c is specified, a clean is performed before the build. If -t is specified a full build is performed if an incremental build fails.



Reproducible: Always

Steps to Reproduce:
Just call 'build' twice without any options. The second call shouldn't have anything to build.
Comment 1 Henrik Lindberg CLA 2011-09-12 13:23:00 EDT
Is the map or the reality broken ?
Comment 2 Thomas Hallgren CLA 2011-09-12 14:17:54 EDT
Well, that depends...

If we just change the reality to match the documentation, then I would expect that some builds would break. If however we add a --incremental option and retain the default behavior, then we won't actually change anything. I like that better since we otherwise need an option to describe the default (full build but not thorough, difference being that a thorough build is preceded by a clean).
Comment 3 Henrik Lindberg CLA 2011-09-12 16:32:22 EDT
(In reply to comment #2)
> Well, that depends...
> 
> If we just change the reality to match the documentation, then I would expect
> that some builds would break. If however we add a --incremental option and
> retain the default behavior, then we won't actually change anything. I like
> that better since we otherwise need an option to describe the default (full
> build but not thorough, difference being that a thorough build is preceded by a
> clean).

ok, so this is both a documentation issue (it does not describe how it actually works), and a feature request. If the --incremental feature is implemented, the docs have to change anyway. 

I asked, because I was about to change this issue to be a documentation issue...