From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Stephen Bannasch <stephen.bannasch@deanbrook.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [EGIT RFC PATCH(was Re: egit problem with sym linked eclipse project dirs)] Add some support for symlinked projects.
Date: Wed, 18 Mar 2009 22:09:16 +0100 [thread overview]
Message-ID: <200903182209.17493.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <p06240820c5e6c6a7d62a@[63.138.152.192]>
onsdag 18 mars 2009 17:02:15 skrev Stephen Bannasch <stephen.bannasch@deanbrook.org>:
> At 7:56 AM +0100 3/12/09, Robin Rosenberg wrote:
> >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
>
> ...
>
> > > 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
Thanks. Deleteing from the update manager deletes the feature from the features
directory plus configuration data.
> >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".
I do it all the time. Come to think of it, just selecting Run As requires that an appropriate
plugin project is selected in the package explorer. Select the org.spearce.egit.ui project
and then Run As > Eclipse Application. You can modify which workspace to open in
the launch configuration. If you want to work on an existing workspace you have to
modify the launch configuration since the launched eclipse won't let you (maybe it
does, but not by default).
-- robin
next prev parent reply other threads:[~2009-03-18 21:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 20:00 egit problem with sym linked eclipse project dirs Stephen Bannasch
2009-01-13 21:37 ` Robin Rosenberg
2009-01-13 23:27 ` Stephen Bannasch
2009-01-23 1:56 ` Stephen Bannasch
2009-01-23 21:33 ` Robin Rosenberg
2009-03-11 22:17 ` [EGIT RFC PATCH(was Re: egit problem with sym linked eclipse project dirs)] Add some support for symlinked projects Robin Rosenberg
2009-03-12 2:57 ` Stephen Bannasch
2009-03-12 6:56 ` Robin Rosenberg
2009-03-18 16:02 ` Stephen Bannasch
2009-03-18 21:09 ` Robin Rosenberg [this message]
2009-03-18 21:10 ` Robin Rosenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903182209.17493.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=stephen.bannasch@deanbrook.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).