Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orion-dev] eclipse.GitService is not a constructor

John, sorry for the frustration.
For now, please take the latest I-build toward M6 and use that as your target.
Clear localstorage as well, because we've had recent changes to cached plug-in data.
This should work.

As Andrew mentioned, the git server code is dependent on jgit, and the dependencies update rather frequently to pick up features and function from jgit.
What this means to you is that the server must be updated more frequently than in the past.
During M5, I was able to run M4 as my target for nearly the entire milestone. During M6 development, I've found myself taking new target platforms much more frequently.

I updated the wiki page to suggest taking the most recent I-build as a practice.

I think it's good practice that the server folks send a note to orion-dev anytime a dependency is introduced/changed between I-builds, letting us know that we need to change our targets. For example, I got busted one day when a com.jcraft.jsch dependency version changed, and we didn't have an N-build containing it. That required pulling in code from orbit.

Part of the problem is that we are pulling the latest from target. Maybe folks like John who don't need daily disruption should be pulling a specific tagged version of the client????

susan


Inactive hide details for "John J. Barton" ---03/11/2011 08:12:59 AM---On 3/11/2011 7:57 AM, Andrew Niefer wrote: > Updating th"John J. Barton" ---03/11/2011 08:12:59 AM---On 3/11/2011 7:57 AM, Andrew Niefer wrote: > Updating the target build should probably fix this.

From: "John J. Barton" <johnjbarton@xxxxxxxxxxxxxxx>
To: orion-dev@xxxxxxxxxxx
Date: 03/11/2011 08:12 AM
Subject: Re: [orion-dev] eclipse.GitService is not a constructor
Sent by: orion-dev-bounces@xxxxxxxxxxx




On 3/11/2011 7:57 AM, Andrew Niefer wrote:
      Updating the target build should probably fix this.
What target build should I use? I thought the target build was supposed to be the previous stable build.
      Alternatively, you can import existing projects and get the org.eclipse.orion.server/features/* projects into your workspace.
Sorry I don't understand what you are suggesting. I followed the source instructions and have 20+ server projects in my workspace, but many of them don't build. The only way I could something to work was to close all of them.

      The "web-ide" launch configuration is set up to use features to determine which plugins will be in the running server. If you haven't imported the features, then they come from the target platform. It is likely that you have older features in the target that don't include some git plugin.

Just to point out: the error message is from the client code.

      Generally speaking, it is also a good idea to keep the target platform up to date because the git server plugins in particular do compile against recent versions of jgit. Having an older version of jgit in the target could lead to runtime errors.
I'm up for anything that will work, but I only have the wiki instructions to go on so I don't know what to do next.

jjb _______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/orion-dev

GIF image

Back to the top