-
Notifications
You must be signed in to change notification settings - Fork 227
Use LTK Refactoring when copying (duplicating) a Project. #2262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use LTK Refactoring when copying (duplicating) a Project. #2262
Conversation
Test Results 1 802 files + 588 1 802 suites +588 2h 0m 40s ⏱️ + 1h 4m 48s For more details on these failures, see this check. Results for commit 3786445. ± Comparison against base commit 7aaa014. ♻️ This comment has been updated with latest results. |
e222d9f
to
d619d9e
Compare
f73dc58
to
4acc07e
Compare
512ca60
to
559e7bd
Compare
559e7bd
to
ce12744
Compare
...se.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/resource/CopyProjectChange.java
Show resolved
Hide resolved
The Idea is that currently it is not possible to modify a project when it is copied and renamed. This leads to usability issues for example in PDE, where the rename of a project modifies the MANIFEST.MF but a copy does not. This solves this by providing a copy project refactoring that can be extended using a copy participant.
ce12744
to
9ebcb2a
Compare
This pull request changes some projects for the first time in this development cycle.
An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patch
Further information are available in Common Build Issues - Missing version increments. |
6a3eb35
into
eclipse-platform:master
@mickaelistria thank you very much for merging |
Thank you for the patch! |
I think the plugin.properties was missing in the commit. |
@jukzi @mickaelistria thank you for noticing, I will look into it directly... |
The Idea is that currently it is not possible to modify a project when it is copied and renamed. This leads to usability issues for example in PDE, where the rename of a project modifies the MANIFEST.MF but a copy does not. This solves this by providing a copy project refactoring that can be extended using a copy participant.
This is related to #2155