| Summary: | [ltk] DeleteArguments misses API getDeleteProjectContents() | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
| Component: | UI | Assignee: | Markus Keller <markus.kell.r> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | markus.kell.r, remy.suen |
| Version: | 3.8 | Keywords: | api |
| Target Milestone: | 3.8 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 361566 | ||
Fixed in master. commit 6a7fe43fe3636b92c240f9c2be1cc5b4ec721357 |
master DeleteArguments misses the API below. Without that, participants can't know whether contents will be deleted or not. /** * Returns whether projects contents will be deleted as well. This method * is not applicable for file and folder deletions. * * @return <code>true</code> if the refactoring will delete the project * contents, <code>false</code> if it only removes the reference * from the workspace */ public boolean getDeleteProjectContents() { return fDeleteProjectContents; }