blocks|key|1764946|text|我围绕产品创建Eclipse工作区，因为对我来说，一个产品可以包含多个项目，例如，将核心库编译到项目中的一个jar中，这将被其他项目使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1764947|在生产环境方面，您可能希望产品在不同的目录结构中运行，这样会更干净。在eclipse中，工作区创建一个带有工作区名称的目录。因此，基于产品/应用程序创建工作区，而不是其中的一个或多个项目。|1764948|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I create Eclipse workspaces around products, because for me, a product can have multiple projects within them, for example like having core libraries compiled into one jar in a project, this is used by other projects.

In terms of production environment, you would want products running in different directory structures, much cleaner that way. And in eclipse the workspace creates a directory with workspace name. So, create workspaces based on product/app rather than one or more projects within them.

blocks|key|4406490|text|我会对不同的“组”项目使用不同的工作区。例如，您可能希望在同一工作区中将主应用程序项目和单元测试项目组合在一起。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4406491|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would use separate workspaces for different "groups" of projects. For example you might want to combine your main app project AND the unit testing project together in the same workspace.

blocks|key|5822614|text|如果项目是相互关联的(即彼此之间存在依赖关系)，那么将它们放在同一个工作区中通常是有意义的。此外，如果您正在处理多个项目以解决相关问题，这一点同样适用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5822615|否则，您将浪费大量时间不必要地更改工作区，特别是当IDE将立即向您显示一个项目中的更改对另一个项目的影响时。|5822616|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If the projects are interrelated (i.e. have dependencies on each other) then it quite often makes sense to have them in the same workspace. Also, if you are working on several projects to solve a related problem, the same applies. 

You will waste a lot of time changing workspaces unnecessarily otherwise, especially when the IDE will immediately show you the impact the changes in one project has on another.

blocks|key|2294321|text|你说了算！我总是发现，在给定的工作空间中保持不同项目的相关版本是一种更干净的方法。这样，每当我需要引用单独版本中的内容时，我都可以在工作区之间切换，并切换回当前版本的工作区。它还使我省去了签出或浏览存储库的麻烦。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2294322|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Up to you! I've always found keeping the related versions of different projects, which belong to the same release in a given workspace a cleaner approach. That way, I could switch between workspaces whenever I need to refer to something in a separate release, and switch back to the current release workspace. 
It also saves me from the hassle of checking-out, or browsing the repository.

blocks|key|1768019|text|您可能还想记住，您可以打开多个eclipse实例，只要它们在不同的工作区中。我不确定这对你是否重要，但我喜欢时不时地这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1768020|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You may also want to keep in mind that you can open multiple instances of eclipse as long as they are looking at different workspaces. Not sure if that is important to you, but I like doing that from time to time.

blocks|key|1768022|text|也许我不走运，但Eclipse经常(比如说每月一次)在启动时死掉，通常是在“初始化Java工具”阶段。推荐的解决方案似乎是创建一个新的工作区。如果您将所有项目都放在一个工作区中，这可能是一件痛苦的事情。我认为较小的工作空间可能意味着崩溃发生的可能性较小。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1768023|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Maybe I'm unlucky, but Eclipse often (once a month, say) dies on startup, typically in the "Initializing Java Tooling" stage. The recommended solution seems to be to create a new workspace. If you have all your projects in one workspace, this can be a pain. I think smaller workspaces may mean the crash is less likely to occur.

blocks|key|2294380|text|由于首选项是特定于工作区的，我倾向于打开一个巨大的工作区--我懒得在工作区之间同步一些设置(例如存储库...)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2294381|另一方面，在一个工作区中打开太多的项目可能会降低Eclipse的运行速度--所以我至少要做的就是关闭我没有在处理的项目。我在Eclipse中管理许多相对短期的项目(最多一个月)，这些项目驻留在相同的工作空间(大多数情况下是相同的存储库)中，因此这种设置为我提供了更大的灵活性。|2294382|如果您有多个相互关联的项目，请将它们放在同一个工作区中。如果您可以确定一组项目，这些项目总是一起使用，但这些组是单独使用的，则将这些项目集放入不同的工作区。在这种情况下，这应该是逻辑结构。|2294383|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

As the Preferences are workspace-specific, I tend to have a enormous workspace open - I'm too lazy to sync some settings between workspaces (e.g. repositories...).

On the other having too much projects open in a single workspace can slow down Eclipse - so the least I have to do is to close projects I'm not working with. I manage a lot of relative short-term projects (at most one month) in Eclipse, that reside in the same workspace (and in most cases the same repository), so this setup gives me a bigger flexibility.

If you have several, interrelated projects, then keep them in the same workspace. If you can identify group of projects, that are always used together, but the groups are used independently, then put such project sets into different workspaces. In that case that should be the logical structure.

blocks|key|5822771|text|我过去常常保持独立的工作区，但我厌倦了保持它们之间的设置一致的困难。现在，我要做的是为不同的项目创建工作集，并更改当前的窗口工作集，以过滤掉除我想要处理的内容之外的所有内容。到目前为止，这对我来说工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5822772|由于每个项目可以有多个工作集，而window工作集可以是工作集的任意组合，因此很容易以这种方式在任何给定时间只看到您想要的内容。|5822773|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I used to keep separate workspaces, but got tired of the difficulty in keeping settings consistent between them. Now what I do is create working sets for different projects and change the current window working set to filter out everything except what I want to work on. So far this has worked fine for me.

Since each project can have multiple working sets, and the window working set can be any combination of working sets, it's quite easy to only see what you want at any given time this way.

blocks|key|4406702|text|我们有这样一种情况，我们有几个项目，其中一些在分支上，坦率地说，这些项目太不切实际，不能放在同一个工作空间中-工作集就是一个笑话。不幸的是。还有打开你不使用的项目，可能会意外地从完成菜单中选择，等等，容易出错。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4406703|对我们来说，真正好用的特性是添加了Team+->项目集(我相信是在Eclipse3.3中)，因为这允许我们有一个单一的文件来描述组成整个应用程序的许多项目，可以通过Team->Import导入到Eclipse中。需要一个给定的项目吗？从CVS中检出它，找到其中的projectSet.psf文件，然后导入该文件。|4406704|事实证明，这对我们来说效果很好。|4406705|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

We have a situation where we have several projects, some on branches, which frankly is too impractical to keep in the same workspace - and working sets are a joke. Unfortunately. Also having projects open you do not use, may accidentially be chosen from completion menues, etc. Error prone.

The really nifty feature for us, was when Team -> Project Sets were added (in Eclipse 3.3 I believe) as this allowed us to have a single file describing the many projects making up the whole application, which can be imported in Eclipse with Team->Import. Need a given project? Check it out of CVS, locate the projectSet.psf file inside of it, and import THAT. 

This has proven to work well for us.

blocks|key|2294481|text|我喜欢使用几个分离的工作区(根据项目类型的不同而不同)，它们从不同的位置导入项目。轻松移动东西，而不会创建大量类似的工作区。我的SCM也玩得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2294482|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I like to use several decoupled workspaces (which differ depending on the type of project), which import projects from various locations. Easy to move things around, without creating a ton of similar workspaces. Plays nice with my SCM too.

blocks|key|5822845|text|我不仅为每个项目保留了单独的工作区，而且还为Eclipse保留了单独的副本。这是因为我通常不得不将项目搁置很长一段时间，然后再回来(几乎没有通知)，而且它们绝对必须构建()。我不能冒险让我为最新项目安装的一些插件(基于maven)会干扰其中一个遗留系统(基于ant)的构建过程。为了记录起见，我确实记录了这些遗留系统的eclipse环境，但在修补生产错误时，我没有时间与eclipse打交道。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5822846|entityMap^0|2D|33|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Not only do I keep separate workspaces for each project but I keep separate copies of Eclipse also. This is because I typically have to put projects on ice for long periods and return to them (with little notice) and they absolutely must build. I can't take the chance that some plugin I've installed for my latest project (maven based) will interfere with the build process of one of the legacy systems (ant based). For the record I do document the eclipse environment for those legacy systems but I don't have time to mess with eclipse when patching a production bug.

blocks|key|2294536|text|我每种类型的项目都有一个工作区。例如:纯Java、Web应用程序、Python等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2294537|原因是我可以共享相似的库，而不需要复制或指向它们。此外，为了避免混乱，我关闭了eclipse中不相关的项目。|2294538|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have one workspace per Type of project.
Ex: Plain Java, Web Application, Python etc.

The reason being I can share libraries that are similar without copying or pointing to them.
Also, I close the unrelated projects from eclipse to avoid clutter.

blocks|key|5822911|text|这取决于你做了多少个项目?如果你做了很多项目，我会使用相同的工作区，因为如果你使用了几个项目，你很容易忘记什么是在哪里，至少可以说是令人沮丧的。然而，我总是为不同的编程语言使用不同的工作区，这样就不会那么令人困惑，当您在JAVA工作区中时，您会认为JAVA+:D|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5822912|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Depends on how many projects do you work?If you work on many projects, I'd use same workspace, because if you use several you can easily forget what is where and that can be frustrating to say at least. However I always use different workspace for different programming languages that way its less confusing, when you're in JAVA workspace you think JAVA :D

blocks|key|5822940|text|我的所有项目都在一个工作区中，并使用工作集来管理它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5822941|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have all my projects in single workspace and use working sets to manage them.

I am simply wondering whether it is best to put all of my Eclipse projects into one workspace, or do a 1 workspace per 1 project. I am just a solo developer, for hobby more or less, but the apps I create do actually have production versions that are running on rather frequent cron jobs, so its almost like an amateur production environment.

The only problems I have noticed so far is for exporting JARs, I have the potential to include source files from other projects which seems like it could get messy.

Eclipse: Should I create a workspace for each project?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我只是在想，最好是将我所有的Eclipse项目放在一个工作区中，还是每个项目一个工作区。我只是一个单独的开发人员，或多或少出于爱好，但我创建的应用程序实际上有生产版本，运行在相当频繁的cron作业上，所以它几乎就像一个业余的生产环境。到目前为止，我注意到的唯一问题是导出far，我有可能包含来自其他项目的源文件，这看起来...

问Eclipse:我应该为每个项目创建一个工作区吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse:我应该为每个项目创建一个工作区吗？EN