NAME

TaskPipe::PathSettings::Project - project path settings for TaskPipe

METHODS

plan

The name of the plan to use

task_identifier

Normally your task modules will have names in the format TaskPipe::Task_(task name). This means 'Task_' is identifying the module as a task module. In the unlikely event you need to use another identifier, you can set task_identifier to a new value.

task_module_prefix

Normally your task modules will have names in the format TaskPipe::Task_(task name). However, lots of modules start with TaskPipe, and if you want to differentiate your project tasks from general TaskPipe tasks you can set task_module_prefix to something else. For example, if you set task_module_prefix=MyProject, then you would create packages with the name format MyProject::Task_(taskname) instead of TaskPipe::Task_(taskname) in your project lib dir.

Note this does not necessarily prevent the potential for a namespace collision when running a plan. For example, if you are planning to use TaskPipe::Task_Record then you should not create a MyProject::Task_Record (unless you are intending to have MyProject::Task_Record inherit from TaskPipe::Task_Record).

lib_dir

The directory inside the project root where TaskPipe will look for Task packages

plan_dir

The directory inside the project root where TaskPipe will look for plans

source_dir

The directory inside the project root where TaskPipe will look for files to use as data sources

log_dir

The directory inside the project root to write log files

AUTHOR

Tom Gracey <tomgracey@gmail.com>

COPYRIGHT AND LICENSE

Copyright (c) Tom Gracey 2018

TaskPipe is free software, licensed under

The GNU Public License Version 3