[
https://issues.jboss.org/browse/FORGE-2200?page=com.atlassian.jira.plugin...
]
Jerome B commented on FORGE-2200:
---------------------------------
I confirm this issue.
Have it w/ 2.13 , 2.13.1 and 2.14 on windows platform.
I used sysinternal process explorer. it confirms it's Eclipse's javaws process
that has a grip on the jar file
Its a pita, because the build is indicated as successful, and the addon installed
My 2 workarounds
1/ In Eclipse, do File/Restart (beware not to have forge console autostarting or you have
to be quick to delete)
OR
2/ Increase the version number (I copy the good one into an xml comment)
Unable to fully remove addon
----------------------------
Key: FORGE-2200
URL:
https://issues.jboss.org/browse/FORGE-2200
Project: Forge
Issue Type: Bug
Components: Addon Development, Windows
Affects Versions: 2.13.0.Final
Environment: Eclipse CLI
Reporter: Michael Schwartz
Priority: Minor
Fix For: 2.x Future
as reported here:
https://developer.jboss.org/thread/251850
While developing addon's it is important to constantly redeploying the addon without
changing the version number for each deploy. Currently this is not possible without
closing/opening eclipse between each redeploy. After a while I found the following:
When executing "addon-remove" in Eclipse Luna the specified addon gets removed
in the installed.xml file in the user's .forge directory.
The corresponding class-files in .forge directory however are still there and cannot be
deleted under windows which is an indicator of an open file pointer.
When stopping forge console the directory still cannot be deleted. One have to close
eclipse in order to delete the directory.
I assume that this is the cause of not being able to update the addon without exiting
eclipse.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)