Eclipse Team Etceteras: Message Forum: Supported Eclipse revisions

Mailing Lists
Message Forum
» Message Forum
Issue Tracking
» Jira
Source Code Repository
» svn
Website
» Web Site
Wiki
» Wiki

Eclipse Team Etceteras was started in August 2009, is owned by Michael Pellaton, and has 3 members.

» Join This Project

Supported Eclipse revisions

» Back to forum topics

4 posts

Replies: 3 - Last Post: January 12, 2011 14:36
by: michael.vogt

« Older Topic » Newer Topic

showing 1 - 4 of 4

michael.vogt

Posted: January 11, 2011 14:51 by michael.vogt

» Permalink

Hi,

I have just installed version 2.8.0 as an extension to our eclipse based custom application. At this time we are still based on eclipse platform 3.3.2. The installation worked without any problems and the netcetera plugins are shown when looking at the feature and plugin details of the running system. However, they don't seem to work....

Digging a bit deeper with the Plug-in Registry view, I found there are dependencies to eclipse core and ui versions 3.5.0. This is obviously not what I have.... Frown

Questions: Is there a netcetera version available, working for eclipse 3.3? Is eclipse 3.5 or greater mandatory or was this just an arbitrary choice?

Michael

Michael Pellaton

Posted: January 11, 2011 17:41 by Michael Pellaton

» Permalink

Hi,

The short answer is: no, there are no pre-built deployable packages for older platforms than 3.5.0 as this was the development target platform.

The longer answer is: You might try to build the plug-ins from source against an older target and I, don't expect too many problems provided that the preference service API has not changed (and I believe it has not changed between 3.5.0 and 3.3.2).

HTH
Michael

Michael Pellaton

Posted: January 11, 2011 19:27 by Michael Pellaton

» Permalink

Hi,

I did a very quick test to see whether it can be built against 3.3.2 and as far as I see, there are at least the following problems:

FrameworkUtil.getBundle() did not exist in 3.3.2. However this code could be replaced with static references to the corresponding Plugin class.
The services are provided as dynamic services (DS) and I am not sure whether there is a org.eclipse.equinox.ds version that runs on a that old OSGi framework. This could be solved by instantiating the services directly where they are used.

The conclusion for the project is that the version constraints imposed on the platform seem to be right in order for the dynamic services to work. However, somewhere the version constraints must be fixed so that the bundles can no longer be installed in case the platform is too old. I opened an bug report for that issue: http://kenai.com/jira/browse/ETE-68

For your case I suggest re-implementing the functions needed in your project based on the ETE services.

HTH,
Michael

michael.vogt	Posted: January 12, 2011 14:36 by michael.vogt » Permalink
	Thanks a lot for the quick answer. I will consider trying it out.... Michael

Replies: 3 - Last Post: January 12, 2011 14:36
by: michael.vogt

« Older Topic » Newer Topic