> First I've created a project, and compiled it. I clicked on Team->Share
Project..., then chose SVN.
> As Url, I gave
> thinking that my project "abc" should live there. As Root url, I set
> ourproject. Then came the question of specifying module name. I wondered
why should I give one.
> I gave the place as the Url, and I don't want to create extra directories
under it. Am I thinking
The URL probably should have been something like:
And then the module name would have been "abc/trunk". The repo root looks
> As an obvious hack, I've created abc and trunk subdirectories. My comment
to this is: yes, I can
> create these directories manually, but wouldn't it be nice if Subclipse
did it automatically?
It would be better if Subversion did it automatically. There has been work
on a new feature to svn mkdir to add a -p switch to do this. Last I knew
it was working on a WC but not a URL. Not sure where it stands. Subclipse
could in theory run the 6 individual svn mkdir commands it would take to
create that path. That would result in 6 commits. Is that what people
would want us to do? I am not sure.
> Problems reported while synchronizing SVNStatusSubscriber. 0 of 1
resources were synchronized.
> An error occurred synchronizing /abc: Error getting status for resource
I have seen this message for a variety of reasons. I think it is just what
it says when any error happens during the process. The most recent time I
got it, it was because the user had changed their password so the one
stored in Subclipse was wrong. I think I have also seen it when the
Eclipse resource was out of synch with the file system. Like I said
though, I think any error will result in seeing this message. It is
something we are looking into. It is not clear whether the status
operation itself does not return errors correctly, or if it is something
about the oddities of the Eclipse Synch framework and API's.
I am not going to keep quoting the rest. Generally, after you finish the
Share Project process a folder has been created in the repository, and that
folder is then checked out, thereby turning your Eclipse project into a WC.
At that point, you can do commit to add the resources. The commit dialog
will let you add everything, but you can of course run svn add first if you
want. It launches the Synch wizard to do all of this, but in the end, you
just need to take those options.
You are currently using the command line adapter, you should really try to
switch to JavaHL if possible, and if not that, then JavaSVN. I was able to
compile JavaHL on Ubuntu using the Subversion Tarball. The only thing I
never figured out was how to get the Subversion libraries into
LD_LIBRARY_PATH, which for some reason is not set on Ubuntu. I worked
around that by launching Eclipse with a shell script so that I could set
LD_LIBRARY_PATH so that Eclipse would find the Subversion libraries at
startup. Recently, someone posted packages for Debian too. I do not have
the URL handy but it has been discussed in this list.
Also, like I said, you could try JavaSVN which is a pure Java alternative.
> I accept that Subclipse is very much under development, but I'm a bit
reluctant to rely on it in my
> job in the face of these errors. Am I wrong?
Obviously that is a decision only you can make. A lot of people have been
using Subclipse for a long time successfully. I always get pretty
discouraged when I see stuff like this because it works so well for me and
in my company. It is frustrating that some people still run into these
problems and we have not been able to solve them 100%. The biggest problem
is that *nix users have a hard time getting working JavaHL bindings.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Fri Feb 25 12:27:51 2005