jmod issue

[Alan Bateman]

On 02/03/2012 00:46, Jonathan Gibbons wrote:
>
> Tried that.   No, it really was a somewhat misleading "file not found" 
> issue.
> I presume the code sees if the item on the command line exists as a 
> file, and
> treats it as such if so, but otherwise presumptuously treats it as a 
> module name.
>
> -- Jon
I think the options to jmod install needs to be re-examined (more 
generally the CLIs need a bit of an overhaul, jpkg more so). As it 
stands the install command can't always figure out what you want to do. 
If you give it a path to a jmod file or a directory of classes then it 
gets it right. However it also allows a module query and this isn't easy 
to disambiguate from the case where you give it a path to something that 
doesn't exist. I'll create a bug for this so that it's not forgotten but 
I think it's something that will resolve itself anyway once someone gets 
around to cleaning up the CLIs.

-Alan