Re: [Gusdev-gusdev] LoadTaxon plugin

[Arnaud K. <ax...@sa...>]

I've tried this:

pcs2g[axk]499: ga +create GUS::PluginMgr::GusApplication --commit
Reading properties from /nfs/team81/axk/.gus.properties
Thu Feb 20 16:28:18 2003        ERROR-IMP       No 
Core.AlgorithmImplementation found for GUS::PluginMgr::GusApplication
Thu Feb 20 16:28:18 2003        ERROR-IMP       Please use 'ga +create 
GUS::PluginMgr::GusApplication --commit'

Basically prior to do the plugins registration this way, 
AlgorithmImplementation needs one entry, GUS::PluginMgr::GusApplication.

Ar

Jonathan Crabtree wrote:

>
> Arnaud-
>
>> Is the Core.AlgorithmImplementation entries population part of the 
>> build process or is it an extra step?
>
>
> It is not currently part of the build process; if you look through the 
> error
> message that the plugin generated, it tells you the command to run in 
> order
> to register it in the database (i.e. AlgorithmImplementation):
>
> > Thu Feb 20 12:43:40 2003        ERROR-IMP       Please use 'ga +create
> > GUS::Common::Plugin::LoadTaxon --commit'
>
> Obviously, this *should* be part of the build process, but I think 
> it's not a
> bad thing that it isn't (at this stage) because we still haven't 
> formalized
> our procedure for testing plugins (both in terms of 3.x schema 
> compliance and
> also in terms of bug testing/automatic regression testing.)  As 
> plugins are
> brought into reasonable compliance with the new system perhaps we can 
> add them
> to the list of plugins that are automatically registered in the 
> database at
> build time.  Steve, what do you think about this idea?  Is this the right
> mechanism to use or should we have another way to indicate that 
> plugins have
> not yet been tested/validated?
>
> Jonathan
>