Skip to content
rjrudin edited this page Jun 16, 2015 · 19 revisions

Automatically load new/modified modules

"gradle mlWatch" - invokes the WatchTask.

This runs an infinite loop, checking every second for modifications in the application's set of module paths. This is a useful task to run when you're developing modules and you only want to load what you've created/modified, and you don't want to have to run a command after every change to load your modules.

See How modules are loaded for information on how modules are actually loaded.

Note that this does not yet account for deleted modules - i.e. it won't delete the corresponding module from the modules database.

Clearing the content database

Call "gradle mlClearContentDatabase" (or usually "gradle mlclearcon") to delete all documents in your content database. You must include the property -PdeleteAll=true. This property is required to decrease the chance that you run this task accidentally.

Clearing the modules database

gradle mlClearModules

Invokes the ClearModulesTask for clearing out all or most of the modules in a modules database. Useful for when you need to do a fresh load of modules because some of the ones in the modules database may have been deleted from your project.

This task depends on mlDeleteModuleTimestampsFile, as it's almost always the case that when you clear all the modules, you also want to delete the properties file that keeps track of when modules were last loaded.

Clone this wiki locally