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

Re: [EGIT PATCH] Rename org.spearce.egit -> org.eclipse.egit

From
Robin Rosenberg <robin.rosenberg@dewire.com>
Date
Jun 18, 2009, 23:20 UTC
Message-ID
<200906190120.29915.robin.rosenberg@dewire.com>
In-Reply-To
<1245253576-13324-1-git-send-email-spearce@spearce.org>

Need an idea on how to proceed here. There is a problem related to updating plugins here. We have renamed feature with one unrenamed plugin. How to we avoid problem when switching from org.spearce to org.eclipse

One option is to release a v0.4.1 (which we should do anyway), which is the last version from master before the split. For technical reasons this will be a branch since the split occurred already.

That 0.4.1 feature should require jgit < 0.5. Then we jgit to v0.5 and make org.eclipse.egit require jgit >= 0.5

Having two EGit features will be confusing. You get two of everything. E.g. Team>Share will have two Git's to choose from, but you cannot tell which is which.

That said, having both could be a feature, since it (didn't really try it), would be possible to switch between new and old workspaces and get the plugin configured for that workspace. The wierdness make me suggest we do not do this. If we really want it we could choose to create a proxy plugin for attaching old workspaces to the new plugins.

-- robin
Next: Shawn O. Pearce
Message 1 of 3 in “Re: [EGIT PATCH] Rename org.spearce.egit -> org.eclipse.egit”
  1. Robin RosenbergJun 18, 2009
  2. Shawn O. PearceJun 18, 2009
  3. Alex BlewittJun 19, 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.