[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Major refactoring - issues?

From: DM Smith <dmsmith555_at_yahoo.com>
Date: 2006-02-08 15:38:15 CET

Karl Auer wrote:
> Hi there.
> We have a few Java projects, developed using Eclipse, where packages
> weren't used properly. That is, all the application classes are in their
> project default packages.
> I can't seem to rename the default package in Eclipse. Hm.
The default package is an artifact of the "view" and not an actual
folder under src (or where ever you keep your source). So it makes sense
that you can't rename it.
> OK, what I could do (for each project) is create a new package in the
> same project, move all the sources (drag and drop) from the default
> package to the new package, then delete the default package. Actually, I
> think it deletes itself if it's empty.
It does not get deleted because it does not exist in the first place. It
disappears because it is no longer needed.
> But what will this too in Subversion/Subclipse terms? Will the moves be
> properly tracked, to be recorded in the repository when I commit the
> project? It seems to me it should. Are there any other gotchas I should
> know about?
I have had problems refactoring into a folder that has been added to svn
but not committed.

Using svn to move a file from one folder to another will retain its
history. Subclipse somehow hooks into Eclipse's refactoring to do the
move for you. Very nice.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Feb 8 15:38:26 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.