On Fri, Aug 29, 2008 at 5:42 PM, Fulara, Adil <AFulara_at_directv.com> wrote:
> My name is Adil and I work at DIRECTV, Inc. as a tool developer. The tool is
> based on the Eclipse framework and currently uses subclipse 1.2.4
> The dev team here is planning to migrate to subclipse 1.4.x in order to work
> with subversion 1.5
> At present, I have installed subclipse 1.4.3 and related plugins via
> "Software Update" in Eclipse IDE and have run into problems.
> I was directed by Mark Phippard to get in touch with this email address to
> seek assistance in successfully migrating.
> Couple of errors has arisen due to API changes so I thought it would be
> great if you could point me to a javadoc or an article on your website which
> could help me resolve the issue.
> The IDE complains of CommitDialog missing from
> org.tigris.subclipse.ui.dialogs package.
> I did read the changelog of the previous releases and I believe subclipse
> now uses a wizard driven approach but I am not sure how to proceed.
This has been moved to a new package name and we forgot to export it.
This will be corrected in 1.4.4 release, which should be out fairly
soon. In 1.4.4, the user that reported this also added a new
extension mechanism to the commit dialog so that they could contribute
actions to items without specifically subclassing our code. I'd
highly recommend you consider a similar approach and we are certainly
open to extending our product in that way.
See this mailing list thread for the discussion related to this:
And here were the relevant commits that will be in 1.4.4:
> Has the package org.tigris.subversion.svnclientadapter.commandline moved?
No, but we no longer provide it with Subclipse. We never used it
ourselves. If you want to write code that uses svnClientAdapter we
have actually made changes that should make this much easier. When
you install Subclipse 1.4.x, instead of svnClientAdapter.jar being
included in the Subclipse core plugin, it is not a plugin itself. The
base SVN Client Adapter plugin just provides the base interfaces and
an extension point for client adapters to plug in to. We provide
JavaHL and SVNKit as separate plugins you can install to fill it in.
You should be able able to write code to the SVN Client Adapter plugin
and insulate your code from depending on a specific client adapter.
You can even just use the Subclipse core plugin as a way to get an
ISVNClientAdapter and it will do so based on the preferences you have
set within Eclipse.
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-08-30 00:04:33 CEST