Please look for your module in the list below. 

Git Module Command Line Interface Support
assembly COMMANDS
communities_api COMMANDS
communities_qc COMMANDS
experiment COMMANDS
file_type_service COMMANDS
genome_annotation COMMANDS
idserver COMMANDS
invocation COMMANDS
jnomics COMMANDS
kb_seed COMMANDS
KBaseFBAModeling COMMANDS
networks COMMANDS
ontology_service COMMANDS
phispy COMMANDS
plant_expression_service COMMANDS
probabilistic_annotation COMMANDS
prom_service COMMANDS
protein_info_service COMMANDS
translation COMMANDS
trees COMMANDS
adapters COMMANDS: No such file or directory
auth COMMANDS: No such file or directory
auth_service COMMANDS: No such file or directory
aux_store COMMANDS: No such file or directory
bootstrap COMMANDS: No such file or directory
cdd_service COMMANDS: No such file or directory
cluster_service COMMANDS: No such file or directory
communities_prospecting COMMANDS: No such file or directory
communities_wizzard COMMANDS: No such file or directory
concrete5 COMMANDS: No such file or directory
datavis COMMANDS: No such file or directory
dev_container COMMANDS: No such file or directory
dev_container_tools COMMANDS: No such file or directory
erdb_service COMMANDS: No such file or directory
exchange_format_specs COMMANDS: No such file or directory
exchange_format_support COMMANDS: No such file or directory
expression COMMANDS: No such file or directory
fastbitdb COMMANDS: No such file or directory
fbaModelData COMMANDS: No such file or directory
feature_selection COMMANDS: No such file or directory
genome_data_browser COMMANDS: No such file or directory
genotype_phenotype_api COMMANDS: No such file or directory
kbapi_common COMMANDS: No such file or directory
KBaseFBAModeling COMMANDS: No such file or directory
kb_model_seed COMMANDS: No such file or directory
matR COMMANDS: No such file or directory
microbes_model_builder COMMANDS: No such file or directory
micro_pheno COMMANDS: No such file or directory
narrative COMMANDS: No such file or directory
network_viewer COMMANDS: No such file or directory
operon_service COMMANDS: No such file or directory
otu_correlation COMMANDS: No such file or directory
perl_runtime COMMANDS: No such file or directory
persistent_store COMMANDS: No such file or directory
plant COMMANDS: No such file or directory
plant_network COMMANDS: No such file or directory
plugin COMMANDS: No such file or directory
prinseq COMMANDS: No such file or directory
py_deploy_tools COMMANDS: No such file or directory
registry COMMANDS: No such file or directory
regprecise COMMANDS: No such file or directory
release COMMANDS: No such file or directory
ribo16s_pipeline COMMANDS: No such file or directory
runtime COMMANDS: No such file or directory
search COMMANDS: No such file or directory
shock COMMANDS: No such file or directory
sim_service COMMANDS: No such file or directory
testing COMMANDS: No such file or directory
typecomp COMMANDS: No such file or directory
ui COMMANDS: No such file or directory
widget_lib COMMANDS: No such file or directory
workspace_browse COMMANDS: No such file or directory
workspace_service COMMANDS: No such file or directory
On Mar 21, 2013, at 7:33 AM, Thomas Brettin <brettin@mcs.anl.gov> wrote:

On the Commands File

We are going to do a minor release next week. If you have not created a COMMANDS file in your repo, please do so before the end of this week. Instructions are listed here:

https://trac.kbase.us/projects/kbase/wiki/StandardDocuments

I've had a number of discussions with Rick on the issue of the COMMANDS file. We see this file going beyond just defining the set of commands deployed in IRIS. It in fact specifies what commands are in the KBase CLI. We plan to integrate the file with the release engineering process.

In the future, commands not listed in the COMMANDS file will not be included in the mac dmg, will not be included in the ubuntu image, and will not be deployed. This allows you to choose which commands are ready for deployment. I imagine the structure of the file could change in the future to contain more information about the commands, but for now lets just get them in our repos.

I've created a number of them for folks to illustrate how easy it is. If anyone else needs help, I'll be available today.

On the Upcoming Minor Release

Any one wanting a new release pushed to production should let the release team know (release-team@lists.kbase.us).



Thanks,
Tom