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

Commit error on moving packages between repository

From: Sejal Patel <sepatel_at_gmail.com>
Date: 2005-11-19 23:36:33 CET

Hey guys. I'm totally new to this and am not even on this mailing list. I've
been using subversion for a while and subclipse plugin for eclipse as well.
I've never noticed this issue before but I've never tried this exact thing
before either. I went to file the bug report and the page said I should
search for existing entry (couldn't find one) and if not found email here to
find out the appropriate way to file the report and with whom to file it

This issue is a subclipse bug. I'll explain the scenario in which the
problem occurs. Then I'll give my untested hypothesis on why it happens 100%
of the time.

Checkout project A from http://myserver/svn/repo/myprojectA/trunk/cma
Checkout project B from http://myserver/svn/repo/newprojectB/trunk/cma

In project A
click on a package with 3 or more directory structures deep and drag it into
the project B source folder.

Example of a project that deep would be com.department.section.project
In that package structure there should be at least 1 file (MyReport.java).

All that stuff should already be checked in and commit in project A and have
a history.

When you drag that package to project B it copies everything over and marks
them for addition in the new project. That is correct. However, it always
errors out without any explaination (not even in the console view) for why.
Other things in that project will checkin fine but not anything related to
the new package just dragged over and added.

Updates will also work fine even on the dragged over package. Just will not
let you commit.

That is the problem.

My hypothesis is that this is because it copies over the .svn folders in the
packages. I believe this is the case because even from the command line I
could not commit the stuff. However when I made each and every one of those
folders by hand and copies all the files over to it and did a commit on that
same stuff (basically only the .svn did not exist) it worked perfectly (even
from inside of eclipse).

This just happened a few minutes ago and I just updated (clean install of
eclipse 3.1.1 with new workspace and fresh install of the subclipse plugin
and then fresh checkout of the projects were all done) yesterday. So I know
it isn't that I'm out of date. I'm also on a linux (ubuntu breezy) platform
so I can't say if the same thing happens in windows (haven't really used
that in nearly 5 years) but I'm fairly certain it is just an problem because
it moves the .svn folders with it.

Justice is nothing more than that which is in the greatest self-interest of
the largest portion of the population.
Received on Sun Nov 20 09:36:33 2005

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.