git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [EGIT RFC PATCH(was Re: egit problem with sym linked eclipse project dirs)] Add some support for symlinked projects.

From
SBStephen Bannasch <stephen.bannasch@deanbrook.org>
Date
Mar 18, 2009, 16:02 UTC
Message-ID
<p06240820c5e6c6a7d62a@[63.138.152.192]>
In-Reply-To
<200903120756.07853.robin.rosenberg.lists@dewire.com>
At 7:56 AM +0100 3/12/09, Robin Rosenberg wrote:
Show 6 quoted lines
>torsdag 12 mars 2009 03:57:09 skrev Stephen Bannasch 
><stephen.bannasch@deanbrook.org>:
>>  OK ... I'm a bit confused now because I no longer have Git listed as
>>  a repository type for Team Sharing.
>>
>  > I deleted the existing org.spearce.* eclipse plugins
...
Show 17 quoted lines
>  > The new plugins are there:
>>
>>     [eclipse]$ ls plugins/org.spearce.*
>>     plugins/org.spearce.egit.core.test_0.4.0.200903112237.jar
>>     plugins/org.spearce.egit_0.4.0.200903112237.jar
>>     plugins/org.spearce.egit.core_0.4.0.200903112237.jar
>>     plugins/org.spearce.jgit_0.4.0.200903112237.jar
>>     plugins/org.spearce.egit.ui_0.4.0.200903112237.jar
>>
>>  Quit and restarted Eclipse.
>>
>>  When I select a project with an existing git repository and try to
>>  enable team/sharing only CVS and SVN are listed.
>
>You don't have the a matching feature. That could be it, but I'm not sure.
>You can also try starting eclipse witth the -clean switch. Looking at the
><workspace>/.metadata/.log could also give you some hints.

I figured out the problem I had when testing the patched egit plugin. If I had installed egit from the update site I had to do more than just delete the jars -- I had to delete the whole feature from within Eclipse -- and then install the new plugin built from source.

In figuring this out I ended up testing the original problem with the master branch from earlier today and didn't see the issue I originally reported.

Did you already integrate the experimental patch?
Here's a documentation patch:
 From feb1ae0ccf7f671506853f4f49e9041950404b3d Mon Sep 17 00:00:00 2001
From: Stephen Bannasch <stephen.bannasch@gmail.com>
Date: Wed, 18 Mar 2009 11:51:56 -0400
Subject: [PATCH] clarify how to delete egit plugin when installing new build
---
  EGIT_INSTALL |   11 ++++++++++-
  1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/EGIT_INSTALL b/EGIT_INSTALL
index 3a8f249..3a9c209 100644
--- a/EGIT_INSTALL
+++ b/EGIT_INSTALL
@@ -21,7 +21,16 @@ things.

  INSTALLATION INSTRUCTIONS

-- Delete any old versions of the plugin in the 
<eclipse-path>/plugins/org.spearce.*
+First remove any existing egit plugin.
+
+If you have installed egit from the egit update site 
http://www.jgit.org/update-site:
+
+  delete the plugin from Software Updates and Add-ons from within  Eclipse
+
+If you have installed the plugin from source:
+
+  delete any old versions of the plugin jars in the 
<eclipse-path>/plugins/org.spearce.*
+
  - Start eclipse
  - Make sure a recent JDK 1.5.0_11 or JDK 1.6.x is among your 
installed JRE's. Which
    one is the default should not matter but Java 6 is recommended.
--
1.6.1.2


>For debugging/testing in general it is often easier to launch Eclipse from
>eclipse (Run As) without reinstalling.

As part of this test I need to switch to another workspace and I 
couldn't get that working with "Run As".
Previous: Robin RosenbergNext: Robin Rosenberg
Message 9 of 11 in “egit problem with sym linked eclipse project dirs”
  1. Stephen BannaschJan 13, 2009
  2. Robin RosenbergJan 13, 2009
  3. Stephen BannaschJan 13, 2009
  4. Stephen BannaschJan 23, 2009
  5. Robin RosenbergJan 23, 2009
  6. Add some support for symlinked projects.Robin Rosenberg, Mar 11, 2009
  7. Stephen BannaschMar 12, 2009
  8. Robin RosenbergMar 12, 2009
  9. Stephen BannaschMar 18, 2009
  10. Robin RosenbergMar 18, 2009
  11. Robin RosenbergMar 18, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.