Beanshell and Javascript extensions not registered in master build

[Alex Thurgood]

Le 08/10/2012 12:58, d.ostrovsky at idaia.de a écrit :

Hi David,

> Could you please check that bsh.jar and js.jar are actually built and
> delivered, i. e.:
> 
> make VERBOSE=true beanshell.clean
> make VERBOSE=true beanshell
> 

Even without doing that I can see :

/home/Development/libo/solver/unxlngi6/bin/bsh.jar
/home/Development/libo/solver/unxlngi6/installation/opt/program/classes/bsh.jar

/home/Development/libo/solver/unxlngi6/bin/js.jar
/home/Development/libo/solver/unxlngi6/installation/opt/program/classes/js.jar
/home/Development/libo/workdir/unxlngi6/UnpackedTarball/rhino/js.jar
/home/Development/libo/workdir/unxlngi6/UnpackedTarball/rhino/build/rhino1_5R5/js.jar


so they are compiled at least

> you should see copy bsh.jar to solenv.
> If it is delievered how can i test these "functional beanshell and
> javascript"?

A menu entry under Tools > Macros > Organise should contain the relevant
entries. These open the Macro manager dialog, where you can test the
scripts.


> Did it work prior to gbuildification?

Yes.


Alex