You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bsf-dev@jakarta.apache.org by "Rony G. Flatscher" <Ro...@wu-wien.ac.at> on 2006/03/29 13:34:36 UTC
Moving the ball: maintaining/updating infos on BSF website and ...
Hi there,
is there anyone who feels responsible for bringing the BSF WWW-site up
to date?
At the moment the information in "docs/" is very outdated, but it seems
that that branch is used for the material displayed on
<http://jakarta.apache.org/bsf>. There is a branch "xdocs/" which seems
to not be reflected at all (eg. "xdocs/projects.xml").
Then, there would be clearly a need for a daily/current "bsf.jar" such
that interested party can get the latest drop.
Then, there is a need to change the Apache license text to 2.0 in all
source files.
Then, there would be a need for a procedure to finally bring the current
drop of BSF to GA level and start to test and work with BSF 3.0, which
should be interface compatible with the upcoming Java scripting
interface (much of the initial work has been thankfully done already by
Sanka and Nandika, if I am not mistaken).
So is there a procedure in place already which we just need to re-activate?
How should we proceed?
Regards,
---rony
---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
Re: Moving the ball: maintaining/updating infos on BSF website and
...
Posted by "Rony G. Flatscher" <Ro...@wu-wien.ac.at>.
Hi Sanka,
>> is there anyone who feels responsible for bringing the BSF WWW-site
>> up to date?
>>
>> At the moment the information in "docs/" is very outdated, but it
>> seems that that branch is used for the material displayed on
>> <http://jakarta.apache.org/bsf>. There is a branch "xdocs/" which
>> seems to not be reflected at all (eg. "xdocs/projects.xml").
>>
> I'll see whether I can fix it ..
>
*Great*, thank you very much !
>> Then, there would be clearly a need for a daily/current "bsf.jar"
>> such that interested party can get the latest drop.
>>
>> Then, there is a need to change the Apache license text to 2.0 in
>> all source files.
>>
>> Then, there would be a need for a procedure to finally bring the
>> current drop of BSF to GA level and start to test and work with BSF
>> 3.0, which should be interface compatible with the upcoming Java
>> scripting interface (much of the initial work has been thankfully
>> done already by Sanka and Nandika, if I am not mistaken).
>>
>> So is there a procedure in place already which we just need to
>> re-activate?
>>
Also another question to add to these open ones: I have been
contemplating to submit the Java part of the BSF Rexx engine, but not
the platform dependent C++ JNI code, such that other BSF engine
implementors could take advantage of the set of string-only interfaces
to interact fully with BSF and Java. Possibly this would help them to
"jump-start" to a full implementation (e.g. array handling is eased
quite considerably for non-Java based language implementations). Now,
would that be helpful, make sense at all?
(It should be always possible to get at the source and compiled code by
getting the BSF4Rexx package.)
Regards,
---rony
Re: Moving the ball: maintaining/updating infos on BSF website and
...
Posted by Sanka Samaranayake <sa...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rony G. Flatscher wrote:
> Hi there,
>
> is there anyone who feels responsible for bringing the BSF WWW-site
> up to date?
>
> At the moment the information in "docs/" is very outdated, but it
> seems that that branch is used for the material displayed on
> <http://jakarta.apache.org/bsf>. There is a branch "xdocs/" which
> seems to not be reflected at all (eg. "xdocs/projects.xml").
I'll see whether I can fix it ..
>
> Then, there would be clearly a need for a daily/current "bsf.jar"
> such that interested party can get the latest drop.
>
> Then, there is a need to change the Apache license text to 2.0 in
> all source files.
>
> Then, there would be a need for a procedure to finally bring the
> current drop of BSF to GA level and start to test and work with BSF
> 3.0, which should be interface compatible with the upcoming Java
> scripting interface (much of the initial work has been thankfully
> done already by Sanka and Nandika, if I am not mistaken).
>
> So is there a procedure in place already which we just need to
> re-activate?
>
> How should we proceed?
>
> Regards,
>
> ---rony
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org For
> additional commands, e-mail: bsf-dev-help@jakarta.apache.org
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
iD8DBQFELVtH/Hd0ETKdgNIRAhdqAJ9OLNUdm7XGIOECzIeTIat/1gFX2QCdGyW2
0f9czJdpsvg0ydjwCj0MmKg=
=xCk+
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
Re: Moving the ball: maintaining/updating infos on BSF website and
...
Posted by Sanka Samaranayke <ss...@gmail.com>.
Rony G. Flatscher wrote:
> Hi there,
>
> is there anyone who feels responsible for bringing the BSF WWW-site up
> to date?
>
> At the moment the information in "docs/" is very outdated, but it
> seems that that branch is used for the material displayed on
> <http://jakarta.apache.org/bsf>. There is a branch "xdocs/" which
> seems to not be reflected at all (eg. "xdocs/projects.xml").
I'll see whether I can fix it during this weekend.
>
> Then, there would be clearly a need for a daily/current "bsf.jar" such
> that interested party can get the latest drop.
>
> Then, there is a need to change the Apache license text to 2.0 in all
> source files.
>
> Then, there would be a need for a procedure to finally bring the
> current drop of BSF to GA level and start to test and work with BSF
> 3.0, which should be interface compatible with the upcoming Java
> scripting interface (much of the initial work has been thankfully done
> already by Sanka and Nandika, if I am not mistaken).
>
> So is there a procedure in place already which we just need to
> re-activate?
>
> How should we proceed?
>
> Regards,
>
> ---rony
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org