The build script now creates a beast-beagle.jar that contains the beagle specific stuff. This is only loaded if the -beagle flag is given and then requires the beast-beagle.jar to be on the class path. We now have our first plugin! This means we can distribute a beast-beagle.jar at a later date and it will work with the current BEAST. This is not quite perfect yet as the parser list has to be packaged in the beast.jar so we can't have arbitrary plugins. We need a way of searching jar files for parser lists. We can then have a /plugins folder into which we could drop jar files.
The build script now creates a beast-beagle.jar that contains the beagle specific stuff. This is only loaded if the -beagle flag is given and then requires the beast-beagle.jar to be on the class path. We now have our first plugin! This means we can distribute a beast-beagle.jar at a later date and it will work with the current BEAST. This is not quite perfect yet as the parser list has to be packaged in the beast.jar so we can't have arbitrary plugins. We need a way of searching jar files for parser lists. We can then have a /plugins folder into which we could drop jar files.
JifengJiang/beast-mcmc,JifengJiang/beast-mcmc,JifengJiang/beast-mcmc,JifengJiang/beast-mcmc,JifengJiang/beast-mcmc