[
https://issues.jboss.org/browse/JBIDE-13948?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-13948.
---------------------------------
Fix Version/s: 4.1.0.Beta1
(was: 4.1.x)
Resolution: Done
I've pushed this to master and fixed it the best that I can. The general situation is,
when changing the fileset to a new valid value, an incremental build of the project is
initiated. It takes the old fileset, removes it (and any files that matched it), and then
adds the new node.
Unfortunately, we can't just assume the old value was always invalid. It may have been
a valid folder which was removed somehow, by the user most likely. So we can't truly
do an incremental modification here.
My patch tries to handle the exception properly and give a bit more advice in the upcoming
error dialog, which says a full build may be required.
This is because if the old invalid folder was at one time valid, but has been removed
somehow, those files still need to be removed from the archive. But we don't know what
they were. We can't remove what we don't know.
Anyway, pushed to master.
Error when fixing location of fileset
-------------------------------------
Key: JBIDE-13948
URL:
https://issues.jboss.org/browse/JBIDE-13948
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 4.1.0.Alpha2
Reporter: Jaroslav Jankovič
Assignee: Rob Stryker
Fix For: 4.1.0.Beta1
--
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