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

RE: [Subclipse-dev] New release necessary ?

From: Martin Letenay <mle_at_whitestein.com>
Date: 2005-09-12 19:48:37 CEST

> I just did my normal build process I would do for a release.
> I had no problem installing/using in a test Eclipse 3.1 installation.
> The core plugin contained the new lib folder with all of the
> correct updated JAR files, including regexp-1.4.
> Mark

OK, Then maybe I've just messed something up here.
(The Team menu was there but any svn operation was unavailable ...)

I've just commited the fixe for the update problem.
Not only update from sync view was broken but update in general
(whe done on multiple resources at the same time.)

Major problem is fixed, however not everything works 100% yet.
There is something special hapenning when doing individual (non-recursive)
updates on resources
when there were som directories moved/renamed.
However I can get the same errors also with Tortoise, so it's more
subversion than subclipse related.

I'll try to investigate it further later, but from my point of view we
should not wait any longer
with the broken Subclipse in the wild ...

Green light for the release from my side ...


P.S. The clientAdpater fixes were:

-Fixed bug in getInfo() of javaHL adapter.
It was throwing an exception when info was asked for resource
not yet in repository (e.g. added files).
-Fixed bug in cmdLine adapter's propget().
On Windows it was leaving additional CR character at end of the property.
-Reimplemented cmdLine adapter's list() command - now uses "--xml" argument
which is reliable to parse.
-Fixed cmdLine adapter's blame().
When both from and to revisions were passed, the from was always ignored.

- removed dependency on commons-lang
- updated to jakarta-regexp-1.4
Received on Tue Sep 13 03:48:37 2005

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

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