avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leif Mortenson <leifli...@tanukisoftware.com>
Subject Re: [PROPOSAL] restructuring of the instrument suite
Date Fri, 28 Feb 2003 18:50:01 GMT
Stephen McConnell wrote:

>
> This is a proposal for the restructuring of the instrumentation suite:
>
> Current structure:
>
>   instrument
>   instrument-manager
>   instrument-client
>
> Proposed structure:
>
>   instrument <-- no change
>   instrument-manger <-- move AltRMI classes to 
> instrument-monitor/altrmi/server
>   instrument-monitor
>     - altrmi/server <-- two classes from instrument manageer
>     - altrmi/client <-- content of instrument-client 

Is there any reason not to just make the instrument-manager build skip 
the altrmi
classes if they are not present.  This is what logkit and other projects do.

However, as things are now, there is no run time dependency on the 
altrmi jars.
If the altrmi connector is not specified in the instrument configuration 
file, then
those classes are never loaded.  This is the same as other jars like logkit
which are built in an environment which contains all available jars.  But at
runtime, it is not required that all of those jars be in the classpath 
if the
relevant features are not being used.

Cheers,
Leif



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message