[
https://issues.jboss.org/browse/FORGE-1644?page=com.atlassian.jira.plugin...
]
George Gastaldi updated FORGE-1644:
-----------------------------------
Description:
If would be nice if each addon had a storage area (not temporary) to store files relevant
to the addon execution. This area could live under {{USER_HOME/.forge/store/addon_name}}.
Here is an example code on how to access it:
{code}
@Inject Addon addon;
File storageArea = addon.getStorageDirectory();
{code}
Examples:
- The current config.xml file could be in the storage directory of the configuration
addon
- The shell specific files (export, alias, history) could be in the storage directory of
the shell addon
was:
If would be nice if each addon had a storage area (not temporary) to store files relevant
to the addon execution. This area could live under {{FORGE_HOME/store/addon_name}}.
Here is an example code on how to access it:
{code}
@Inject Addon addon;
File storageArea = addon.getStorageDirectory();
{code}
Examples:
- The current config.xml file could be in the storage directory of the configuration
addon
- The shell specific files (export, alias, history) could be in the storage directory of
the shell addon
Addons should have a storage area
---------------------------------
Key: FORGE-1644
URL:
https://issues.jboss.org/browse/FORGE-1644
Project: Forge
Issue Type: Feature Request
Components: Furnace (Container)
Affects Versions: 2.1.1.Final
Reporter: George Gastaldi
Fix For: 2.x Future
If would be nice if each addon had a storage area (not temporary) to store files relevant
to the addon execution. This area could live under {{USER_HOME/.forge/store/addon_name}}.
Here is an example code on how to access it:
{code}
@Inject Addon addon;
File storageArea = addon.getStorageDirectory();
{code}
Examples:
- The current config.xml file could be in the storage directory of the configuration
addon
- The shell specific files (export, alias, history) could be in the storage directory of
the shell addon
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira