]
George Gastaldi closed FORGE-886.
---------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.0.0.Alpha10
(was: 2.x Future)
Resolution: Done
Implemented using furnace-manager
Should be able to re-install an existing Addon if it is a SNAPSHOT
------------------------------------------------------------------
Key: FORGE-886
URL:
https://issues.jboss.org/browse/FORGE-886
Project: Forge
Issue Type: Feature Request
Components: Furnace (Container), Plugin Repository
Affects Versions: 2.0.0.Alpha3
Reporter: Lincoln Baxter III
Assignee: George Gastaldi
Fix For: 2.0.0.Alpha10
Currently re-installing Addons is not supported, because there is no way to tell Forge to
stop using the existing deployed files without giving it time to detect the change and
re-deploy the addon.
In order to implement this, the Forge registry file probably needs to use some kind of
marker files.
{code}
.dodeploy
.deployed
.undeployed
{code}
So that it knows how to respond when changes are made faster than timestamps can detect.
This would (hopefully) also in theory be a step toward multi JVM (multiple running forge /
concurrent modification instance) support.
This has been partially implemented, but only naively. The files are actually re-written
on UNIX based OS's, and will be re-loaded next time the addon is disabled/re-enabled,
but this will not work on Windows.
--
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: