When a user builds a 2.1 or 2.2 project with a 3.0 they can get an error
due to invalid command line options from rzc. What happens is that the
3.0 tasks (which are a singleton) are talking to the 2.X build tool
(which is NOT a singleton).
Recently some changes were make to the 3.0 tasks which caused this bug
because it did not properly accomodate downlevel versions of rzc. We
have an integration test for this scenario for but the regression was
not detected, so obviously something is wrong with the test setup. I'll
investigate that separately.
When a user builds a 2.1 or 2.2 project with a 3.0 they can get an error due to invalid command line options from rzc. What happens is that the 3.0 tasks (which are a singleton) are talking to the 2.X build tool (which is NOT a singleton).
Recently some changes were make to the 3.0 tasks which caused this bug because it did not properly accomodate downlevel versions of rzc. We have an integration test for this scenario for but the regression was not detected, so obviously something is wrong with the test setup. I'll investigate that separately.