Project requiremodification with forceOnly

I've noticed some others have encountered the same issue I had, which
was the need to use force only builds with modification being
required. It would seem to me that if it was the intention for
"buildWasForced" (Project.java) to override other configuration
options, that it would be the first option checked rather than the
last.

Given these cases:

CASE 1) I want to schedule builds regardless of changes (none)
CASE 2) I only want to build if something has changed (requiremodification)
CASE 3) I want to build by force once, regardless of changes (none OR
requiremodification)
CASE 4) I only want to build by force, regardless of changes (forceOnly)

the only case that I can think of for using both is:

CASE 5) I only want to build by force and only if there are changes
(forceOnly + requiremodification)

Anyway, the way I fixed my issue was as follows:

Project.java (440) if (buildWasForced) {
changed to
Project.java (440) if (buildWasForced && !(forceOnly && requiremodification) ) {

This will continue to respect the rules to force a build if the
project is "forceOnly" or "requiresmodification", including if there
were no changes or neither option is set, while preventing a build
when using both options.

Thanks,
Jacob S

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference