> -----Original Message-----
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
> 
> Seems to me that we have two options here:
> 
>    URL
>    Artifact spec
> 
> If we use a url we are not going through the repository, instead we
> would need to setup a separate cache with an index that keys resources
> against url.
> 
> If we use the artifact spec then we need to establish a more complete
> specification that what is currently recognized by Merlin.  Currently
> you can select the merlin implementation using an artifact spec, but
> this has two associated problems:
> 
>    a) the spec external form currently uses [group]:[name];[version]
>       but the ";" character is problematic on a unix command line
>       unless quoted (but this isn't a problem when used in a
>       properties file)
> 
>    b) the spec external form does not provide a way of declaring the
>       type
> 
> I'm currently thinking that a separate url cache would be better.

The reason I brought up the artifact spec since I thought "why create
another cache when we already have a repository?"  But I agree that the spec
would need better defined and it might be easier to just have a URL cache.
I'm open for either option and just wanted to hear everyone's opinion on the
matter.

J. Aaron Farr
  SONY ELECTRONICS
  DDP-CIM
  (724) 696-7653

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to