I am please to announce that Subclipse 1.1.2 has been released and posted
to its update site. We will be following the odd/even numbering standard
that is so often used in open source projects. The odd releases (1.1.x)
in this case are "development releases" leading up to the eventual GA
release of 1.2.0.
Subclipse 1.1.x is built on and requires Eclipse 3.2. It will not install
on previous releases as it uses new API specifically from Eclipse 3.2. I
built it on 3.2 RC6 but I would assume it would run on most of the release
If you are running Eclipse 3.2 and want to try the latest and greatest new
features, then this is probably the release you should use. Otherwise,
stick to the stable 1.0.x releases.
The update site URL for this release is:
This release will not be posted or visible on the general web site. The
mailing list is the only place it will be publicized. This will change as
we get closer to a 1.2.0 release.
The change log for this release stream can be viewed online at:
Here are the relevant bit from the changelog:
NOTE: As of Subclipse 1.1.0, the minimum Eclipse requirement is now 3.2.0.
Subclipse 1.1.2 was built on Eclipse 3.2 RC6. Presumably it will work with
most earlier releases of 3.2.
NOTE: Subclipse 1.1.0 removed the SVN Resource History view as we now use
the common Team History view. You will likely get an Eclipse error message
if you use an existing workspace that had that view open. This is normal
and is not a problem. You will get the error the first time you open each
perspective that had the view open.
13 June 2006
* Fixed refactoring problem when moving more than one class to a new
* Key binding support for commit, update and synchronize. (394)
* Do not enable Finish button on Sharing Wizard until the page where
you specify the folder name.
* Fixed problem where History view did not refresh the current
* Fixed some possible NPE's in Synch view when using svn:externals.
* Fixed handling of commit from Synch view so that it respects the
view settings, such as ChangeSets or items removed from the view. (506)
* When committing a change set, if the proposed comment was not
edited, then the change set was being committed with a null comment.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jun 13 15:43:43 2006