"Cain, Tom" <tcain@solekai.com> wrote on 11/02/2006 11:24:58 PM:
> We've already integrated Subclipse 1.0.3 into our Eclipse application,
and
> using the ISVNClientAdapter from the svnClientAdapter module for all of
our
> SVN operations. Now that Subclipse 1.1.8 is out and fully supports the
new
> 1.4 WC format, we'd like to upgrade our application to the new version.
> However, it seems that due to the new (since 1.1.0) packaging of the
> Subclipse jars, we can no longer access the svnClientAdapter.jar file
that
> is embedded in the subclipse.core plugin jar (even tho the necessary
exports
> are defined).
> Is this a known issue? I've found similar bugs posted on the Eclipse
site
> related to access to jars inside of jars (ex: https://bugs.eclipse.
> org/bugs/show_bug.cgi?id=139755)
> The workaround I've hacked locally is to extract the subclipse.core
plugin
> into a folder and use that instead. The only problem is that we cannot
> enforce the users of our application to do the same.
It should all work, after all the Subclipse UI plugin has to use these
classes and there is nothing special about that plugin just because it
comes from us. You just need to use Eclipse 3.2 and get your plugin
updated correctly so that it finds the JAR. Perhaps look at the relevant
aspects from the UI plugin.
If I remembered exactly what you have to do I would tell you.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Fri Nov 3 14:29:15 2006