Martin Schaffstall writes: > It is interesting to observe that each time the project reaches > another milestone a Sun employee steps in and demands a full change of > the project. But it seems Sun now shows its true face by tearing down > the project with unbearable review requests, essentially preventing > progress indefinitely.
What utter nonsense! I want the project to integrate. I just don't want it to integrate in a way that will cause a disaster down the road. Having builds themselves break (as opposed to particular projects seeing testing failures) would be a disaster. In this particular case, the project team has repeatedly ignored advice from various folks (not just me) to the effect that building test cases to run in the middle of the build is not considered good practice within the ON consolidation, and that the _preferred_ way to deal with build dependencies is with explicit dependencies: that is, a flag day. The project team's chosen course -- using LD_LIBRARY_PATH -- to get around the numerous hurdles in the way of this discouraged practice itself causes new problems. There is clearly a difference between pointing out a flaw in the implementation -- even one that will need to be fixed before integration -- and a "full change" of the project (whatever that may mean) or "tearing it down." Both of those charges are demonstrably false. If you have something useful to contribute, please do. If all that you have is FUD, please consider finding a better place to fling it. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
