Hi Sanka,
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?
unfortunately, I have no knowledge about the build process of BSF.
AFAIK, Sanjiva or Victor are/is the man in the know, but the latter one
has been quiet as if he fell off the edge of the world...
So right now, I cannot really help you, so I would say, if no one else
shows up, just go ahead with what you see fit and appropriate. If you
need assistance one way or the other, I will try to dig into this in
order to help; also we'd need to incorporate all the
suggestions/additions on new supported languages and the like.
Regards,
---rony
P.S.: One thing I would wish myself was to set BSF up such that a
regular build is created from the sources such that interested parties
get really to download the latest version of the binaries as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
