Hi Rony, I was about to commit those changes and held it back to get some clarification.
These changes will require commons-logging.jar to be in the class path, when source is compiled. If I am not mistaken there is an automated build process via GUMP. So could you please tell me how do these changes without hurting the automated build process? If I upload commons-logging.jar to trunk/lib directory, will it resolve the matter for GUMP? or is there another way tell GUMP to add this jar to its class path when it compiles bsf-src? Thanks, Sanka On 1/16/06, Rony G. Flatscher <[EMAIL PROTECTED]> wrote: > Hi Sanka, > > > As for the final preparations of a new release of BSF, I would like to > > suggest the following changes. > > > > (1) Get rid of org.apache. bsf.util.DebugLog.java class and use > > commons-logging and log4j to log whatever we need to log. > > +1 > > > (2) Remove org.apache.bsf.engines.activescript.* from the current > > repository since we no longer support it. > > +1 > > > (3) Move to testcases out from the trunk/src dir to /trunk/test which > > will make it looks more cleaner. > > +1 > > A question: would it make sense to submit a testcase for the ooRexx > engine, even if the engine itself is not part of the base distribution? > > > Thoughts ? > > Great, the ball is rolling ... > > ---rony > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
