With some recent changes to maven ( separate classpaths for tests and maven prefixes on properties ), maintaining the legacy and maven builds is getting to be a pain. Currently the iutests in maven do not work since there are changes required due to the above maven changes. They are minor, but will break the legacy builds ( wrt cactus tests ).
Options for jakarta-turbine-2: 1) Time to let go of the legacy builds and switch to maven as the sole build env? 2) Check in changes, break legacy run of cactus tests. The rest of the legacy build should be fine. 3) Do not check anything in, leave legacy builds intact. Maven iutests won't work. I'm pro option 1, but not sure if there are features of the legacy build that are yet needed ( packaging up the old torque into a torque.zip? ). ================================================================= Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
