[Subclipse-dev] package refactor issues
From: Dan Lo Bianco <dan.lobianco_at_cloudsoftcorp.com>
Date: Thu, 20 May 2010 05:17:22 -0700 (PDT)
I've spent a fair amount of time googling about this issue, but I've yet to find a definitive answer or solution. For the past few months I've been struggling with subclipse when it comes to renaming java packages. I've finally been able to come up with a working procedure, but it all seems rather unwieldy for what should be a simple action.
Currently, my method for renaming packages starts off with the most logical step- using eclipse to refactor and rename the package. Initially, this seems to work fine- the old packages + classes are marked for deletion, while the new renamed versions come up as new files (but with history, so the history is preserved). However, at this point things start to go wrong- any attempt to synchronise or commit and SVN seems to choke and will indicate the file is out of date. Synchronising seems to then flag the old package as having a 'conflicting deletion'.
Fixing that is a bit of a headache. First, running the update command seems to convert the 'conflicting deletion' into a 'tree conflict'. Once you have the tree conflict, you can view them in the SVN Tree Conflicts view, but for each offending package you must manually select the resolve dialog, untick a checkbox (so you force the deletion through rather than reverting back to the old version on SVN), before confirming the resolution. With 5 - 15 packages per project and at least 20 projects, this is a very repetitive task.
Is there a reason tree conflicts can't be resolved en-masse (certainly in the case of pushing the local changes through as authentic, i.e. equivalents to 'override and update' and 'mark as merged' for files)? Also, am I doing something wrong when it comes to renaming packages, or does everyone have to go through all these hoops?
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
This is an archived mail posted to the Subclipse Dev mailing list.