[
https://issues.jboss.org/browse/JBIDE-11877?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-11877:
--------------------------------
Fix Version/s: LATER
(was: 3.3.0.CR1)
This issue will be rejected as "WONT FIX". Currently, cleaning the project
initiates a new build, same in java and jdt. By starting a clean build, all your .class
files are removed, and automatically regenerated.
In the same way, a clean build will delete (and hten regenerate) the project archive. You
can disable the project archives builder if you want.
Simply deleting the .jar file is the same as simply deleting a .class file. Without
deleting the associated .java file (or, for project archives, deleting the archive node),
the automatically generated artifact will be replaced.
The output jar is a build artifact, same as any .class file.
Deleting jar archive from Project Explorer doesn't affect Project
Archives explorer
-----------------------------------------------------------------------------------
Key: JBIDE-11877
URL:
https://issues.jboss.org/browse/JBIDE-11877
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.3.0.Beta3
Reporter: Jaroslav Jankovič
Assignee: Rob Stryker
Fix For: LATER
If I simply delete jar archive (not node within Project Archives explorer) from Project
Explorer, this "change" in project doesn't affect archive node within
Project Archives explorer in Project Explorer - archive is still there. Then when I clean
build the project, jar archive reappears. This seems that only way to remove jar file
permanently is using Project Archives explorer or view. I think that this shouldn't be
the only way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira